Mike Clarke
Forum Replies Created
-
Forum: Plugins
In reply to: [Tabby Responsive Tabs] Problem with target URLsWell it was embarrassingly simple after I tracked it down to being a cache issue.
The utm_* parameters are google analytics campaign parameters and we’re using the Wp Fastest Cache plugin. Normally URL’s with query strings are not cached but the situation is different for the URLs which contain google analytics parameters. If a URL contains any google analytics parameters such as utm_source, utm_medium, utm_campaign, utm_term, utm_content, the parameters are ignored and the URL is served via the page cache.
Our cache is configured to not cache pages for logged in users so that developers will always see the effects of their software edits. This is why I was seeing the target tab when I was logged in but visitors who were not logged in were served the cached page which has the first tab opened.instead of the target.
Selecting the cache option to exclude URLs with Google Analytics parameters solved the problem
Forum: Plugins
In reply to: [Tabby Responsive Tabs] Problem with target URLsThanks for the suggestions.
Many of our plugins are essential for normal operation of our site so I shall have to do some testing on the development version when time permits. One thing that I have now noticed that the problem doesn’t affect users who are logged in – debugging this is going to be ‘interesting’.
Forum: Plugins
In reply to: [Optimize Database after Deleting Revisions] Unable to view log fileThe log file was deleted again last night with the upgrade to version 4.5.
I’m using the scheduler. I tried switching to NOT SCHEDULED, and then back to weekly but it made no difference and there were still no buttons for viewing and deleting the log file.
I’ve restored the log file from the backup and all is working correctly again.
Would it be possible to arrange for the log file to be retained across upgrades instead of being lost. Perhaps it would be better to store the results as a serialized 2 dimensional array in wp_options instead of keeping a log file in the plugin directory.
Forum: Plugins
In reply to: [Optimize Database after Deleting Revisions] Unable to view log file/wp-content/plugins/rvg-optimize-database/logs/ was empty.
On checking the backups I can see that rvg-optimize-db-log.html existed in that directory at 23:10 on January 6th but the directory was empty at 05:10 on January 7th.
Could it be that the file was deleted in the course of the upgrade from 4.4.2 to 4.4.3 at 01:01 on January 7th ?
I’ve restored rvg-optimize-db-log.html from the backup and the buttons for viewing and deleting the logfile are now visible and working. I’ve run a manual optimisation and confirmed that the results were appended to the logfile.
Forum: Plugins
In reply to: [Optimize Database after Deleting Revisions] Unable to view log fileThat looks like what I .used to see but now there’s no buttons for viewing or deleting the log file.
Here’s what I see:
https://drive.google.com/file/d/13sTJiHcChIi3cjmM9EGmDQXD-jDWOa_t/view?usp=drive_webWell it’s run for a few days now and survived two upgrades without dropping into learning mode. Looks like Sod’s law applies and things won’t go wrong when you want them to.
If the problem arises again I should be able to produce “before” and “after” copies of the contents of wflogs because I’ve set up a cron job to retain periodic backups of it.
It would be useful if I could make the cron job check to see if learning mode had been activated. Is there some value I could check in a config file or the database?
This time he WAF survived the upgrade without reverting to learning mode.
I’ve got a feeling that the previous instances of switching to learning mode might have been dependent on timing relative to the daily wordfence_daily_cron run. I’ll have another attempt and try to time things so that the cron job “sees” the change in version. This might take two or three days but I’ll get back to you when I have more info.
The previous times this happened there had been a time lag between the upgrade and dropping into learning mode suggesting that it might be happening when a cron job ran after the upgrade so I’d left things to follow their own courses.
Wordfence has upgraded itself and the WAF is still fully enabled so I’ll leave things as they are until tomorrow and see what happens overnight.
OK, I’ve rolled back to 6.3.14. I will wait to see what happens after Wordfence auto updates and get back to you with the results.
I don’t think the “Restrict auto update” plugin will have had any effect. It just adds a filter based on an example in the codex to prevent one of our installed plugins being auto updated – this was needed because we’ve made some local customisations to that particular plugin.
bash-3.2$ ls -l wp-content/wflogs/
total 228
-rw-rw—- 1 sedbergh1 83005 40083 Jul 27 21:25 attack-data.php
-rw-rw—- 1 sedbergh1 83005 8302 Jul 27 21:27 config.php
-rw-rw—- 1 sedbergh1 83005 51 Jul 27 20:19 ips.php
-rw-rw-r– 1 sedbergh1 83005 101240 Jul 18 07:08 rules.php
-rw-rw—- 1 sedbergh1 83005 44202 Jul 18 07:08 wafRules.rules
bash-3.2$I’ve emailed the diagnostics to you.
It looks like this could be related to updating Wordfence.
Wordfence was automatically updated to 6.3.15 yesterday and the WAF is back in learning mode again today..
The firewall has remained in fully enabled mode subsequent to me switching learning mode off.
No other config.tmp have remained in the wflogs directory.
Here’s the current directory listing:
-rw-rw—- 1 sedbergh1 83005 40083 Jun 8 06:39 attack-data.php
-rw-rw—- 1 sedbergh1 83005 639417 Jun 8 10:03 config.php
-rw-rw—- 1 sedbergh1 83005 51 Jun 8 08:45 ips.php
-rw-rw-r– 1 sedbergh1 83005 101240 Jun 6 07:04 rules.php
-rw-rw—- 1 sedbergh1 83005 44202 Jun 6 07:04 wafRules.rulesI have Apache access logs for the last month but no Apache error logs. It might be possible that my hosting provider could extract data from the error logs for me but the most recent config.tmp.* file is dated March 10th so I doubt if they’d have records going back as far as that.
Looks like I should just delete the config.tmp.* files and keep an eye on wflogs to see if any more appear.
Here’s the current contents of wflogs:
bash-3.2$ cd wp-content/wflogs/
bash-3.2$ ls -lt
total 1348
———- 1 sedbergh1 83005 0 Oct 23 2033 config.tmp.VxFzcR
-rw-rw—- 1 sedbergh1 83005 635016 May 22 11:31 config.php
-rw-rw—- 1 sedbergh1 83005 51 May 22 10:30 ips.php
-rw-rw—- 1 sedbergh1 83005 40083 May 22 04:38 attack-data.php
-rw-rw—- 1 sedbergh1 83005 44202 May 14 13:46 wafRules.rules
-rw-rw-r– 1 sedbergh1 83005 101240 May 14 13:46 rules.php
-rw-rw—- 1 sedbergh1 83005 349568 Mar 10 17:35 config.tmp.84qAjH
-rw-rw—- 1 sedbergh1 83005 98287 Jan 17 20:11 config.tmp.K4kCVJ
-rw——- 1 sedbergh1 83005 827 Jun 17 2016 config.tmp.arVpPP
-rw-r—– 1 sedbergh1 83005 824 Jun 17 2016 config.tmp.QupnEpSome of the files predate the time when learning mode was switched on (16/05/2017, 19:34:02) so it doesn’t look as though the wflogs folder had been deleted. But I’m rather suspicious of config.tmp.VxFzcR which is dated several years into the future.
I’ve resolved the issue of the IP address for the request not matching the IP the user logged in from. He was using a laptop and moved from one location to another between logging in and uploading some files. At the second location he connected through a different ISP.
I’m confident that my site hasn’t been compromised, daily Wordfence scans are all clean and Gravityscan results don’t show any cause for concern.
Forum: Plugins
In reply to: [WP Fastest Cache - WordPress Cache Plugin] Deleted post remains in cacheThanks. It’s working fine now.