Wigbi 1.1.3 is out

In Wigbi 1.1.2, I added a new .htaccess file that did not contain the magic quotes line, since that line made Wigbi crash if the PHP installation did not support magic quotes. However, I managed to remove the line in the incorrect file, which made all Wigbi AJAX pipeline operations fail. Great scott!

I have added a hotfix (love the name) which is available as Wigib 1.1.3 at github and wigbi.com – get it if you managed to download the crappy 1.1.2 version.

And while I am at it, I can as well talk a bit what will be included in the upcoming Wigbi 1.2. You see,  the Wigbi AJAX pipeline is really convenient, but can expose the system to bad stuff, since any class method can be executed as long as Wigbi is aware of the class. I will therefore add a new configuration file parameter In Wigbi 1.2.0. It is named ajaxClasses and is a comma-separated list with the names of all the classes that can be used with the Wigbi AJAX pipeline. Every data plugin can be used without adding its class name here, as well as Wigbi, but all other classes must be added here before you can go AJAX on them.

Finally, after today’s demo, I have decided to develop another start package called Wigbi CMS, which will feature a (basic) CMS framework. It will be released with Wigbi 1.3.0…which will be out…uhm, soon.

Hotfix fuck up!

The Wigbi 1.1.2 release contains two .htaccess files in the Wibi folder – one with magic quotes disabling and one without. However, I managed to make the wrong one default, so if you download Wigbi 1.1.2, no AJAX operations will work, if you have magic quotes applied.

Either replace the .htaccess file in the Wigbi folder with the NO_MAGIC_QUOTES.htaccess file, or download Wigbi 1.1.3.

Bad Daniel begs for forgiveness!

Wigbi 1.1.2 (.htaccess hotfix) is out

After some great feedback at my blog, I have released Wigbi 1.1.2, which contains a new wigbi/.htaccess file called wigbi/NO_MAGIC_QUOTES.htaccess

The story, in short, is that I never had any problems with Wigbi when working with it locally or hosting Wigbi-based sites at my hosting company. However, after developing a site for a friend of mine, Wigbi AJAX updates (e.g. when updating HTML content) started receive corrupted strings, where new lines were converted to \n etc. Then, one day, the same thing started happening at my hosting company. It turned out that they had enabled magic quotes.

So, in order to never let those quotes ruin another Wigbi site, I added a line to the wigbi/.htaccess file, which disabled magic quotes. The problem with this approach, however, is (which I was informed of a couple of days ago) that not all PHP installations have the magic quotes feature. For such installations, the .htaccess file in question stops working…and Wigbi does as well.

In Wigbi 1.1.2, the magic quotes wigbi/.htaccess file is separate from the original one. If you experience problems with magic quotes, just switch the .htaccess files for that server.

Disabled magic quotes

I have disabled magic quotes for Wigbi.

If the feature was disabled, Wigbi would handle AJAX posted data incorrectly.

Read more here: http://danielsaidi.wordpress.com/2010/11/24/php-the-horrible-magic-quotes/

The fix has been checked in on GitHub.