notorioushttp

Thx Tosaha. I’ve just run into this issue as well. I wish the author of the plugin would have a look at this and fix it.

Wouldn’t it be great if we could register issues directly on the plugin? Drupal has that. So the number of open and closed issues and bugs can help you decide whether you want to look into using this plugin.

OK, this is still a problem. I’m getting Internal Server Error 500 pages, and it’s freaking me out. I’ve tried a number of things:

– Overwrote all WP files
I uploaded a fresh zip of 3.1.2, and unzipped it in situ, rather than FTPing it up file by file.

– Updated wp-config.php file
I commented out the SECRET_KEY define, and added the WP_DEBUG one. This just made things worse: now the dashboard 500ed. I reversed the changes, but the dashboard still 500ed. (wtf?)

– Started a fresh install in a new directory
Created a new subdomain on a separate domain I had hanging around, and pointed it to this directory. Copied the wp-config over, so it would point at the same DB. But the directory and domain info are in the DB, so it keeps going back to the original directory.

– Changed main domain to point to new directory
OK, it now works, mostly. On the dashboard I’ve got the Right Now, Recent Comments, Quick Press and Recent Drafts blocks showing up properly. The WordPress Development Blog block shows nothing inside; and the Incoming Links, Plugins and Other WordPress News blocks just say “Loading…”.

I could use some help here. If you’ve seen this sort of behaviour, or have some insight, I’d be grateful for some direction.

Thanks for your help,
– AAA

Thx Samuel B for the quick response.

I deactivated WordPress Stats, and installed Jetpack. Now I keep getting an Error 500 page on the dashboard, and the Jetpack draws the chrome of the page then nothing inside (no data).

I’m thinking I’d like to start the WP install from scratch. Is there some plugin that migrates posts and pages from one install to another?

Thx,
– AAA

OK, here’s what happened. I upgraded from 2.7.1 to 2.8.4 on my dev box. It went well. I committed the changes to Subversion, and updated the blog on our staging server. That’s when I got the error.

I found another post on this forum referencing the missing file. It said all the files hadn’t been copied over. The penny dropped: there were some new files in the update on dev, which weren’t versioned in Subversion; so they didn’t get copied to staging.

I went through the blog directory adding any unversioned files to the repo. Commit on dev. Update on staging, and all is better.

When I updated on prod it went smoothly.

I got the same issue. *VERY* disappointed no one has helped you out on this. Googling the error brings up a metric assload of other sites with the same error. Some of them are STILL stuck with this.

Have you been able to resolve the issue?

Otto42: My apologies. I tried your solution and it worked like a charm! All links are based on my local domain.

Thanks!!

BTW, where is this documented?

I think the bloginfo_url filter is what I need for this. I’m wondering: do I have to create a plugin to use this, or can I use it from my theme?

Thx for the responses guys. I’ve been doing some Codex diving and it’s looking like the filters might be just what I’m looking for. If anyone has suggestions on this, I’d be grateful for some direction.

So, I had an idea. But there are some issues, and I’m hoping someone can help out with that.

If there are nop other ways to do what I need, perhaps I can lift the domain name (i.e. https://wpdev.com/) from my ENVIRONMENT file (in my framework every serving directory has an ENVIRONMENT file which specifies certain configuration settings. These files do not go in the repository, and must be configured on each server, and in each directory.)

Then I can tweak the bloginfo(‘url’) function to return the ENV domain name rather than the one from the DB.

The problem comes when we want to update WP. These changes will get creamed by the update.

So come on, is there another way to do this?

Thx for your help.
– AAA