private183
Forum Replies Created
-
Forum: Plugins
In reply to: [Yoast SEO] 403 ForbiddenAre you sure this is SEO related? So this doesn’t happen on any other admin page?
Anyway i guess it’s related to (some security plugin using / or by yourself adding) a rule in htaccess. Did you check the file if the access to any part of the link is denied?
Forum: Plugins
In reply to: [SlimStat Analytics] IP not masked, not transformedOkay, today it does work, could it be it takes some time to do that? (i mean sure i did clean previous results before i tested it till yesterday).
And what about provider names? Or ip masking is preferably used (anyhow provider names would also need to be masked)?
Forum: Plugins
In reply to: [SlimStat Analytics] Cache and TrackAnd if i exclude the tracker? Shouldn’t it then be possible to track the get request or s.t. like that either the pages are cached?
Forum: Plugins
In reply to: [Yoast SEO] *Warning* SEO Title messed up v1.5.2I also got a problem with title, not rly exact same one – but similar since 1.5.2 (and still in 1.5.2.4): %%cf_<custom-field-name>%% doesn’t work anymore – it doesn’t read the custom field anymore but just “%%cf_<custom-field-name>%%” on every page.
Thank you, for your answer. Well that sound’s as it wouldn’t be too hard to manage.
So first i thought to use an vpn (paid one using openvpn) – i mean if i am already connected to america either it’s the east instead near washington (tested 2 available servers + 2 outside of US so at least 1 connection should have made it moreless direct/not routed somewhere “cheaper”) – at least no proxy inbetween vpn should interfere? Then i thought of my anti virus that uses a local proxy to check connections. Temporary disabling (while still in vpn) also didn’t help.
Finally i decided to tracert noc1.wordfence.com – and of ~30 routs just ~12 managed to stay in the timelimit, yet i changed it to 500. And no matter from where (VPN) i have sent the request – it stopped after “rtr3.te7-5.lw.netriver.net [69.46.33.213]”. So, what now?
And did you check the above referenced checkbox? Further after any config change at W3TC that affects server sided caching you need to purge the proper caches.
I don’t think Cloudflare has anything to do with it – in the end it’s basically just a proxy.
I also got this error – did you check the minify settings? It told me:
Minify Auto does not work properly. Try using Minify Manual instead or try another Minify cache method. You can also try a lower filename length value manually on settings page by checking “Disable the Minify Auto automatic filename test”
After i checked the above referenced box the error disappeared.
Further CSS minify somehow doesn’t work. At least for non-logged-in users as set up, meaning not only CSS but also many php files are not taken into account if i check the result-page’s source code.