herooftheday77
Forum Replies Created
-
Forum: Plugins
In reply to: [Cachify] Comment fields are suddenly pre-filledThank for getting back to me.
In fact, i still facing the same issues, so that i turned off the whole plugin for the moment.
Beside of that, i am trying to figuring out if cachify is anyway a good solution for my blog. (Somewhere in the docs it says cachify fits best for small – medium sized websites. but how big is medium, by the way? ?? )Using “duplicator” i cloned the whole site to a sub-directory for testing purpose. i am able to give you login details if you get in touch with me. But i am not sure if we are able to reproduce the problem here, too.
Meanwhile, i also activated APC extension on my server and i wanted to test it agains the “save to hd” option.
regards
ok,
thanks for the hint with the #rowspan# into table.
That could help, will try it.thanks again.
Forum: Plugins
In reply to: [Cachify] Comment fields are suddenly pre-filledby the way:
if i empty cache manually, the issue is also gone (for the moment).
Forum: Plugins
In reply to: [Cachify] Comment fields are suddenly pre-filledI will try to setup a staging site today.
thanks.Forum: Plugins
In reply to: [Cachify] Comment fields are suddenly pre-filledYes!
RewriteEngine On RewriteCond %{SERVER_PORT} !^443$ RewriteRule (.*) https://%{HTTP_HOST}/$1 [R=301,L] # BEGINN CACHIFY <IfModule mod_rewrite.c> # ENGINE ON RewriteEngine On # GZIP FILE <IfModule mod_mime.c> RewriteCond %{REQUEST_URI} /$ RewriteCond %{REQUEST_URI} !^/wp-admin/.* RewriteCond %{REQUEST_METHOD} !=POST RewriteCond %{QUERY_STRING} ="" RewriteCond %{HTTP_COOKIE} !(wp-postpass|wordpress_logged_in|comment_author)_ RewriteCond %{HTTP:Accept-Encoding} gzip RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/cachify/%{HTTP_HOST}%{REQUEST_URI}index.html.gz -f RewriteRule ^(.*) /wp-content/cache/cachify/%{HTTP_HOST}%{REQUEST_URI}index.html.gz [L] AddType text/html .gz AddEncoding gzip .gz </IfModule> # HTML FILE RewriteCond %{REQUEST_URI} /$ RewriteCond %{REQUEST_URI} !^/wp-admin/.* RewriteCond %{REQUEST_METHOD} !=POST RewriteCond %{QUERY_STRING} ="" RewriteCond %{HTTP_COOKIE} !(wp-postpass|wordpress_logged_in|comment_author)_ RewriteCond %{DOCUMENT_ROOT}/wp-content/cache/cachify/%{HTTP_HOST}%{REQUEST_URI}index.html -f RewriteRule ^(.*) /wp-content/cache/cachify/%{HTTP_HOST}%{REQUEST_URI}index.html [L] </IfModule> # END CACHIFY # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress
Forum: Plugins
In reply to: [Cachify] Comment fields are suddenly pre-filledsome of the plugins we are using:
antispam bee
amazon web service
WP Offload S3
clef
SSL Insecure Content Fixer
UpdraftPlus
Vafpress Post Formats UI (from theme)
Wordfence Security (not using their falcon cache engine)
Pinterest Button
WP Instagram Widget (from theme)
WP Retina 2x
Yoast SEOGoogle Analytics + Statcounter
thanks a lot for any help and / or suggestions…
Forum: Plugins
In reply to: [Cachify] Comment fields are suddenly pre-filledHi,
thanks for your reply.
yes, the issue is still there. Some of my readers told me about it just 2 days ago.
Cachify is active.
Settings are:
saves on HD
expires after 4h
new comments empty cache
no minifyI commented several times from different browsers, with and without stealt mode. You can test it here:
https://flowersonmyplate.de/schnelles-karamell-chocolate-chip-popcorn/
it can reproduce this strange behavior:
i leavea comment using IE11 in stealth mode.
i go the the same page using chrome in normale mode (and not logged in at WP) and i can see the pre-filled fields, name + email, of the visitor who leaved a comment before…I didn’t deactivated all plugins so far, since i need them on this live site (we have visitors on the page all time), but i did deactivated cachify and the issue was gone.. so, my guess…something goes wrong with the cache..but i might be wrong.
Forum: Plugins
In reply to: [StatCounter - Free Real Time Visitor Stats] StatCounter still breaks HTTPSthis would be interesting for me, too.
Since Google is watching out more and more for ssl secured websites, this is also an important SEO topic for WordPress users.
If I check my site using :
https://www.whynopadlock.com/check.php
It shows me that there is an unsecure connection to statcounter:
Insecure URL: https://c.statcounter.com/…. /…..
Is it possible to change the counter URL in WordPress manually?
I reinstalled the official StatCounter Plugin for WordPress, after i switched over to SSL but this plugin still breaks my ssl connection.
regards
Michael