Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Mike Davis

    (@2dizzylizards)

    The issue seemed to be with the version of WordPress I was using. I just upgraded from 2.9.2 to the current 3.0.4 and the warning is gone. The upload path was OK, so I guess W3 Total Cache didn’t like my version of WordPress.

    All seems to be good now running WordPress 3.0.4.

    Thanks!

    Thread Starter Mike Davis

    (@2dizzylizards)

    Any news on this? Thanks!

    Thread Starter Mike Davis

    (@2dizzylizards)

    Nevermind. After extensive searching I found out how to do it.

    This order of rules within your .htaccess file is VERY important. Use the following structure when listing your rules (which means the rewrite rules go above the W3TC rules):

    Custom Rules

    W3TC Rules

    WordPress Rules

    Also, you have to use the correct rewrite code within .htaccess. The following is what I use for our MediaTemple hosting, per the MediaTemple knowledgebase. I tried another suggestion and got into a 301 redirect loop, so I went with what MediaTemple told me (funny how that works)! Note: replace “example” with your URL. Note2: I put the rewrite code within an <IfModule> as shown below per a suggestion from Frederick in another post. Not sure if this is necessary, but it seems to work, so I am leaving it.

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteCond %{HTTP_HOST} !^www\.example\.com$ [NC]
    RewriteRule ^(.*)$ http://www.example.com/$1 [L,R=301]
    </IfModule>

    Thread Starter Mike Davis

    (@2dizzylizards)

    This plug-in is displaying very weird behavior regarding this issue. Sometimes it will generate a sitemap all messed up as described in my original post. Other times, like right now, there is absolutely nothing wrong with the sitemap structure.

    Everytime I publish a new post, I hold my breath when I check to see how the plug-in chose to generate the sitemap.

    The last time it generated after publishing a new post, it was messed up. Then sometime in the next 12-24 hours it fixed itself, without me manually rebuilding the sitemap, or publishing a new post.

    Strange, to say the least.

    -Marshall

    Wow! Thanks Diggers!

    I couldn’t figure out why I couldn’t log into my WordPress.com Stats from my Dashboard. It was because I had 3rd party cookies turned of in FireFox.

    Instead of activating 3rd Party Cookies (which some will tell you is a bad thing), you can just (in the FireFox Preferences under Privacy tab) click on “Exceptions” in the Cookies section and enter “dashboard.wordpress.com” (without the quotes, of course).

    This will allow you to accept 3rd party cookies from WordPress.com so that you can log into your WordPress.com Stats account.

    Now I am happy to be able to see my stats again!

    I would like to know the outcome of this, as I am having the same problem with FireFox 3. My stats plug-in no longer allows me to log in via my blog’s dashboard in FF3.

    However, when I log into my admin area of my blog in Safari, I am able to log into my stats plug-in on the dashboard. The stats display fine in Safari.

    Any ideas why I am unable to log into the WordPress.com stats plug-in 1.2.2?

    Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)