kalleankaco

I had the same issue with the Gutenberg editor: the font-sizes in the editor got larger and larger, making it impossible to do any writing on blog posts.

I don’t know the exact cause of this, other than it has to do with Gutenberg apply CSS from OceanWP’s settings in the customizer. Normally this is a good thing because it allows your editor to replicate the exact CSS on your front end, but something about OceanWP’s implementation is buggy.

Here’s the solution to this problem:
1. Download the Stylus addon for Chrome or Firefox. This addon allows you to modify the CSS of any site you see and the changes are only applied to your current computer.

2. Once Stylus is installed, add the required CSS that fixes the weird font-size bugs in the Gutenberg editor. In my case, I only needed to add the following lines in Stylus but your version of WordPress/Gutenberg/OceanWP might be different (just use your browser’s built-in page inspector to look at the CSS to find the matching selectors):

/* The Gutenberg Editor for WordPress inherets CSS from OceanWP Theme which causes bugs, e.g. enormous font-size settings. */
.interface-interface-skeleton__content .block-editor .editor-styles-wrapper .editor-post-title__block .editor-post-title__input {
    font-size: 30px;
}
.interface-interface-skeleton__content .wp-block {
    font-size: 20px ! important;
}

I’m being lazy here and applying a font-size of 20px for ALL the editor contents, so everything from a paragraph to headings with be set to 20px. If you are less lazy than me, you can apply different CSS for separate html elements like h1,h2,h3,h4, etc.

In the selectors above, I’ve added selectors to make sure the declarations only apply to the gutenberg editor and nothing else on the edit page. Additionally, I’ve set up Stylus to limit the CSS to my blog domain by using the “Applies to” at the bottom of the Stylus editor.

This is a temporary fix in that it doesn’t solve the underlying issues, but it’s much faster and easier to solve than trying to figure out wtf Gutenberg+OceanWP is up to.

• This reply was modified 3 years, 2 months ago by kalleankaco.
• This reply was modified 3 years, 2 months ago by kalleankaco.
• This reply was modified 3 years, 2 months ago by kalleankaco.

Thank you – the latest released fixed the bug.

Appreciate the work that went into this is so few hours, @wordpresschef .

Want to confirm that the bug still persists on 3.34.1 with WordPress 5.3. Basically, if customer picks a certain booking date, the date picker auto selects the previous day.

• This reply was modified 4 years, 11 months ago by kalleankaco.

Update: the solution to this issue was provided by venumurki in this related support thread. Solution:

So I changed the “Booking time range” setting on Settings > Booking rules to maximum 1 month and server response time went from 25 seconds to 5 seconds!

So I changed the “Booking time range” setting on Settings > Booking rules to maximum 1 month and server response time went from 25 seconds to 5 seconds!

Thank you, venumurki!

It’s still not perfect but a huge improvement. The previous max setting was “just” 6 months so I can’t imagine the response time for 1 year on our hosting.

Many thanks for taking the time to write that reply. Will try changing max days to a month or two.

“Also we changed the order of booking, by selecting that in settings.”

Do you mean the option “Change Order” on the page Settings > Booking rules?

• This reply was modified 5 years, 5 months ago by kalleankaco.

Have the same problem with incredibly slow loading time between steps in the AJAX version. Looked at your site and problem seems to be solved? Care to share how you solved this?

100% agree. Gutenberg seems rushed and poorly designed for beginners and experienced users alike. So much functionality and intent is hidden in the UI. The devs obsessions with “distraction free writing” has pushed key functionality to the sidebar or top bar of the post editing page.

Thanks Tor-Bjorn for your replies. I was awake til morning trying to troubleshoot why the plugin was broken but ultimately decided to downgrade both the plugin AND wordpress to avoid the bugs.

Yeah, 3.28.1 is seriously broken on WP 5.1. I get the same error like niyawms.

Yes, exactly.

Thanks for the tip.

I actually had to use another theme because 2017 simply isn’t worth the effort. Wish that www.ads-software.com didn’t rely on Automattic for their core themes and made a better effort to design a theme that’s literally used by hundreds of thousands of sites.

• This reply was modified 7 years, 7 months ago by kalleankaco.

Great to see this resolved. Thank you everyone involved.

No worries. Again, thank you kindly for your prompt fix.