Jay
Forum Replies Created
-
Any update?
It’s Wp-Admin -> Users.
Thanks for the quick response! Appreciate it 🙂
You can ignore responding to the below question since it may not have directly anything to do with the question raised.
How would we make sure that the API endpoint is not left open and can be triggered only at the system’s end? Basically, since it’s a JS AJAX call, how would it be more secure?
Below was the response from WP Rocket’s team:
Your implementation is not compatible with caching. PHP and MySQL processes don’t run on cached pages.
It will run only for the first time cache is created. Same with cache for logged in Users.These articles give a good overview:
Does WP Rocket Support Fragment Caching?
Caching for WordPress, Explained in Plain EnglishTo verify, that page caching is the culprit, you can install this helper plugin Disable Page Caching For Logged-In Users that will disable page caching for logged-in users but will preserve optimization.
You should clear cache after installing the helper plugin.If the logs start working after that, this means page caching is indeed the culprit.
This helper plugin will “resolve” the issue with logs when user is logged-in, but you will need to decide if you prefer to keep page caching or the custom logs.Let me know if you need any further assistance, I am happy to help. 🙂
This is the plugin that we are using.
https://wordpress.org/plugins/miniorange-saml-20-single-sign-on/
Hi there,
Thanks for your response.
I was able to figure it out on my own, eventually.
Regards,
Jay.Hi Champ Camba,
I’ve the same query.
And I’ve tried adding the code in functions.php, as well as ultimate-member.php, but the message doesn’t change.
Do let me know how to go ahead about the same.
Thanks,
Jay.Also, wanted to check if there is a way to export the data from Dashboard->Simple History because I can see no export filters under Settings->Simple History.
Not to mention that I have overridden the 60 days rule to make sure that the older data does not get deleted from the database.
As of now, my exported simple history CSV file size is around 70 mb, and taking way too much time to get it exported.
And thus looking for an alternative in a way of running a SQL query.
It semes like a conflict with either other plugins or theme itself.
I’ve tried using the same 2.1.6 version of Ultimate Member plugin with a fresh installation of WordPress and it is working fine.
Thank you for clarifying the issues.
Thanks Towhid, I will check it out and let you know.
Appreciate your response.
Seems like the issue is still not resolved. The different issue I was facing had gotten resolved when I switched themes. And not the menu problem.
The issue seems to have been resolved, at least for now, when I switched back to a different theme and then back to the original theme.
Don’t know the root cause of it.
The only thing that I can relate is updating the WordPress version from 5.4.1 to 5.4.2.
Possible conflict with WordPress update?
Same with one of my website as well.