|
Anti register bots
from PEAK XOOPS
(2007/8/23 3:57)
|
I've just released Protector 3.13 with anti auto registering bots. (You can search it by petro@dnati7.org , george-walker-bush.info or boss@villa9.org) If you installed Protector correctly, just copy the plugin filters_disabled/postcommon_register_insert_js_check.php into filters_enabled/. No core hacks needed. Since I don't like Captcha (it's not friendly with visible handicapped), I make it as JavaScript. You should check a guest can register after enable the plugin. You can also check the bots will be rejected by turn JavaScript off. Note: If you access via "Reliable IPs" in Preferences of Protector, this plugin never stop registering.
|
|
Compatibilities between Core from xoops.org and D3 modules
from PEAK XOOPS
(2007/7/12 18:06)
|
The versions of 2.0.14/15/16 from xoops.org are troublesome because they lost basic compatibilities before 2.0.13 though they are numbered as 2.0.x.To be honest, I want to say"use XOOPS 2.0.16a-JP instead of such a buggy version":-)However, I had declared"I don't stand each side of cores".Then, I have to support my modules against 2.0.16 from xoops.orgAt first, I've modified"altsys"which should be the foundation of D3 modules.Almost works were executed with the feature of tplsadmin.Let's try altsys-0.55 with 2.0.16, and report bugs to me.And I doubt why the incompatibility of the template system is not fixed at all.If class/smarty/xoops_plugins/resource.db.php is fixed by the patch, All of Xoopsers -Core team-, -module developpers-, and -pure users- must get a lot of benefits. (I assert it!)I expect it to the new core team of xoops.org strongly. :-D
|
|
d3pipes - Ajax in admin side
from PEAK XOOPS
(2007/7/6 6:22)
|
d3pipes implements Ajax for constructing a pipe from various joints.You can see- Reordering by drag&drop- Different forms corresponding to each jointsJust copy JavaScript library named"common/lib"into your XOOPS.http://xoops.peak.ne.jp/md/mydownloads/singlefile.php?lid=104And you can also see from the picture - the admin theme is made by bcool's taka.http://demo.2bcool.net/(bc_admin01)This is a very good theme for the altsys's feature of"admin in theme".(Update the altsys into the latest version if you use the feature)
|
|
command injection of phpmailer in XOOPS
from PEAK XOOPS
(2007/6/13 6:03)
|
referhttp://larholm.com/2007/06/11/phpmailer-0day-remote-execution/Though this is a fatal (sudden-death) vulnerability, it is not the default setting.If you dare to change the value of mailmethod from"php mail()"to"sendmail", change it to the other values.I've just released Protector-3.04 with this check.If you leave such a setting, protector alerts"phpmailer security hole! Change the preferences of mail from"sendmail"to another, or upgrade the core right now!"to you.
|
|
Let's make joints (2)
from PEAK XOOPS
(2007/6/11 5:19)
|
I'm itroducing the second sample of"parse joint".This joint named D3pipesParseLinkhtml can fetch"publish time"and"link of the article"on the other hand, D3pipesParseSimplehtml can fetch only the"heading".D3pipesParseLinkhtml has been already included the latest archive of d3pipes.With the sample joint of D3pipesParseLinkhtml, you can make a pipe like this.(Just a sample)[code]0 Fetching from outside snoopy (URI of the page)10 Transfer to UTF-8 (asyoulike) The encoding of the page20 Parsing XML linkhtml #([0-9/]{10}).*href=\"([^"]+)\"\> (.*)\#iU30 Transfer from UTF-8 (asyoulike) Internal encoding of your site40 Clipping into local moduledb 86400[/code]It is defficult to describe the option as a regex pattern for linkhtml.You have to know the meaning of each ().1st () corresponds datetime (published)2nd () corresponds link URI3rd () corresponds the headingOr1st () corresponds link URI2nd () corresponds the heading3rd () corresponds datetime (published)You hav ...
|
|
A naming rule for language directory
from PEAK XOOPS
(2007/6/8 4:36)
|
minahito has suggested new rule for the language directory.[code](language name)_(encoding) (*) all should be small letters[/code]Of course, this change should be graced for the compatibilities.eg)French encoded ISO-8859-* should be named"french"as conventional.French encoded UTF-8 should be named"fr_utf8"newly.Though my modules contains"japaneseutf"as"Japanese encoded UTF-8",they should be renamed"ja_utf8"gradually.
|
|
Installer Attack
from PEAK XOOPS
(2007/6/3 6:40)
|
Do you know'intaller attack'?If you leave'install'folder in the public area of the server, attacker can know your DB password, DB prefix etc.You should know attackers know the folder of'install'can be renamed'_install'etc.This is certainly a mistake of the user.But I find checking a constant'_INSTALL_CHARSET'can protects your xoops from such attacks.I've just updated the module Protector numbered 3.03 with the feature.If you dare to use the installer after installing Protector, remove the precheck line from your mainfile.php
|
|
Language constants overriding system for D3 modules
from PEAK XOOPS
(2007/5/8 3:54)
|
I had written language constants of D3 modules can be override by putting files under XOOPS_ROOT_PATH/modules/(dirname)/langauge/ from XOOPS_TRUST_PATH/modules/(trustdirname)/language/But I found it is hard to use. (eg. Newly appended constants can be displayed its name instead of its value)And I think CMS should be change its language constants not only via FTP but also"control panel".Then, I've just implemented Language constants overriding system into altsys-0.5.- mylangadminA controller called by each module's admin area. (like myblocksadmin or mytplsadmin)This controller saves user values into DB(altsys_language_constants), then makes a cache file under XOOPS_ROOT_PATH/cache/- D3LanguageManagerA singleton class for module/core on including language constants.This class can be used like...[code]require_once XOOPS_TRUST_PATH.'/libs/altsys/class/D3LanguageManager.class.php';$langman =&D3LanguageManager::getInstance() ;$langman-> read('main.php', $mydirname , $mytrustdirname ) ;[/code ...
|
|
Let's make joints (1)
from PEAK XOOPS
(2007/4/27 5:16)
|
It is quite easy to create a joint for d3pipes.This is a sample to get renewal announcement from HTML.With d3pipes, all you have to do is creating a class of parse joint.Make a class definition file underXOOPS_TRUST_PATH/modules/d3pipes/joints/parse/In this document, the class is named as Simplehtml.ClassName: D3pipesParseSimplehtmlFileName: D3pipesParseSimplehtml.class.phpJust write a method of execute() in the file.execute() of"Parse"joint gets a string and returns array of entries.Each entry should have 4 parameters.'heading': heading'pubtime': UnixTimestamp (Set it if you can)'link': URI of the article (Set it if you can)'fingerprint': ID of the articleWith the sample joint of D3pipesParseSimplehtml, you can make a pipe like this.(The site describe each renewal annoucement in )[code]0 Fetching from outside snoopy (URI of the site)10 Transfer to UTF-8 (asyoulike) The encoding of the site20 Parsing XML simplehtml #\([^
|
|
D3 Pipes Introduction (3)
from PEAK XOOPS
(2007/4/23 17:53)
|
Look the flow of (A) with detail.(A) Outer XML fetch/parse patternXML fetching -> convert to UTF8 -> XML parsing -> convert to internal encoding -> extraction -> clipping1) fetching XML string (fetch)This must be used with parser.This joint passes a XML sting to next joint. (without input)2) converting XML string to UTF-8 (utf8to)This joint converts from a XML string to a XML string.This joints is disabled default because almost all RSS are encoded by UTF-83) XML parsing into array (parse)This joint converts from a XML string to some entries can be treated as pipe data.4) converting entries from UTF-8 to internal encoding (utf8to)This joint converts from pipe data to pipe data recursively5) extracting entries (filter)This joint filters entries.Input should be pipe data, also output is pipe data.This joint can be placed after clip, union etc.6) clipping into local (clip)This joint stores entries into DB etc.It is important that clipping_id is assigned for each entries.Using clipping_id, ...
|
