Geeklog Forums

I have five Geeklog installations. Four of these are Geeklog 1.3.7 sites. (The other one is 1.3.6) On two of the Geeklog 1.3.7 sites I cannot access the admin/plugin.php. There is no error message and no entry in the error log. The browser times out after several minutes. On the other two Geeklog 1.3.7 sites I have no difficulty accessing admin/plugin.php. One of the "bad" sites was just upgraded from 1.3.6 to 1.3.7. The other "bad" site was a clean install 1.3.7. All of the plugins are working without error and there is no other problem accessing any other admin functions.As far as I can tell there is no common plugin in the "bad" sites that is not in the "good" sites. There is no other common "bad" feature in the "bad" sites that is not in the "good" sites. I tried copying over admin/plugins.php from a 1.3.7 site that is working. No effect. Any ideas on how to troubleshoot this problem?

On the sites where it times out, do you have any plugins that are not installed yet? I.e. you have the files for the plugins in their proper places but the plugin has not been installed. As of Geeklog 1.3.7, plugins that have not been installed yet will be listed on the plugin menu so that they can be installed by simply following a link (instead of having to type the URL into the browser's address bar). Maybe something is going wrong there? bye, Dirk

No, there are no uninstalled plugins. All plugins are installed and all plugins are working. One site where admin/plugins.php is unresponsive has six plugins installed. The other unresponsive site has two plugins installed. The only common plugin between the two is the stats plugin (using a name other than stats). However, ALL five of my Geeklog sites have the same code installed for stats and I have no problem on three of the five sites. Here's what I've tried so far: 1. Copied a copy of admin/plugins.php from a good site to an unresponsive site. 2. Changed gl_plugins value for pi_enabled from 1 to 0 for all plugins. (Did this on the site with only two plugins.) 3. Emptied the gl_plugins table. (Site then showed no plugins installed in the Admin Only list.) 4. Restored the gl_plugins table content. None of these steps fixed the problem. All plugins work. There are no errors reported in the error log. No errors are reported in the browser. But when you attempt to access admin/plugins.php nothing happens until the browser finally gets bored and reports the page unreachable. Any ideas on how to debug this?

There are two ways you can go about debugging this. 1) Eliminate things until it works and then add things back until it breaks. On a site that works turn off all plugins -- see if you can access the page. If not try reverting back to the 1.3.6 version of the plugin page. If that works then you can be fairly confident the page is the problem, if not then something else. 2) Once you find a general area like say it is the plugin page then start debugging with COM_errorLog statements and see where in the code it bombs. You might also check for a variable collision at this point. Let me know If you need any more help. TomW

Commenting out the call to show_newplugins() at the end of the function listplugins() in admin/plugins.php "fixes" the problem. If I have time later I'll look into what is going wrong in show_newplugins(). The problem in show_newplugins() occurs before the call to the template, because I do not have the necessary template in my themes and I'm not getting an error message about the template not being found.

The problem with admin/plugins.php and the show_newplugins function was caused by having extra folders in geeklog/plugins/ directory. Here's how this happens on my sites: When I upgrade a plugin I disable the plugin and then I rename the three folders associated with the plugin. I then upload the three new folders. This allows me a quick way to restore the earlier version by simply deleting the new folders and renaming the old. As a result, the geeklog/plugins directory on two of my five sites contains folders of earlier plugin versions. These are most often named 1.1.beta.pluginname. The show_newplugins tries to examine the contents of geeklog/plugins directory and is unable to deal with this junk. Removing the old directories "fixes" the show_newplugins problem. At this point I do not have any uninstalled plugins in these directories.