rdebruyn

when the error shows and the 2 buttons are displayed, there was also a … menu

I clicked that and saw something like try to repair the block. I tried in my local copy and it worked, so I tried in my production environment and it worked also.

I have no idea what caused the issue, but I seem to be back in business. Thanks for the quick response ??

Ray

– disabled all plugins except CoBlocks
– went back to a revision from 2 months ago
– double checked the error does not show. Sometimes I have to exit after doing the revision and then go back to the page to see it.
– added an image and updated

All looked ok, but when I exited and navigated back to the page, I saw the error again.

CoBlocks Version 1.18.0

WordPress 5.3 running Ascension theme.

Are you running the Gutenberg Plugin?
No

Are you running other plugins?
AddToAny Share Buttons
Akismet Anti-Spam
All-in-One WP Migration
Contact Widgets
Duplicate Page
Gravity Forms
Media Library Assistant
Simple Lightbox
Sucuri Security – Auditing, Malware Scanner and Hardening
Wordfence Security
WP101 Video Tutorials
Yoast SEO

I tried doing the resolve path in a local copy and it converted the block to an html block. I can try disabling plugins if you think they might be an issue. Worst case, I guess I could remove the block and recreate it to see if the issue comes back.

I have serious doubts about it being caused by Wordfence as well. I guess I’m just at a loss as what caused it and what fixed it. Thought I’d post in case other had the issue and had some insight.

Thanks for the quick response ??

The only thing that topic addresses was max_execution time and checking for javascript error in the console.

I increased max_execution_size to 300. The upload takes far less than a minute and the error comes up immediately after.

I checked the console and had a warning about content blocking. I changed browser settings to stop blocking which fixed the console error, but the upload issue remained.

As I stated above, when I look at the error log, I see:
Failed to open stream – no such file or directory
File: …path/class-ai1wm-archiver.php

If you have nothing more, I have successfully done an export and import manually. It’s a bit tedious, but doable. I had trouble using sftp at first. The documentation said it should be on by default, but turns out the virtual machine I’m using has ssh turned off when using virtual box. I have sftp working now.

I realized reading my post after submitting, that the lightbox plugin could be involved. To be sure I deactivated the lightbox plugin and repeated the steps. I did see the same issue. Link URL did not get updated when the image was changed. When I viewed the page and clicked on the image, it went to the old image’s attachment page.

The issue is still there

This is the plugin:
https://www.ads-software.com/plugins/coblocks/

It comes as part of the default install from godaddy, so will probably get a lot of use.

I found an imperfect solution:

function eis_add_longdesc3( $content ) 
{
  //should replace data-link in coblock gallery images to longdesc so addtoany image share works
  return str_replace( " data-link=", " longdesc=", $content);
}
add_filter( 'the_content', 'eis_add_longdesc3' );

I would rather be able to add the longdesc attribute to all images, but in the end, this filter was the only one that modified the output html. Since the data-link attribute already had the attachment page URL on images from the coblock masonry gallery, I could make all those images shareable. Since the page being shared is the attachment page, it picks up the og meta info from that attachment page.

So, in the end, I have a partial solution. I would still take any advice for better or alternative solutions.

nice ??

another site now showed 7.1.20. I updated that no problem. The changelog still only shows 7.1.18 as the newest update tho
https://www.wordfence.com/help/advanced/changelog/

usually first turn debugging on:
in sftp, edit the wp-config.php file – look for the line:
define(‘WP_DEBUG’, false );
change false to true and try the site

normally you would see one or more error messages and possibly the site with error messages showing in places. I dod not get error messages when I turned debugging on so I removed the wordfence directory in wp-content/plugins and tried the site again. That fixed it – then installed wordfence again

figured it out…

a couple weeks ago we had another 500 error that seemed to be caused by a wordfence plugin update that failed to complete. Applying the next update solved the issue.

On this site, somehow the wordfence plugin existed in the plugins folder version 7.1.15, but did not appear on the admin plugins page. Somehow it was causing the issue with the yoast update failure to update.

I pulled production to staging. I guess this process in godaddy installs the plugins in the directory, so the wordfence plugin now showed on the admin plugins page. I updated wordfence successfully and then the other plugins. All updated fine this time.

The 500 server error is gone. Now I need to check my other sites.

Hope this helps ??

I have the same issue on 2 sites.

co-op.place staging site – I updated only yoast to 9.03 and get a 500 server error accessing any pages

orleans-office-space.ca – I updated yoast to 9.03, gutenberg and contact form 7 with the same – a 500 server error accessing any pages.

I put orleans-office-space.ca into debug mode and confirmed my suspicions that the yoast update was the culprit.

Through SFTP, I renamed the yoast plugin folder and the errors were gone.

I renamed the yoast plugin folder back and it was deactivated and showed it needed an update to 9.03. It seems there was a problem during the update. When I performed the update again, an 500 error occurred and it would not activate the plugin.

We are hosted on GoDaddy

I have no access to the server logs. I would have to contact GoDaddy for that.

Hi Tammy,

I’ve started toying with the editor again. It looks like the solution of adding my own style is a bit cumbersome.

Some css is not an issue. I’ve been replacing existing wp sites to replace old themes and have been adding custom css to the theme to make it appear closer to the old site. So a lot of that css is just about adding a header image, fixing the content width, adding a gradient to the body etc. None of this is needed for the editor.

I have added some style for a white frame for the figure/figcaption. Without that css in the editor, the caption text simply looks like other text in the page. It’s hard to get an idea of the end result without a preview.

As I add more custom css, I would also have to edit the local css file I could set for the editor. Making changes in both places is on going and counter productive. The old editor did apply quite a bit of custom css. It would still be better to see the style as a true wysiwyg.

Before Gutenberg, I was modifying the html code. Many of these changes were not much of an issue. Now with Gutenberg, I find it likes to change the code – especially when I first edit the page. It wants to convert to blocks which modifies the html so that I lose my customization.

In an example of this I wanted 3 or more thumbnail images to appear in a row and wrap as the page narrowed. To do this I added a div to contain the images and a div with a figure/figcaption for each thumbnail. Convert to blocks broke this into 3 images all on separate rows. I found I could create a custom html block, but I don’t see it as easily edited. ESpecially if I wanted to add more thumbnails.

To fix this, I created a gallery which gave much the same result. It wouldn’t quite wrap as I wanted leaving 2 thumbnails in a row breaking out of the content area. I had to add some css to fix this, but it leaves the page as editable through the visual editor.

My main concern is not just to edit the site, but also to be able to hand it off the my boss who is less technical. I think I convinced him that it’s in our best interest to get used to the editor now. Our plan is to create a staging version of one site we’re working on and activate Gutenberg there. We’ll make changes on production, then make similar changes in staging and compare the results/experience.

There is a learning curve and I’m sure a lot of people find that to be the end of the world lol. Losing or at least not requiring short codes is a huge step forward for me. My learning curve includes understanding how css is used by the editor. For example, I was expecting a float:left; in the css to have images wrap in the gallery. I never did determine what css was used to achieve the result, but did find where to bang on the pipe to fix it.

I applied the latest update to the plugin today and will try and keep as up to date as possible with changes. I look forward to see what’s to come,
Ray

Cool thanks ??

Hopefully people become a bit more positive about the change. I certainly see iy as an improvement.

Ray