based on those two posts I am linking below I am interested in how the MainWP Child Report filters are working? I am testing this now on a site that comes with the Spotlight plugin for Instagram feed.
When Spotlight is installed it leads to a lot of log entries and increases the DB size (maybe impacts performance also). I don’t see those entries in Simple History plugin but MainWP Child Report plugin obviously tracks those. A filter for those logs could be added Sl-insta-media, however, I don’t know how. It’s not possible to save a filter based on Context it seems.
I tested any random other Context attribute and that worked and could be saved. But Sl-insta-media cannot. No error in the console either related to this.
However, when I try to save the same happens again - it’s not actually saved, the fields/rules are empty again. That means it looks like nothing changed on my end after updating to the pre-release version of MainWP Child Report.
One thing you can try is to open that child site in an Incognito window to avoid local browser cache, and then try adding an exclusion.
Alternatively, you can delete the local browser cache.
I’m suspecting that some relevant JavaScript files may be cached.
If you have any other with Spotlight plugin installed, please try adding an exclusion on them as well, but also in an Incognito window.
I tried to test a few more things and now I came up with something that I cannot explain yet.
I tried in Incognito Mode as you suggested. I tried on the live site + dev site. As I am more flexible in testing with the dev site, I started disabling plugins there. At some point it suddenly worked. Then I re-enabled the plugins step by step, waiting until it will break, which it never did.
I know from other troubleshootings that there are those weird situations where disabling all plugins and re-enabling all could make a difference.
However, when I tried the same at the live system it did not work. Now I try to figure out what could possibly different between dev and live - both did not work previously but now dev works / live does not.
Now it worked. I had the tab still open and tested one more time before postponing this for later. And now it suddenly worked. I cannot tell what could be different to all my previous tests, especially as I tried to test without all possible cachings.
I cannot 100% tell now if your dev version made a difference but I assume very much yes, because you could also replicate it.
I’ll share this information with the Spotlight plugin support. I assume this change will make it to one of the next plugin versions.
I’ll test view more times in the next days (remove, add, remove, add, incognito, normal, etc.) just to see if there is any valuable information to share. But I hope this is it now and I can close this myself
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
WordPress® is a registered trademark of the WordPress Foundation, and WooCommerce® is a registered trademark of WooCommerce, Inc. MainWP is an independent product and is not affiliated, associated, or endorsed by the WordPress Foundation, WooCommerce, Inc., or Automattic Inc., except where noted under the Jetpack® API and Trademark License Agreement. All product names, logos, and brands are property of their respective owners and are used for identification purposes only.
