mad99

Hi Jeff,
Thank you very mutch for your fast reply and your hint to ask the Divi-Support.

I did and chat currently with Drin from Support. He will forward this issue/bug to the dev. But also in the same moment he wrote:

Unfortunately, there is no ETA on a solution that I can provide at this time. Though I can assure you that issues are addressed as quickly as possible based on our development team's current workload and the severity of the issue when compared to the severity of other open issues.

So my hope is rather humble.

But as I wrote in support-chat I investigate the Divi-Code and 99% sure I found the ?Problem?.

In Line Line 423 from wp-content/themes/Divi/includes/builder/feature/BlockEditorIntegration.php

if ( ! $this->_can_edit_post( $post ) || ! et_builder_enabled_for_post_type( $post->post_type ) ) {
return $actions;
}

When I delete the ! (not) from ! $this->_can_edit_post( $post ) ||
Then the Link is shown also with the active Plugin ?Disable Gutenberg?.

So I’m quite sure when ?Disable Gutenberg? is activated it seams
$this->_can_edit_post( $post )
returns FALSE
So it seams for Divi, when Disable Gutenberg is activated the Post/Page seams to be not longer editable.

But it is, because over the twice click:
First => Click ?Edit Page?
Second => Click ?Build ON The Front End? the Page is editable.

So I continued to get to the bottom of the code.

The portected fuction _can_edit_post()
In LIne 43 is only check if function_exists ?gutenberg_can_edit_post?

See code:

protected function _can_edit_post( $post ) {
if ( function_exists( 'gutenberg_can_edit_post' ) ) {
return gutenberg_can_edit_post( $post );
}

So this is the real point of problem!
I guess there are two different solutions.

FIRST:
_can_edit_post should have some query for plugins that disable Gutenberg and the function ?gutenberg_can_edit_post?. This I wrote to Drin from Divi-Support. And he will forward the chat to developer. But wrote:

The developers will be having a look at this chat in this case, as we as support only do help with the issues that the Divi theme has.

SECOND:
Maybe you as Plugin-Author from ?Disable Gutenberg? can leave visible the function gutenberg_can_edit_post.
Or maybe you have another good idea how it is possible to save Divi from this stumble about querying the “gutenberg_can_edit_post” function.

Would be great to hear from you or other solution-finders.
Best regards
Martin

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

Hey CLUEVO team,
thank you for the quick feedback and your really special offer.

To be honest, in the meantime I took a closer look at the possibilities of SCROM and the lesson contents that can be created with Authoring Tools.
I build some for testing.

At the end SCROM-GUI is not my idea of current design possibilities and UX for websites. In everyday life it feels rather complicated, to capsulate the lessons and the course-work-flow in external tools like UDUTU (Seams to be more time-consuming).
UDUNTU’s GUI seams at least a bit of outdated.

But I’m almost sure Adobe’s tool has more to offer. But the sales strategy doesn’t seem nice ;o).
The switching back and forth while publishing and improvement processes remains (in my opinion rather inefficient for the web).

Sure, with your tool you offer the integration of other content.
But at this time, the presentation and course-sequence-info are then a bit “simplistic”.

At the end, I have to decide now which tool to use in the next few years. So in the current status is not applicable enough for me.

Sorry, your plugin looks promising. I will certainly continue to follow Cluevo. I just don’t have enough time to wait or spend much time on beta testing or “waiting for WooCommerce to integrate”.

But I greatly appreciate your special offer to solve this in this very individual way!

Thank you very much.

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