ready_paul
Forum Replies Created
-
Forum: Everything else WordPress
In reply to: Balantfromsun Hack / InjectionI have reported as requested in your link.
Forum: Everything else WordPress
In reply to: Balantfromsun Hack / InjectionHi Steve,
Thanks, I thought it might help people fix sites quickly rather than go through the same amount of time I had to go through to fix and therefore risk further damage.
I assume you will delete this post but thanks for letting me know.
Hi Alim,
I will do that asap but in the meantime and in LIB/UI/crm_metaboxes.php
R
Thanks Maria,
I’ll leave my hack in place and perform manual updates of WP-CRM for now as the client will just get annoyed at having to do that each time.
Hi Maria,
Latest Version of WP-CRM and Latest Version of WP.
The process to create the issue is.
1: Add user via WP-CRM filling fields required.
2: Once you select save button, the Toggle settings under Special Actions opens and asks to enter a PW twice. SEE crm_metaboxes.php for the coding for this.
3: Also, if you try and update an existing user the above happens each time asking to add a Password for the user.You can see this function in crm_metaboxes.php
Paul
Hi Maria,
Sorry but nothing to do with other plugins. Tested for that as part of any troubleshooting and prior to posting here.
The FIX:
I had to hack out the <div class=”minor-publishing-actions”>…</div> from crm_metaboxes.php to fix.Of course I will have to do this on all updates if you are not going to address the issue.
Thanks,
Paul
Forum: Plugins
In reply to: [WP Fastest Cache] Several Bugs / issuesThanks to Emre’s great support this issue is now resolved.
I now consider this to be probably the best caching plugin available if you just need simple fast caching of your WordPress site.
Forum: Plugins
In reply to: [WP Fastest Cache] Several Bugs / issuesClients and Website editors update Widgets all the time. If the cache does not clear when they update then the site will show old content.
So that is why EDITORS have to have the ability to manually delete the cache.
This will also fix the issue where the Posts and pages are not cleared on some hosts. i..e https://www.lcn.com because EDITORS can then manually clear the cache after they update a PAGE, POST or WIDGET.
Forum: Plugins
In reply to: [WP Fastest Cache] Several Bugs / issuesYou Said: The cache are not cleared after widget update.
That is why the Ability for an EDITOR to Delete the Cache is required.
Forum: Plugins
In reply to: [WP Fastest Cache] Several Bugs / issuesIt is not the browser cache.
It is a plugin issue with some hosts. Mainly https://www.lcn.com
All I need is the ability to ALLOW Editors to clear / delete the cache.
Forum: Plugins
In reply to: [WP Fastest Cache] Several Bugs / issuesDo you have a direct email?
Forum: Plugins
In reply to: [WP Fastest Cache] Several Bugs / issuesAs your plugin will NOT clear the cache after a new post or widget update.
I need to ALLOW Editors to manually clear the cache.
Forum: Plugins
In reply to: [WP Fastest Cache] Several Bugs / issuesYes
and after any widget update on some Linux hosts.
Forum: Plugins
In reply to: [WP Fastest Cache] Several Bugs / issuesPut simply just in case.
Can you please allow editors to also manually clear the cache.
Reason: Your plugin does not work / clear the cache after an update on some linux hosts.
Forum: Plugins
In reply to: [WP Fastest Cache] Several Bugs / issuesI am not sure how screen shots will help?
Basically, on the tested Host LCN.com your plugin does not clear the cache when you update a page or widget.
LCN.com are a standard Linux Host that fully supports WordPress and I have a client that hosts 3 x websites with them.
The problem
The problem is that when an Editor / Admin makes an update, the update is not shown on the site as the plugin still serves the old cached files. They also lose the top ADMIN tool bar.As an admin you can manually delete the cache but not everyone can be an ADMIN.
The only workaround I can see is to allow Editors to manually delete the cache. Then the Editor can manually delete the cache every time they update.
So the simple answer / workaround whilst not fixing the issue is to build in the ability for Editors to manually clear the cache.
Can this be done?
If not, I’ll use the tried and tested W3 Total Cache