- This topic has 15 replies, 2 voices, and was last updated 3 weeks, 3 days ago by
.
-
Posts
-
Hi,
Thanks for your huge work.
I’ve noticed some weird behaviour on my website which is now on live dev stage. When I perform customisations, pages updates, or publish some contents (posts, forums, replies) and CSS hacks I have to refresh twice for the modifications appears on the front. The biggest problem remains that user’s actions (such as log in/out/replies/get notifications) have to be perform twice to work too. Do you have any idea where can i find where this problem is ? I don’t have any cache plugin running on the installation, I’ve disabled PWA plugin (but i’ll need it in prod) and I’ve installed Private Site following your advices in Cera Documentation.Thanks in advance to let me know if you have any idea about this.
Best regards
Kévin
Hi scheuerkev,
Thank you for buying our theme. We hope it will meet all your expectations!
Thank you for these specifications. It seems to be a cache issue. 🤔
Does your host provide a cache feature?Best,
Hi Manathan,
Thanks for your reply. In fact no, I don’t have any cache feature working on hosting server. When I flush the browser cache under Chrome Dev Tools (empty cache and hard reload) I receive the page correctly, with all CSS customisations that I made. But if I navigate from these page, the design “reset” with native blue colors and typo. In the “Network” tools, i see that the last ressources loaded is the normal page, with a 200 code, and just above that (the last one loaded so) is the same document with a 301 code (from service worker). Imo, the problem can be locate here. The fact is that I disabled the PWA Plugin (it seems the service worker still exists) for build the design but I have to activate it in prod version. Do you mind the theme gonna work correctly in this usecase ?
Thanks a lot for your reply
(excuse my english)
Regards,
Hi Kévin,
To help us getting clues and find a solution to this issue, please activate logging on your website, just turn WP_DEBUG to true, by pasting the following code lines in your wp-config.php file, just before the line that says ‘That’s all, stop editing! Happy blogging.’:
// Enable WP_DEBUG mode define( 'WP_DEBUG', true ); // Enable Debug logging to the /wp-content/debug.log file define( 'WP_DEBUG_LOG', true ); // Disable display of errors and warnings define( 'WP_DEBUG_DISPLAY', false ); @ini_set( 'display_errors', 0 );More on this in the following topic: Debugging in WordPress.
Thank you.
Hi Manhatan,
Thanks for your reply, I’ve performed the modifications you recommend in your previous message
Regards
Hi Scheuerkev,
Thank you for your feedback.
It’s best if we take a quick look at this. Could you create a new website user for us please? If possible with administrator capabilities so we can make a quick check of your settings.
You can post the user name and password in your next reply and mark it as private to keep this between us.Also, are we free to deactivate plugins for our tests? In this case, I invite you to make a backup before we investigate your website further in order to make sure you don’t loose any data if something goes wrong.
Thank you.
This reply has been marked as private.
Hi Scheuerkev,
Thank you for granting us access to your WP Admin.
We took a look but I cannot reproduce the issues you were facing. Can you please tell me if you can still face these issues?
Regards,
Hi Manathan,
Thanks for your actions and your help, please let me join 2 screen cap of the same page, in customization mode, where the good css rules apply, and the second one in visitor mode, with the default css apply. As you can see on yellow/blue icon on main menu sidebar or the typos. Can’t figure where this problem is :/
Regards,
Hi Scheuerkev,
When closing the customizer, your cache still show the last version of the page. The modifications you made are well published, only you can see the previous version as it has been saved in your cache. Refreshing the page and clearing the cache should help you see all the new customization you made.
That’s not a theme issue, that’s related to kirki, the plugin who extends the customizer. Some settings are saved in the cache to make it run faster.
Do you face another issue ?
Best,
Hi Manathan,
Thanks a lot for your reply and your indications. I’ve made a screen record where the true problem is, when i flush the cache, i’ve got the good css customizations applied, but, when I navigate through the website, instantly, the old css rules (cached I suppose) reapply again. I can easily agree that’s not a theme problem, but, if i deactivate the kirki plugin, i can’t make work the website.
Can you please juste check this video capture and tell me what you think about that ? I give you the link hereRegards,
Hi Scheuerkev,
Thank you for your screencast, I can see the issue. We’ve been able to reproduce this.
However this time, thanks to the code snippet that you’ve recently added to your
wp-config.phpfile, we should be able to read the error.Could you share the content of your
debug.logfile with us please? You can post the content of this file as plain text in your next reply and mark it as private to keep this between us.After having reviewed your next reply, we’ll be able to tell you if the issue is caused by our product, a third party plugin or any type misconfiguration on your server.
If we’re not able to help, we’ll recommend you to transfer the error logs to the plugin author or to your server hosting support.
Thank you.
This reply has been marked as private.
Hi scheuerkev,
It seems this issue is related Super Progressive Web Apps plugin. I deactivate this plugin and all seems to work fine. Can you please confirm me all is working on your side?
Best,
Hi Manathan,
Thanks for your reply. I’ve noticed that the actions your performed in Super PWA made the website running correctly unless on Chrome, except in incognito mode. Don’t know why ? Does this mean Cera is not compatible with PWA specifications ?
Best regards
Can you please try to empty the cache on Chrome? If it works in a private navigation, it has to work on chrome.
I think there a cache feature in this plugin. I suggest you to reach out the plugin authors to know how to deactivate the cache of this plugin. Deactivating this feature should allow you to use this plugin without this issue.
Best,
Hi there,
This topic has been inactive for a while now so we will be closing it to keep the forum tidy. Don't hesitate to create a new topic if you still need help and we'll be glad to help you!
Best regards,
The Themosaurus team.
The topic ‘Twice user actions needed’ is closed to new replies.
