Oxygen Block screenshots fail to generate

[stuartabowler]

Description:

When I create an Oxygen Block, sometimes the Screenshots do not generate, failing with a popup warning, though the Edit page UI often claims that they do generate. I have many blocks that do successfully generate screenshots, and those always succeed. However, in some cases the issue is tripped and those block screenshots always fail.

My best educated guess based on looking at my log files is that some screenshot generation attempts exceed a server timeout. I have not been able to pinpoint which components are responsible for this.

In the sandbox site there is an Oxygen Block called "Example block that cannot generate screenshots". If you attempt to place this block in a page you will see that the Component screenshot is missing (see screenshot below)

Sandbox link:

https://oxygen-qhywwqa8v89fl.oxygen-demo.qsandbox.me/wp-admin/post.php?post=44&action=edit

Steps to reproduce the behavior:

1. Go to 'the "Example block that cannot generate screenshots" edit page'
2. Click on 'Generate screenshots'
3. Wait for the error message to pop up

[KittenCodes]

@stuartabowler I'm very sorry, the Sandbox site expired before I had chance to look at this.

Would you mind letting me know what was inside the block that you were having problems with so that I can try to replicate this?

[hayatbiralem]

Hey @stuartabowler 👋 I have the same issue. Did you solve this?

[santo74]

@KittenCodes I'm experiencing the same issue, namely that I can't generate any screenshots.
When trying to do so I get a popup with the error "Failed: Could not validate the license." while I obviously do have a valid license (otherwise I wouldn't even be able to create that block in the first place).

Despite the error, the text in the screenshots section now shows "Screenshots successfully generated" (in green). However, when I navigate away and then come back it again shows "Warning: Screenshots never generated" (in orange).

[KittenCodes]

@santo74 This is something we're currently investigating. I believe it is related to the certificate issues that have recently occurred in WordPress: https://core.trac.wordpress.org/ticket/54207.

[santo74]

Thanks @KittenCodes for the follow-up. Will this have any impact on other parts of the Oxygen Builder plugin or is it only related to the screenshots?

[KittenCodes]

@santo74 Some sites are having problems accessing Composite Elements, which may be related - it's something we're still looking into. I'm not aware of any other issues.

[santo74]

Ok, thanks for the clarification.
Since I haven't used the composite elements in a while I didn't notice any issues with them, but it's good to know there might be.

[portseif]

I'm now facing this issue as well. I've tried everything: saving permalinks 2x, resigning shortcodes, re-installing Oxygen, and combing through the db looking for any discrepancies. The two I found were oxygen_composite_elements_license_key and oxygen_composite_elements_license_status which were both null, so I set the correct data and still got the error.

So, then I read the link @KittenCodes posted (https://core.trac.wordpress.org/ticket/54207), and installed the SSL fix (https://github.com/ClassicPress-research/cp-ssl-fix) and still nothing.

Lastly, I reset all permissions via FTP in case that was the culprit... nope.

The only thing I haven't done is downgrade WordPress. I just thought I would post everything I've done to correct this issue.