Gepostet am:23.04.2009 01:57
#9
Aw:: Plugins bei Wordpress-Modul funktionieren nicht
23.04.2009 01:57 Es gibt noch eine neuere version. Gamcht bei Novasmart:
XOOPS WordPress/Xpress 2.11.0
http://xoops.novasmarttechnology.com/modules/wfdownloads/singlefile.php?cid=2&lid=2
WordPress For XOOPS 2.11.0
If the reader wonders, why we waste our time to spent time to upgrade “abandon” modules instead of working om AMS 2.50 Beta 2 as fast as possible, here is our answer.
We like WordPress for XOOPS, its stable and surpass all XOOPS blog modules that we try. XPRESS or wordpress 2.05 should be maintain by xoopsforge.com (phppp) and we put a lot of trust the module will be updated by him regularly. Thats the main reason we use this module in our sites (yes, it is sites, not site ). But of course, we not just blindly put our trust to xoopsforge.com to maintain the module (its normal for open source), we did our own study and conclude in case there is no update from xoopsforge.com, we can update it ourself without significant resources.
Unfortunately, what we afraid is occur. After Wordpress 2.05, xoopsforge.com stop updating the modules and left it un-patch for > 1 year. Same as AMS, we only have 2 choice… update it ourself or left it vulnerable. So, our choice is clear, lets patch it. However contra with AMS, we didn’t plan to take over the development.
With our limited knowledge, it take us 15 man-hours to finish the update/patch to Wordpress 2.0.11 including regression testing. Luckily, its work like a charm and its rock solid stable in our server. So, we name it as WordPress For XOOPS 2.11.0 mimick the same numbering as xoopsforge. Whats 15 man-hours mean to us ? With only 1 person working on this modules, its mean 2 weeks of development since our average spent time in XOOPS projects only 1 hour/day per person.
After we publish our work at xoops.org, we got some request to upgrade the module to WordPress 2.6.x, but we politely refuse to do so since it will take significant amount of our time to do so. We need to take our resource from AMS if we did so. Except someout want to pay our effort, I think we don’t want to involve. FYI, the to upgrade the module to be compatible with WordPress 2.6.x, we need to modify and validate 300+ files compared than to update the module to WordPress 2.0.11, we need to touch only 81 files.http://xoops.novasmarttechnology.com/modules/wordpress/6/ams-development/wordpress-for-xoops-2110-and-ams-250-beta-2
When ich aber lese auf worpress site sieht es so aus alsob dieser version dangerous ist:
March 2, 2007 WordPress 2.1.1 dangerous, Upgrade to 2.1.2
http://wordpress.org/development/category/releases/
