CSS not loading on Front End

[inzlabs]

Hi,

First. Thank you for your amazing work and talent.

We are impressed by Qubely and all the capabilities that bring to Wordpress, however we run into a problem we seem can't solve. In the back end Qubely looks great as it should be, however on the front end it does not load the CSS.

Neither: qubely.bundle.min.css ont-awesome.min.css

This is the page as example with the issue

Example: Back end Ok

Front end with problem:

We have tried Qubely on two different Qordpress sites with the same theme and it works flawlessly. But on this one, we don't know where would be the problem.

We have tried deactivating all the plugins but the problem persists.

Thank you for your time and help solving this problem.

[designerbrent]

I've been looking at this with @inzlabs as the theme developer and I wanted to add a few more details:

The problem seems to be with public function qubely_enqueue_style(). It is checking on line 323 to see if the post meta information for _qubely_css is there and it is failing on our live server. Both @inzlabs and myself have tested it locally and it works.

When I look at the DB, there are not post meta entries for _qubely_css.

The theme we are using is a private corp theme and explicitly include Gutenberg blocks that work with the theme. We were hoping to include yours, but if we can't get around this, we will have to remove them. The ones we are including are the following:

    'qubely/infobox',
    'qubely/wrapper',
    'qubely/timeline',
    'qubely/accordion',
    'qubely/accordion-item',

Thanks for your assistance.

[fai-sal]

@designerbrent thanks for your detailed comment, we are working at this issue and will get back to you soon.

[Inkvi]

Do you have any update on the issue? I've just installed Qubely Pro and have the same problem.

[jgarib]

I've experienced this or a similar issue and resolved it by adding a new preset or duplicating the active preset and setting it as the default. Seems to be something to do with saving the preset css postmeta. I didn't dig deeper once I discovered that when this happens if I mess with the global theme presets I can get it to work.

It's been a few months but I seem to recall seeing an error in my console that lead me to identify the global presets as the issue. This is under the Q menu in the upper right hand corner of the gutenberg editor screen.

[Joennuh]

I've experienced this or a similar issue and resolved it by adding a new preset or duplicating the active preset and setting it as the default. Seems to be something to do with saving the preset css postmeta. I didn't dig deeper once I discovered that when this happens if I mess with the global theme presets I can get it to work.

It's been a few months but I seem to recall seeing an error in my console that lead me to identify the global presets as the issue. This is under the Q menu in the upper right hand corner of the gutenberg editor screen.

Many many many thanks for this comment! After a very long search to solve this frustrating issue I was finally able to solve it by adding a new preset! :-)

I also referenced your post at the Wordpress Qubely support page: https://wordpress.org/support/topic/qubely-blocks-render-in-editor-but-not-on-the-front-end/page/2/#post-14058892 As there are more people facing this issue.

[mvalencia464]

I've experienced this or a similar issue and resolved it by adding a new preset or duplicating the active preset and setting it as the default. Seems to be something to do with saving the preset css postmeta. I didn't dig deeper once I discovered that when this happens if I mess with the global theme presets I can get it to work.

It's been a few months but I seem to recall seeing an error in my console that lead me to identify the global presets as the issue. This is under the Q menu in the upper right hand corner of the gutenberg editor screen.

That didn't work for me, but deactivating the Blocksy Companion plugin did.

[praghavaji]

@designerbrent thanks for your detailed comment, we are working at this issue and will get back to you soon.

By soon you mean never?

[praghavaji]

In my case an archive page was missing qubely styles. Why? Because the page itself didn't have a _qubely_css post_meta record. Every Qubely block in the posts that the archive page pulled in did have this post_meta record but the archive page itself did not. So, Qubely decided not to send the styles to the page, even though the page had a bunch of posts with Qubely blocks in it.

As a temporary hack I created the relevant post_meta record for the page manually and it now works.

The long term fix is to replace Qubely with something else.