css

Please avoid opening up a new forum post for the same related issue. The forum allows you to reopen any previous issue you created and that has been closed if you are still encountering an issue. Creating new issues in the forum is going to create confusion on the topic and difficult for other users and us to follow the discussion.

On the topic of CSS, we’d be happy to help support you, but we need additional information to provide that support. Otherwise we are spending hours trying to resolve issues without specific details. We have tested the behavior you described using a test environment based upon the details you have provided to date, but we haven’t been able to reproduce the behavior.

We do anticipate this could be occurring as a Theme or Plugin or Custom Code conflict you are specifically using on your site. Unfortunately, we are unable to reproduce your exact website configuration with all plugins and theme modifications, especially if you are using Pro/Paid plugins we are unable to purchase those just for testing purposes.

“It was working fine yesterday for an hour of intensive use, and today when i checked, the css was gone again and had to deactivate the plugin again.”

Unfortunately, this type of description doesn’t provide us additional information to take action. Based upon this description, sounds like you are making a lot of modifications and potentially any one of those modifications could be introducing errors.

Please provide us additional and specific details on the behavior, specifically which CSS code line creates your error or which plugin/theme conflict is occurring with screenshots, reproduction steps before the error, error logs or dev console error reports. These specific details will allow us to review the issue further.

We will go ahead and leave this forum post open for you to review getting additional information. Again, please avoid creating new post if this post is closed at a later time, just reopen this post if you get more details in the future. Thank you.

ok sorry, i presumed ‘closed’ was definitive.

I dont think i ever mentioned any modifications, nor did I hint to them. Not sure where you’re reading that. It’s a rare site that has no modifications at all.

There’s absolutely no pattern in the errors unfortunately. The only thing i could do is set up a mirror site where you can test yourself, if you want. I dont promised any date for that, i’m pretty busy, but eventually will do so and inform you about it.
Thanks

Any additional information you can provide would be helpful to identifying the root issue and enable us to continue troubleshoonintg.

One recommendation, use a screen recording tool, like https://www.loom.com/ as you are working. This will capture the error and steps you perform leading up to the error. Once the error occurs, open up the browser developer console for any logged errors. We could then review and analyze the video to see if we can identify the repo steps or understand a pattern on when the error occurs.

A mirror site could be helpful, but that is a lot of work to create for yourself and also we don’t have the support resources to test on the mirror site trying to reproduce the error. Often the error is related to a specific step you are doing, and even with a mirror site, we might not be able to reproduce.

A screen recording tool is definitely more work for me. As written, it happens that there’s no problem for a long time (hours). And i’m not busy on that site anymore for other things besides this issue. As I see it, it will probably remaining unsolved as neither has the time to solve it; I’ll search for an alternative instead. Thanks anyway!

Understandable. We will go ahead and close the issue at this time, feel free to reopen the issue again, if you have additional details to share helping us to troubleshoot or would like to revisit after exploring alternatives.