Sarah Lewis

I’m having this problem when upgrading to 2.6.2 with Fantastico. Here’s the process that’s been consistently working for me to correct it:

1. Using FTP, rename the plugins folder (at /wp-content/plugins/) to plugins-old
2. Log in as usual
3. I am prompted to upgrade the database, so I click that button and it does
4. Rename plugins-old back to plugins
5. Log in again

Once I do that, everything seems to work.

@abidavis: It’s possible, but it’s not particularly easy. You basically have to create a plugin (or a function within the functions.php file) that intercepts the page loading process (using the template_redirect hook), have it do some conditional logic, and then serve up the appropriate page.

Someone could probably write a plugin to make it easier (for instance, provide a settings panel in the WP-Admin) but I’m not aware of existing plugin.

You might find this thread useful. It fixed the problem for me.

I was getting this error on a blog that’s password protected (it’s in development and the client doesn’t want anyone outside the organization to see it yet). I found this Trac ticket, which led me to this plugin, which worked for me.

Thanks for the feedback, hotkee. Can you confirm you tried it from a directory outside of WordPress?

For instance, my setup has WordPress in the root of the domain, and I don’t get the error if I try to include from there, but I have an “ads” subdirectory (which is the location I really need to call from) and that’s when I get the error.

I can confirm that I have standard table prefix (and it’s listed in the wp-config.php file) and no core mods at all.

You have to install the Post-Plugin Library first. I learned that this morning. ??

Oops, just realized this is because I forgot to reinstall the Post-Plugin Library after an auto-update of it failed. I installed it and all is well.

I’m getting the same error on activation.

Running into the same thing. Pulling the include from the same directory (root of the blog) seems to work, though.

Thanks so much for the quick fix! Works like a charm.

My reasons for wanting a hook are different from yours, but the Widget Logic plugin gave me exactly what I needed with its optional widget_content filter.

(In my case, I need to do some different styling on the first word of the widget title, so I used the filter to parse and wrap in the appropriate class.)

Thanks for mentioning this. We’re looking into it and will do our best to fix. I’ll update here when we have a new version.

I’m glad the fix worked! In this case, it was a simple oversight on my part (and it affected other widgets, so I quickly got details about what was going wrong).

I’m not sure that there’s anything that can be done to prevent it, but really appreciate you letting me know; that’s the best way to help it not be a problem.

Since the fix worked, I’d be grateful if you would mark this issue as resolved. ??

Thanks again for the feedback!

I think we’ve got this issue tracked down. The newest version should avoid the problem; let me know if it doesn’t!

I’m using some code found on Andy’s site to do a variation of this on my site. Might be worth a look if you’re still wondering.