wagerrard

Esmi, I’m not in the habit of retaining empty posts.

Got it working.

I’m on a VPS.

Buried in the vendor’s httpd.conf file for my Apache is a directive that, to paraphrase, says “ignore .htaccess files.”

I commented that out. re-installed the latest version, and we’re all happy.

Re: www — Thought as much, but hadn’t noticed that on previous versions.

No visitors yet, presumably. Nothing here so far.

I haven’t checked “no cache for logged in users”, and I checked for caching after logging out.

Odd. It’s not producing any error messages, just not any cached files, either.

I just tried yesterday’s release, 0.9.4.3, as well as 0.9.4.1 and 0.9.3. Same behavior.

This is on a VPS that runs OpenSolaris. Does the code make any assumptions about the platform it’s on? I’d successfully used 0.9.3 on a shared server, also on OpenSolaris, which points, unhappily, in the direction of something in the configuration of the VPS. (E.g.: I had to ssh in as root to delete the cache directory, on each version. My FTP tool was happy to remove the two PHP files. Also, the installed permissions on Cache and the two php files were 644 on some versions, and 755 on others.)

Anyway, thanks again for the effort you put into filling an obvious void in WP’s capabilities. Caching ought to be an opt-in alternative.

OK, I saw this again on a third, and brand new, WP install.

All plugins were deactivated except Supercache. I was warned to set permission on wp-content to 777. I was warned to add th wp-cache line to wp-config.

in setting, I used full on and compression. All other options remained at default. Both .htaccess files were either amended or created correctly.

Advanced-cache.php and wp-cache-config. php were created in wp-content, as was the “Cache” directory. Inside the Cache directory is an emtpty “Blog” directory. (What’s it for?)

Everything created by supercache is owned by www and in the www group.

I logged out and repeated brought up index.php and the two pages I created. Cached files were not created.

Fixed.

I’d included in my header javascript intended to thwart other sites from displaying my site in a frame. Here’s the code”

`<script type=”text/javascript”>
if (top !== self) {
alert(‘The URL ‘+self.location.href+’ cannot be viewed inside a frame. You will be redirected.’);
top.location.href = self.location.href;
}
</script>’

If you put this code in your header and then try to preview, you’ll see the message about “….cannot be viewed in a frame.”

Remove the code snippet, and all is well.

More…

The second time I moved the theme folder from the host server back down to my development, I saw the same behavior there. Perhaps something went awry in the original transfer up, although the transfer was done as ASCII and a quick look shows nothing unusual in the files.

I then moved a backup folder from the development server to my host’s sever, and was able to preview and activate the files. These files are identical to the others.

Contrary to some reports I’ve seen here and elsewhere pointing to this as the reason theme will not preview and activate, the new folder — the one that reviews and activates correctly — contains a space in its name.

donncha, thanks for working through this. Apologies for what must have been my mistake with the development release.

Pretty sure I had the development release. I pulled it down from the link on the download page. Gremlins, maybe.

Nonetheless, I deactivated, deleted, and reinstalled and all seems well. Advanced-cache.php matches what’s in the trunk.

Thanks.

donncha, commenting out that line does eliminate the error display and allows new posts to publish. You’ll have to help me with the REQUEST_URI bit, though. I’m not a coder. If I should see it in advanced-cache.php, though, its not there.

My settings: ON (Cache and Super Cache enabled), Cache rebuild on, compression on. The rest is the default.

Thanks very much for the plugin and the attention to it. My site’s on a shared server and being able to serve static pages is a very good thing indeed.

Donncha, I tweaked the permissions on advanced-cache.php from 644 to 777 and twiddled with the admin page, as well as just deleting the file. I got the same failure to post error I mentioned earlier, claiming that wp-cache-phase1.php isn’t where its supposed to be.

Ditto when I installed the development release.

The posts in question are saved as drafts and will subsequently publish successfully.

For the record, I’ve seen no opendirs messages.

OK, I slapped myself and viewed the source of the error page WP showed me when i tried to post. In there I found this:

“<!– WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! –>

That’s from advanced-cache.php

However, the path in the code is correct. Here it is:

`if( !include_once( ‘/users/home/wagerrard/web/public/wp-content/plugins/wp-super-cache/’ . ‘wp-cache-phase1.php’ ) ) register_shutdown_function( ‘wpcache_broken_message’ );’

Umm, it’s this one that’s broken: Download

That’s referenced by the download link on Donncha’s site.

I’m far from an expert, but…

Have you reinstalled Super Cache?

if it’s installed, does .htaccess exist and is it configured correctly? Are advanced-cache.php and cache-config.php in wp-content?

I was not able to post this to support because neither of the blogs involved are wordpress.com sites.

That said, this is obviously a wp.com issue.

I have two wp.com accounts, but no wp.com site::

1. dayoldpie; [email protected]
2. wagerrard; [email protected]

Two self-hosted WP blogs are associated with dayoldpie:

1. https://www.distanttarget.com
2. constanttarget.com

Note: distanttarget.com no longer exists.

I want to do two things:

1. Delete distanttarget.com. Because that site no longer exists, there is no wp-admin page available to enable the deletion.

2. Dis-associate constanttarget.com from the dayoldpie account and associate it with the wagerrard account.

I want to use the API key associated with the wagerrard account with the stats plugin.

FYI: The Aksmet plugin didn’t reject that key.

Possible?