Optimole
Forum Replies Created
-
Forum: Plugins
In reply to: [Super Page Cache] New Admin Interfacehey @bobsled,
Good point, thanks for reporting it, it was an oversight from our end and it wasnt migrated. The team is working atm to bring this up, will follow up with an update soon.
Thank you for understanding.
Hi there,
We’re currently not aware of any ongoing issues, so we’d really appreciate your help in isolating the root cause.
Here are a few steps to try first:
- Disable Optimole CSS/JS optimization (if it’s enabled) and check if the issue persists.
- Clear the cache if you’re using a caching plugin.
- If you’re using a page builder that generates external CSS files, look for an option to regenerate those files and give that a try.
If the issue is still unresolved after these steps, please reach out to us via optimole.com/contact and, if possible, share access to a staging version of your site. This would allow us to test plugin updates and better identify the source of the problem.
Thanks!
Hi,
No, is not.
Do you have more details? Like any error log reported? Or if you have a staging version of it can you contact us on optimole.com/contact to coordinate on troubleshooting this.
Thanks!
Hi @nolandc,
I’m very sorry for the frustration you’ve experienced, and I appreciate you sharing your concerns.
I’d like to clarify a few points to address your concerns accurately:
- First, regarding your images: Optimized images are indeed stopped after account deactivation. However, your original images remain accessible for up to one month after deactivation precisely for restoration purposes. If your transferred images appeared blank upon restoration, it’s possible there was an issue during the transfer process.
- Regarding the email notifications, our system sends multiple alerts as accounts approach their usage limits. I’m sorry to hear you didn’t receive these. It might be worth checking your spam folder or checking your registered email address.
- Finally, we never intend to force upgrades. If our system mistakenly showed you reached your quota, I’d be more than happy to investigate this discrepancy closely. Our intention is always transparency, not a bait-and-switch tactic.
Thank you for your understanding and patience.
Hi,
We do exclude bots already by their User Agents and they are not counted against the quota.
I hope this helps.
We’re sorry for the confusion and any inconvenience this has caused.
To clarify, before any account is deactivated, we send multiple notifications and provide a grace period during which images remain accessible. Even after deactivation, you can still download your images for up to a month.
That being said, we appreciate your feedback and will review how we can improve this process to avoid similar situations in the future.
Hi @bauhausweb,
If you check the ajax endpoints while you are logged is normal those to not be replaced. Can you share the page where I can find those ajax requests being triggered to verify?
Thanks!
Hi there,
Images from admin-ajax.php should be replaced and served via the CDN when you are not logged in.
I hope this helps.
Forum: Plugins
In reply to: [Super Page Cache] best way to purge cacheHey,
Purging the cache from the plugin dashboard should be enough.Forum: Plugins
In reply to: [Super Page Cache] Prevent the following URIs to be cached – Not workingHey,
I might have an idea about what can potentially be wrong here, but I would need the site url to take a look at the headers at least.Forum: Plugins
In reply to: [Super Page Cache] Fastcgi errors are still occuringHey,
Thanks for letting us know. Do you have Cloudflare enabled or you don’t want to enable it and you are wondering why is this a problem?Forum: Plugins
In reply to: [Super Page Cache] backend.min.js TypeErrorHey,
We just released a new version fixing some reported issues, let me know if it works now.Forum: Plugins
In reply to: [Super Page Cache] Javascript error in latest version – 5.0.1 and 5.0.0We just released a new version that fixed this.
Forum: Plugins
In reply to: [Super Page Cache] Host name heads upHey,
We did some fixing around this in the next version, can you update and try again?