• YIKES! I downloaded and activated the plug with this message:

    A custom url or permalink structure is required for this plugin to work correctly. Please go to the Permalinks Options Page to configure your permalinks.

    Warning! /home/dbistrow/public_html/wp-content is writeable!
    You should change the permissions on /home/dbistrow/public_html/wp-content and make it more restrictive. Use your ftp client, or the following command to fix things:chmod 755 /home/dbistrow/public_html/wp-content/

    This is a WP blog with over 3,000 posts and I’m not sure what “custom structure” permalink I should make and how that would affect my daily blogging. There is only one user and no registration available for this blog.

    Thanks for any constructive help.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Just set it to the default, yyyy/dd/postname works well.

    Thread Starter Don Anastas

    (@javaman1)

    Just set it to the default, yyyy

    I’m not sure what you meant exactly. I did lower the permissions in the public folder and the warning went away.

    I suppose I’ll wait and see if there is an improvement. I’ve also written to my host to see if they might help or offer some suggestions.

    I may wish to compress files later.

    Thanks.

    Go to Settings->permalinks and you’ll see all your options.

    Thread Starter Don Anastas

    (@javaman1)

    I got most of this working. A redirect plugin is also installed. My permalinks change to reflect real filenames.

    At the bottom of my WP Super Cache is this message:

    Trailing slash check required.

    It looks like your blog has URLs that end with a “/”. Unfortunately since you installed this plugin a duplicate content bug has been found where URLs not ending in a “/” end serve the same content as those with the “/” and do not redirect to the proper URL. To fix, you must edit your .htaccess file and add these two rules to the two groups of Super Cache rules:

    RewriteCond %{REQUEST_URI} !^.*[^/] %{REQUEST_URI} !^.*//.*$
    You can see where the rules go and examine the complete rules by clicking the “View mod_rewrite rules” link below.

    My htaccess file looks like the one in the view mod_rewrite rules and I added the cold offered in the warning and this sent the whole website down, therefore, I removed it.

    I’m not sure exactly where that code “RewriteCond %{REQUEST_URI} !^.*[^/] %{REQUEST_URI} !^.*//.*$” belonbs as something very similar already exists as follows:

    RewriteCond %{REQUEST_URI} !^.*[^/]$
    RewriteCond %{REQUEST_URI} !^.*//.*$

    This seems to be the only to complete at this point.

    Thank you, Don

    Thread Starter Don Anastas

    (@javaman1)

    I believe it’s working now. The only thing left is to ensure the redirect works.

    Thanks again.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘[Plugin: WP Super Cache] Error message and warning’ is closed to new replies.