Today I am releasing updated versions of my Page Restrict, Lightview JS and Shadowbox JS WordPress plugins.
New to the Page Restrict plugin is moving the content required for the admin pages into another file and including it only when in the admin portion of your site so that it isn’t even loaded into memory during normal site views.
New to the Lightview JS plugin is support for the [ gallery] shortcode.
New to the Shadowbox JS plugin is support for the [ gallery] shortcode.
Enjoy!
I have a question for all of the users out there who are using the Shadowbox JS and Lightview JS WordPress plugins.
Would you prefer the plugin to automatically add the activator attributes to the links for Shadowbox and Lightview respectively, rather than having to manually add it to your links?
I am one of those people who believe that more flexibility is a better feature than ease of use by less typing.
With that being said I could see a situation where one would simply want to use Shadowbox or Lightview for all of their image links and where adding the activator attributes to the links would become tiresome.
Perhaps a good compromise would be to add functionality to either enable or disable global activation on image links? Perhaps making global activation the default would be beneficial?
I think I have already talked myself into adding this functionality but I would still like to hear some user feedback, so tell me what you think.
I have been helping a friend setup a dedicated server to host his clients sites on and wanted to make things as streamlined and as easy as possible. To do so I installed Apache 2.2, PHP5, XCache and mod_fcgid. I am using suexec with Apache to run the scripts as the users who own the scripts.
I wanted to verify that XCache was working, so I copied the XCache admin directory into one of the document roots and tried to login. To my surprise I was not able to login even though I was using a known good md5 password hash in the XCache configuration.
It took me about a month of searching to find out that the server variables PHP_AUTH_USER and PHP_AUTH_PW don’t seem to work with mod_fcgid. This Lighttpd forum entry led me to the XCache admin config.php.
Here is what is required:
In this file add the following, using the information you provided in the XCache configuration:
<?php $_SERVER[‘PHP_AUTH_USER’] = ‘admin_username’; $_SERVER[‘PHP_AUTH_PW’] = ‘admin_password’; ?>
Configure some other means of authentication such as htpasswd or htdigest
For some time now I have been trying to manage support for my WordPress plugins in the comments here or via email. I have quickly found that it becomes unmanageable and the comments become overwhelming.
To alleviate the pain of supporting my plugins via this manner I have added a support forum. All WordPress plugin support discussions should be entered at the new support forum. I have enabled comment moderation here now so that support discussions no longer make it into the comments. These instructions are provided in the comment field on all pages.
So if you here to ask a support question for a WordPress plugin please head over to http://forum.sivel.net/.
A link to the forum also appears in the navigation bar on the upper right of this site.
The AJAXify FAQ-Tastic WordPress Plugin has been updated to version 0.3. New to this update is WordPress 2.6 compatibility. See the Change Log for changes. Enjoy!
The Lightview JS WordPress Plugin has been updated to version 0.3. New to this update is WordPress 2.6 compatibility. See the Change Log for changes. Enjoy!
The Shadowbox JS WordPress Plugin has been updated to version 2.0. New to this update is shadowbox.js 2.0,calling javascript libraries when available from Yahoo and Google APIs and WordPress 2.6 compatibility. See the Change Log for changes. Enjoy!
A few weeks ago I posted that I would be going out to the LinuxWorld Expo in San Francisco. Yesterday I made my appearance, and took the time to talk to the guys at Haiku for a good while. They seemed to get the idea that I flew out here just to see their booth…Perhaps I may have actually said that.
Anyway, they took a picture and claimed that it would be on the Haiku website by the following day (today). And not really to my surprise, but I’ll say that I am, my picture is indeed there.
See the section titled “Interest still strong”.
While using checkgmail on Ubuntu 7.10 I was running checkgmail with no problem at all. I not too long ago upgraded to Ubuntu 8.04 and quickly noticed that checkgmail was taking 30+ seconds to start and was taking 100% of my CPU.
I did a search on Google and found a lot of users experiencing the same problem. It took a bit of reading, which is why I am posting this, and found that it is do the localizations (languages) that are loaded into checkgmail. There are 1,728 lines in checkgmail devoted to localization and I imagine that it is due to parsing this data that is causing the 100% CPU useage.
The solution to speeding up checkgmail is to remove all of the localizations that you don’t need. For me this was removing lines 3089-3280 and 3346-4817 or checkgmail and the corresponding lines in ~/.checkgmail/lang.xml.
I have created some patches to take care of this but cannot guarantee that with updates to the code that the localizations will remain on the same lines as they are this minute. So use with care. The patches can be applied as such:
wget http://sivel.net/patch/checkgmail/checkgmail_1.13svn_slowstart_checkgmail_en.patch
wget http://sivel.net/patch/checkgmail/checkgmail_1.13svn_slowstart_langxml_en.patch
patch /usr/bin/checkgmail checkgmail_1.13svn_slowstart_checkgmail_en.patch
patch ~/.checkgmail/lang.xml checkgmail_1.13svn_slowstart_langxml_en.patch
If you have checkgmail running kill it and start it up again. It should have started almost instantly and not taken 100% CPU to do so.
In a recent post I said that I wanted to release updates to all of my plugins for WordPress 2.6 compatibility at one time. But I have been busy on some other things and haven’t given my plugins the attention they need. So I’m going to release updates as I get time. To start I am releasing an update to the Polaroid on the Fly WordPress Plugin. See the change log for changes.