Archived topic
Trouble Customizing Additional CSS
17 replies · Started by Alex on April 27, 2021
When I go to Customize > Additional CSS and edit it, I get an error message "Looks like something’s gone wrong. Wait a couple of seconds, and then try again." I can edit everything else just fine. I tried disabling all plugins, same error. When I go into the browser inspection window, I get a 403 error on wp-admin/admin-ajax.php. See attached image. Alternatively, if you could point us in the direction of where we can find that file, we can edit it outside of the interface as a last resort.
Hi there,
That's strange. The additional CSS field is a WordPress core function so it shouldn't be a theme issue.
So disabling all plugins didn't help at all?
What if you activate a Twenty series WP theme?
Disabling all plugins did not help, I get the same error. I switched to Twenty Twenty-One and added .test {margin-left:0px;} to the blank css file and it saved just fine. I changed back to GeneratePress and tried to modify the additional css again (modified a #000 to #eee) and received the "Looks like something’s gone wrong. Wait a couple seconds, and then try again." Not sure if this has anything to do with it, but we're using the Dispatch theme from the Site Library.
Super strange.
Haven't had other reports on this.
Can you send me the dashboard login with all plugins disabled to test?
Let me know :)
Hi Leo,
Can you provide me with an email so we can take this offline? Thanks.
Please use the private info field:
https://docs.generatepress.com/article/using-the-premium-support-forum/#private-information
Okay, please see that field. Also, all plugins are disabled right now. Thanks!
Hey Leo...just checking in on this. Were you able to get the dashboard login and check this out for us? While we've been waiting we went ahead and tested the same thing on our current theme (Flex Mag) and it worked just fine. Any feedback is super appreciated, we really need to get this figured out. Thanks!
Hi there,
Does your site's hosting have some sort of page caching and/or security feature? If it does, can you disable/purge it? Let us know.
We are checking with the host now, but we're 95% certain our dev environment does not have these. Stay tuned.
Just as a follow-up as we wait for the host to respond.
We copied the CSS from the Additional CSS field in GeneratePress and pasted it into the Additional CSS field in the default Twenty Twenty-One theme. When we hit Publish on the Twenty Twenty-One theme with the GeneratePress CSS, it errors out. When we removed all the GeneratePress CSS from the Twenty Twenty-One theme, it published just fine.
Hi there,
so i tried somethings all of which failed.
I installed the Simple CSS plugin as this saves the CSS outside of the Theme - and that also throws a 403 error - strangely being reported by WordFence that is not currently enabled.
I added the CSS in pieces, and it sometimes would save and sometimes it would not - so there isn't any specific CSS element that could be triggering a potential security risk that i could see.
I had to remove the CSS - but i have saved it into the this GIST:
https://gist.github.com/diggeddy/e00ef573b332e953b392de8781cae0a9
You will need to see wait and see if your Host can provided any further info.
Thanks, we're waiting on our host and that gives us something to look into re: Wordfence. We'll follow up once we have time to investigate further on our end!
Let us know what they find
Thanks for the extra set of eyes, turns out Wordfence on our live site was blanketing the dev site as well. Once we disabled that, we were able to update the Additional CSS on the dev site. Appreciate you all hanging in there with us!
