Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

critical error when mistaken syntax in css #5

Closed
danj-O opened this issue Aug 28, 2020 · 6 comments · Fixed by #6
Closed

critical error when mistaken syntax in css #5

danj-O opened this issue Aug 28, 2020 · 6 comments · Fixed by #6

Comments

@danj-O
Copy link

danj-O commented Aug 28, 2020

I was going along my merry old way adding some custom js and css to my bb with code settings and accudentally put a colon instead of a semi-colon somewhere and I got a critical error and can't get back into the editor to fix it! what do I do? Are you aware of this issue?

@fastlinemedia
Copy link
Collaborator

Hey @danj-O, thanks for posting and sorry to hear about the issue.

Can you try BB's safe mode to see if that'll let you get in there and remove the bad code?

https://docs.wpbeaverbuilder.com/beaver-builder/troubleshooting/debugging/safe-mode/

Let me know how it goes.

Justin

@codente
Copy link

codente commented Aug 31, 2020

@fastlinemedia I recommended safe mode to him in the forum. Said it didn't work

https://community.wpbeaverbuilder.com/t/simple-css-error-locking-me-out-of-bb/12796/5

@danj-O
Copy link
Author

danj-O commented Aug 31, 2020

As codente said, I tried safe mode and the page still wouldn't load to make edits. So strange, all it was was a colon instead of a semi-colon. In the end, I really needed to continue working, so I got rid of this plugin and I've been using the cmd+y input area for css and js. The weird part is that if I try to load code-settings back up after deleting and reinstalling, I immediately crash again.

@fastlinemedia
Copy link
Collaborator

Thanks for the info. I'll see about making this plugin compatible with safe mode in case this comes up again.

Pross added a commit that referenced this issue Sep 1, 2020
This also adds a message into the CSS as a comment with the compile error and node ID and type to make it easier to find the offending settings.
Fixes #5
@danj-O
Copy link
Author

danj-O commented Sep 2, 2020

cool beans! I'll give the plugin a try again once this is fixed. Kinda hard to use if I can't ever make any mistakes. Otherwise, love the convenience of this plugin! Thanks for your efforts!

@fastlinemedia
Copy link
Collaborator

Hey @danj-O, the fix is merged. Install a new copy and let us know how it goes :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants