eelcobruinsma

You’re very welcome! I really appreciate the effort you and your fellow plugin authors put in these nice tools.

Hi there,

Glad that has been cleared up.

Later today, when I have a bit more time, I will write a review.

Thanks.

Hi there,

I used the first update process. Your question about the profile put me on the right track. In 4 out of 5 sites on which I had installed AG, there was a profile that had disables all but a few blocks. These profiles remained in the database even after removing the plugin and became active again after I tested a new installation. This is how I discovered that AG caused the blocks to disappear.

I forgot all about the existence of these profiles. So I am now in the process of re-installing AG on the remaining sites. I will immediately change the profiles associated with it.

The remaining mystery is, how these 4 profiles got configured to disable all but a few blocks in the first place. I never consciously disabled 95% of all blocks on multiple sites. And why not on the one remaining site? Since these are all sites for which I am the only editor, there is no one else to blame.

But all’s well that ends well, it was not a technical issue, and I now know that it is prudent to check the profiles from time to time, because some goblin must be intervening.

Anyway, I’m happy to be able to use AG again. Thanks for your quick response, which enabled me to solve the issue.

Dear @kkikuchi1220

Thank you for your swift action. I have installed and tested the plugin, following your instructions. It all works fine. The columns remain intact. And you were right, it is a Gutenberg core problem. I will recommend your plugin, because it offers nice options with a lot of freedom with respect to styling.

Thank you for taking action. I wish you good luck with future developments and hope to see more of your work.

Best Regards,

EB

Dear Kazuki Kikuchi (@kkikuchi1220)

Thank you for your reply.

As I do not have the know how to develop plugins myself, but only to use the to produce content-rich sites, I, as a user am always in your debt, and respect the work you do.

I wish you the best of luck with finding and fixing this bug. You are not the only one struggling with the same problem. I would be happy to use the plugin again and I hope it will be a valued part of the Gutenberg landscape. I added a star out of respect for your open and immediate approach.

Best regards.

EB

No problem.

