cent

Hi Mohammad,

I noticed that afterwards. Is there a reason the JSON response doesn’t include the full post permalink but just the GUID link? Also is there a way to include the featured image URL in the response?

If you move your site contents from one domain name to another, FB likes will not follow those posts as people like a URL and if that URL changes, etc. You can pass an old URL to twitter and it will maintain the social count.

Its not a WP problem.

Hi Michael,

Coincident perhaps that you’re issue was related to the DB Cache plugin. The problem I was having appears to have been related to the WP Supercache plugin and may be similar. I switched to W3 Cache and using Memcache instead of file cache and my problem has seem to went away as well. However, for me its perhaps too early to tell as the problem doesn’t seem to have predictably. So far its working fine. I’ll give it another few more days before saying for sure on my end.

Best,
Cent

Hi Esmi,

Thats whats odd. Same theme and same set of plugins (actually cloned from each other) which are 100% identical doesn’t cause the issue to happen on the other sites.

I’ll try resetting the plugins folder and deactivating a small group of plugins at a time.

Thanks for the suggestions.

Is this a first? Any suggestions is greatly appreciated.

Hey Donncha,

As this may have been covered before, do you have a shortlist of plugins where you’ve seen this happen? Not to throw another dev under a bus, but ultimately using Supercache is more important than any other plugin on high traffic sites. Alternatively, is there something that I can search for to find the culprit? Understandably if its not WPSC that is the issue or part of the issue, any help is even more appreciated.

Best,
Cent

A Wootheme was loading JS code for their buttons in the left sidebar of the admin that was causing the conflict with WP Post Add/Edit page. Changing to a different template, fixed the problem immediately. Switching back to the Wootheme, brought the problem back. I don’t believe its related to their theme itself, but just some code they’re running on the admin screen.

I commented out a woothemes_add_javascript and the admin is working again. Broke the JS on the blog, but its an easy fix.

Looking further… there is something conflicting with JS on the post add/edit page. JS works every where else in the admin once I added: define( ‘CONCATENATE_SCRIPTS’, false ); to the wp-config file.

It appears that no JS is running in WP admin area. Tried under Safari and Firefox. Nothing JS related is even being triggered.

Just had this same problem happen to me. No DB issues, no apache issues. Worked in Safari (logged in as the admin) but not FF (not logged in). Cleared WP Supercache and it came back up. I believe WP Super Cache doesn’t attempt to cache the page for logged in users or the admin which would explain why it worked in Safari but not in FF. Still need to investigate this.

However, in case anyone might have a similar problem hope this helps.

Hi… What’s was the solution to this or what plugin was causing the problem? We have a similar issue.

The warning message above just indicates that PHP errors are displayed. If you turn off php error messages and let the header redirect happen which it cant since the header is already sent, you can see where its suppose to go.

Forgot to mention… using the WP 2.5 default theme although I’ve made CSS changes. Nothing was touched in the actual PHP files though.

I think I may have found a solution to add the Blogger post ID as an HTML comment proceeding the actual body of the post with WordPress 2.2.1’s Blogger Import. Testing it now… will post in the next 30 mins if there hasn’t been a solution. As I searched Google and the forums here, there didn’t seem to be one so I wrote one.

Best,
Cent

Also noticed that if I post a comment to an entry, I get a blank page (although the actual comment does get saved)… if I reload the page (w/ post) I get a message back saying there’s already a comment saved. if I revisit the original entry, I see my comment at the bottom.

not sure if that helps or not.