[Plugin: Advanced Post List] Maximum execution time after update

Glad you love the plugin. Sorry about the issue though. I hope you backed up your presets prior to upgrading though.

It could be a number of reasons why your getting that error. The most likely reason is that your getting hung up on something (a loop). It may be a script error, or a script getting an error from some backend code, or maybe something in constructing the settings page. Its hard to tell on my end, but you said this problem only exists on the plugin’s setting page, right?

Here’s a couple other questions…
Have you tried disabling other plugins to see if the plugin would work?
Have you tried selecting “Yes” on “Delete preset upon deactivation” and then deactivating and then reactivating the new plugin version (it should give it a fresh install)?

Just to give you an update…

I’ve been looking into the issue trying to figure out what the source could be, and it could also be host related (mainly GoDaddy). I’ve notice a lot of other people recommended modifying the php.ini file’s max_execution_time. I’m also going through the plugin and writing in some safe-guards, but I was wondering, do you know how to turn on Debug in WordPress?

Sorry I don’t have any more info on this as of yet. Spend most of the day going through the plugin and correcting some things that might be a possible issue. I should have an update available soon though.

The Debug mode in WordPress might give you an error that I can work with. It isn’t something I recommend using on a public site, but its ultimately up to you if you want to use it. A lot of the times I just create an exact copy of the site’s files and database, and then put it on a localhost (requires some code to be changed in order to make the switch though). After that, I do a step by step debug run with an IDE. The timeout error isn’t much to go by, so a lot of it is guess work, assuming it is related to the plugin.

I doubt it has something to do with the amount of categories and posts, although I can’t rule it out completely. I used a ton of categories to make up for the loss of the post type & taxonomy support in 0.2, and I didn’t encounter a timeout error while working on 0.3, but not everyone’s problem is the same.

My main worry however, whether it’s the problem or not, is the plugin’s database. Although, so far, it looks like things are good. My second main worry though is the WordPress scripting support, but the only thing that relies on scripting while loading the page is the preset database table, and nothing needed to be altered in that part of the JavaScript (still the same as you might of noticed)…but the timeout error does have a relation with scripting. Another problem is that you may need to optimize your (phpMyAdmin) database. Since it’s on the same server, its got me wondering if the database might be a lil jumbled up.

At the moment, I’m working on uploading a new beta version. There were a few things that were throwing ‘strict’ errors that I fixed up. So if you do plan on using debug mode to see if you can catch an error, I strongly advise updating to Beta 3 first, AND using it as brief as possible.

define('WP_DEBUG', true); Should be the only thing you need to add or change to get it started.

I would also recommend changing error_reporting() in <em>site name</em>/wp-admin/load-scripts.php, and, optionally, <em>site name</em>/wp-admin/load-styles.php to…
error_reporting(E_ALL | E_STRICT);, but depending on what other plugins you have, you might catch a lot of other plugin errors.

Btw, I found some problems with Activate, Deactivate, and Delete/Uninstall action hooks. So after you update to Beta 3, if you could trouble shoot it one more time by restarting it, it should work and give you a clean install to work off of. Sorry, I took a deeper look into it and also found a bug while handling the action hooks.

Ok, the next beta just got uploaded.

Is that all the error says? and it only happens on the plugin admin page?

Well, I’m kind of running out of time to explain it in my next post since i’m about to head out for the evening…but have you made any changes to the php.ini file?

That’s pretty lame. The hosting that I have you can modify the file.

Is there any way you could ask the hosting admin to grant you access to modify it? Cause it could troubleshoot your problem. If not, my guess is that they are throttling your site.

If you do plan on going to a dedicated hosting service. It would probably be a good call to make.