I think I have some more information for you to isolate the problem. I just tried it again on several pages and was editing the CTA block without problems. Then all of a sudden the memory use went up from 43% to 94% and the iMac froze. After killing all processes I recapitulated and discovered that it happened when deleting text from the “Call-to-action text” field. More in particular. When I fill in this text field and want to change the text, I start deleting the text with backspace. When the text-cursor arrives at the last letter to be removed (so the first letter/character of the sentence, or CTA-text” the memory use soars.

I have repeated this procedure > writing > deleting with backspace; several times and the problem repeated itself. So immediately upon deletion of the last remaining letter, which will not be deleted by the way, all memory is sucked into this procedure. Perhaps this has something to do with the CTA block’s CTA-text field not being allowed to be empty. I don’t know.

I hope this helps you to identify the problem.

Cheers.

EB

Hi,

I agree that it is weird. And I suspect that it must be some kind of interaction with Gutenberg that causes the issue. I have noticed one other freeze when editing a block that was unrelated to the AB-CTA block. When I activated AB to do some further testing nothing much happened. When I decided to use a CTA-block all went well. Until I can back to the block to edit the main text. Immediately my memory use soared to 94% and the iMac stopped responding until I managed to quit Firefox.

There is a pattern, when looking back at the issue. The freeze occurs when editing an element/block, repeatedly. Like writing something, deleting some letters, and retyping. Insofar as I can tell now, it may indeed be some deeper Gutenberg issue (because it once happened when NOT editing an AB CTA-block), but in most cases it occurred when editing a CTA-block. So editing the CTA-block may be the trigger that activates an underlying problem in Gutenberg. You may well be right there.

I only don’t know how, and what. You may have noticed that I upped the stars, so as not to punish AB for something that is somewhere deeper under the surface. But there is a correlation, and you might have to mingle with the Gutenberg team to find out more.

My setup is fairly clean and optimised. I never experience any trouble, and when working with WordPress this is the only issue I repeatedly, apart from the fact that the Gutenberg interface itself is far from perfect, and complete yet.

The AB blocks are quite useful, and being able to use the AB CTA-block would save a lot of hassle, because it’s customisation options are really nice and easy to use.

Hi there.

I’m sorry to say that the problem persists. When I wrote the earlier reply I could not replicate the problem and everything went smoothly. So I went on editing the 4 CTA blocks that I needed. I changed the background colour, and filled in the text in the right spots. I experimented with one CTA block to style it with a background image, which it didn’t write display as I wanted, but that was not the issue. After working for a while I speeded up and switched from one CTA block to the other quite quickly to harmonise the texts in both blocks. At that moment the memory usage went up from 50% to 95% and the computer froze. I could see that actions reached the system, but with a delay of minutes. The otherwise completely silent fan became audible. I could not stop the browser, or optimise the memory, and had to reboot by manually pushing the on/off button. I must say that this otherwise never happens, because the computer is in ship shape.
I did not change anything with respect to running plugins, and no other software was running apart from the browser, Firefox in this case. I hope this helps.

Hello,

Good of you to drop in so quickly. Before writing the short report I did what you suggested. Deleting the block, even creating several test pages just to see which combinations might cause the problem etc. I use the latest version of Atomic Blocks and Gutenberg. I update as soon as an update is available.
I tested in Safari and Firefox, latest versions, on an iMac.

The trouble occurred when I subsequently entered the CTA Title, the CTA text, and the CTA button text, when I came back to edit the CTA text again, my processor load soared and the rainbow disk started spinning, practically taking all possibility of interaction away. On 2 occassions I had to reboot the computer. And later I managed to force quit the browsers, optimise memory, and start over.

I tested it on a website which already had an installed, and updated version of AB, and also on a website where I installed AB today.

Strangely enough, I came back after dinner, saw your message and wanted to reproduce the error, and I am getting the effect.

Which makes me think there might be an unwanted interaction with another plugin. E.g. I deactivated another blocks plugin recentlty, because it consistently broke Gutenberg’s column layout.

As I said, at first I thought that Firefox was the culprit, because of the heavy memory footprint, but switching to Safari gave me the exact same result.

Now I have created all AB blocks on one page. Everything works as it should. To test is well, I have created 5 CTA block, 1 of which I have nested in a container. All 5 work fine, even after repeatedly editing and re-editing the title, text and button text. Nothing much has changed over these hours, so I have to figure it out.

I have to systematically recreate the exact configuration that I had earlier to see if the problem occurs again, and when. It may be an interaction between AB and some other plugin I deactivated to analyse all possibilities.

So that will take some time. But I will be back with the results soon.

Good of you to jump in.

I installed the plugin on another website today. Immediately my Gutenberg columns broke down. Not only that, but in the editor the plugin wreaked havoc too. Columns were pressed into the left corner of the editor and were too small to edit.
After deactivating everything was workable again and the columns reappeared in the preview and rendered test page.

I am afraid I have to de-install the plugin from my sites, it is costing me too much time .

Hi Maxime. Thanks for the reply. I will surely be happy to test the plugin anew, because the basic approach is good. I understand that Gutenberg itself is a bit of a moving target, so moaning about the odd issue now and then is not really the best option. So the best of luck with finding the cause.

E

Hi Tammie,

Well thanks for your reply to my review. I am really looking forward to the enrichment that the phase 2 which you refer to will bring.

To be clear, in my original review I stated that I deactivated Gutenberg. But only for a day or so. I decided to activate the plugin on 6 websites I am currently working on. Looking at the functionality from different angles, and using it in conjuction with different auxiliary plugins. I thought this might be more constructive than just sitting there and waiting for things to happen. With every improvement and enhancement my experience will grow too, and I will be able to judge its impact better than when I would not use Gutenberg at all.

I am not a GitHub kind of developer, but an experienced web designer with a keen eye for delivery of content, so I will always look at the functionality from that perspective.

Good luck with the next phases.

You’re welcome Ben! I have installed the update and the page now displays everything as smooth as silk! Thanks for the swift action and have a good weekend!

E

Hi Ben.

Fantastic! As I said, I like the theme a lot. It’s very clean, and still ‘newsy’ and classic. So it’s great when all features can be used, and the blog can be displayed as well.

I will update as soon as your update is live. Thanks for you explanation and swift action!

Eelco