nothroughroad

@nick_byrd Thanks for taking the time to copy it over here too, appreciate it.

Just updated to 5.0.0 and the issue seems to have been fixed. Thanks v much.

Thanks for responding @miemie . Yes, the problem still persists with 4.3.1. I’ve cleared caches using LiteSpeed.

Clare

That’s great, thanks for the speedy response.

Thanks @hchouhan. Have done as advised for now.

I have been experiencing a similar issue. The steps to replicate…

Create a new page
Add some paragraph text
Add new DLM block, but don’t select a download from the list
Wait… until the page tries to auto-update (or try and save the draft or publish page)

“Updating failed. The response is not a valid JSON response.”

Refreshing the page gives the new “Critical error” message and sends the “Your Site is Experiencing a technical Issue” email

Bump. Worse than that. Here are the WAVE Errors and Alerts for the base installation, one all-day event, one recurring event, agenda view. Similar for the day/week/month views and the widget.

Errors
– Empty link
– Broken ARIA menu
– Very Low Contrast
Alerts
– Redundant link
– Very small text

Bump. I too am interested in any very very near future plans, as I am currently adapting a site that already uses ai1ec and it fails WAVE, for example.

Here are the Errors and Alerts for the base installation, one all-day event, one recurring event, agenda view. Similar for the day/week/month views and the widget. My advice? Steer clear.

Errors
– Empty link
– Broken ARIA menu
– Very Low Contrast
Alerts
– Redundant link
– Very small text

• This reply was modified 4 years, 10 months ago by nothroughroad. Reason: Made list clearer

Thanks for your response. Is there any way of sharing this info privately? Eg the database prefix is sensitive info.

Please could you prioritise the second problem I found, which is that any product manually set to Catalogue visibility:Hidden disappears from the All Products list on the back end, as well as on the front end.

I have contacted the developer of the separate plugin to look into the problem re setting the products to Hidden on a timer.

Thanks

PS. Maintenance Mode is currently activated, but Ive also tried it without this.

Thank you from me too!

OK, I think the problem with the front end is caused by the separate plugin that doesn’t set the products to Catalogue visibility:Hidden properly.

But I have since found that any product actually set to Hidden disappears from the All Products list on the back end, as well as on the front end. This isn’t very helpful, nor the behaviour I would expect. For example, I might want to duplicate the Product.

Thanks
Clare

Hello

I also am having a problem with the hidden setting.

I’ve found that although the Timer column on the ‘All Products’ screen indicates hidden, in the Product edit screen the Catalog visibility is still “Shop and search results”.

This produces a number of problems with display on the front end.

1. My Shop catalogue is saying eg “Showing all 10 results” while displaying 9, because 1 is “Hidden” according to Timer while actually “Shop and search results”

2. Woocommerce Products by Category block still displays the supposedly hidden events

3. The following Woocommerce shortcode in block and widget hides the “Hidden” (according to Timer) events, but they are still counted in the limit because they are actually “Shop and search results”. As there are 2 expired products in these categories, only 3 products are displayed.
[products columns=1 limit=5 orderby="menu_order" order="ASC" category="66,67" visibility="visible"]

Therefore I consider this an urgent issue that needs resolving.
Thanks
Clare

• This reply was modified 5 years, 1 month ago by nothroughroad.

Done. It only took me 7 weeks! Also submitted another re adding new taxonomy from within a Pod post. I didn’t check whether either had been raised in the interim, so apologies if either are duplicates.
Thanks.

PPS. I disabled the REST API in the original Pod, and lo the Featured image panel appears in the classic-style editor.
It’s not a GeneratePress thing, as the same issue appears in the WP Twenty Twenty and Twenty Nineteen themes.
So my first post above is probably not a thing, and instead it appears to be a Gutenberg thing… grrr.