Bill Dennen

There is definitely a connection to Role Scoper. I just saved some options in Role Scoper and it wiped out the contents of wp-content/cache/, including the .htaccess file.

The htaccess file was owned by root, with 644 permissions, so it’s surprising that it got wiped out.

Also, my supercache directory was wiped out too.

It seems that Role Scoper is quite aggressive in deleting files in wp-content/cache.

Still looking for advice.

I recently installed Role Scoper plugin. I noticed in its source that it has several mentions of “htacces” but I assume this means the main WP htaccess file and not this one in the cache.

(Our main htaccess file is untouched)

I did some more digging.

With FORCE_SSL_ADMIN true, since this is how we want to run it.

URL of post = https://somedomain.com/somesite/2010/10/test-2/

All of our public-facing pages are accessed over http. Backend should be https.

If I try to edit the content with the front-end-editor, I get the blank NicEdit box.

If I change the URL of the public page to https:

https://somedomain.com/somesite/2010/10/test-2/

it works! Looking for suggestions.

I think this looks great, but I a can’t speak to how scalable it is!

Thanks for replying. I guess one problem is that using

define('FORCE_SSL_LOGIN', true);

doesn’t work in the most secure way. The login page is still insecure, even though the form action is secure. So, the user does not get a “secure page” lock on the login page.

You might try this one:

https://wpebooks.com/replicator/

Thanks. I commented it out.

My plugins page says I have Version 2.9.4 installed. BUt, when I go to /wp-admin/options-general.php?page=manage_amr_ical, it says “AmR iCal Events List 3.0”.

Weird?

thanks!

Looks fine. Did you fix the problem?

This approach of adding rewritcond statements does have some advantages. Only certain requests are sent to WordPress for processing.

So, if somebody requests some wacky URL (not one being redirected to WordPress) and it’s a 404 — there’s no additional overhead of going to WordPress just to deliver a 404 page.

Ok ok. Yes, you’re right of course. Perhaps this is short-term pain, and we’ll all be happy in the end.

I’d also like to turn off mod_speling, which would solve this problem, but would create other problems.

not yet, need to reinstall/configure the plugin in our dev environment to reproduce.

There seems to be a typo in the latest version of this plugin.

Line 26 of popup.php

$forumurl = str_replace("http:", "https:", $formurl);

should be

$formurl = str_replace("http:", "https:", $formurl);

This seems to solve some problems we’ve been having.

Frederick, sure, I’ll try. ??

ha ha. Yes @andrea_r.

I had the problems with W3 total cache even when I disabled the cache via the plugin settings. The problems went away when I disabled and deleted the plugin itself! Very weird.