MrBrian

I have all the options disabled under ‘Where to display the short URL?’, the CSS box empty, and it still places the stylesheet in the page. If you could include a check for that and not force CSS on us that would be optimal.

Same problem… Without all the fastcgi stuff. Was working fine weeks before so probably started appearing after plugin update. Should i just disable the logging? Everything seems to be working fine.

I just discovered the problem was related to the expire time i had set in the plugin. I had assumed 0 meant infinite, and instead it causes the entry to expire instantly which completely negates caching. The x-cache-engine header still doesn’t generate however.

An unrelated suggestion i have is for your plugin to check that WP_CACHE is set to true, and if not notify the user that caching is disabled. Thanks for your work on this plugin!

That does indeed fix the noise.

I have this same problem. My site still caches fine, but i get these errors flooding my error logs. In my case, I’ve tried forcing regeneration of the permalinks with no success. It appears the Post ID that it is trying to pull the permalink for doesn’t exist – the highest post id i have is 726 and all the errors reference post ids in the 10s of thousands.

PHP Warning: wp-ffpc unable to determine path from Post Permalink, post ID: 36502

I had the same problem. You need to completely remove the eaccelerator extension from loading for it to work.

Removing eaccelerator.so from my php.ini did the trick.

Experiencing exactly the same thing – stuck on file #3, mysql backup but no files, not even a folder in dropbox.

Same thing to me… not cool

A restore isn’t automated. It simply backs up the files into the folder you specify on dropbox, and the database file is located in wp-content/backups by default.

In style.css of your theme, under the “post” attribute adjust 60px to 20px or so.

Rename all the “https” to “http”. There’s an error with the SSL configuration on the server where the javascript is located, and you don’t need a secure connection for retrieving javascript.

The twenty ten theme is the default WordPress theme, and since a theme is required for WordPress to work, you can consider TwentyTen a core part of WordPress and you should not expect modifications to the core to remain after an upgrade. I do see that many people make this mistake, but the developers would have to separate the theme from WordPress and provide them as separate downloads.. which just doesn’t make sense when the theme is a required initial component. At least for now it’s not likely to change and we can only educate those to create child themes as intended.

You’ll have to link to your website or the theme’s download as we would need to see the theme’s stylesheet and the page’s html to help you.

Just rename the twentyten folder to something else, like “twentyten-mod”. Also that error is just a warning and does not always mean that the code isn’t working. Is it doing what you want?

It would be best to ask the plugin author to make it compatible with caching plugins like super cache, as it will take more than simple editing to make it work. Unless your site is heavily trafficed or you expect high bursts of traffic (like from digg), you really don’t need super cache anyway.