Skip Navigation

[Resolved] unexpected attempt of restoration of block

This support ticket is created 2 years, 3 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 3 replies, has 2 voices.

Last updated by antonK-2 2 years, 3 months ago.

Assisted by: Waqar.

Author
Posts
#2451189
Снимок экрана 2022-09-05 в 19.43.45.png

attaching unexpected attempt of restoration of block. Please advise how to avoid it as restore a lot of blocks takes a lot of resources.

Thank you
Anton

#2451429

Hi Anton,

Does this content template includes any block(s) from a third-party plugin or theme, which is no longer active?

To troubleshoot this, I'll need to see how this content template and its blocks are set up and you're welcome to share temporary admin login details, in reply to this message.

Note: Your next reply will be private and making a complete backup copy is recommended before sharing the access details.

regards,
Waqar

#2452163

Thank you for sharing the admin access details.

I noticed that an incorrect post type was selected for the "View with" field in the content template named "МИУ Онлайн".
( screenshot: hidden link )

As this template is being used for the "МИУs Онлайн" post type, I've selected one of its posts "МИУ Апрель 2022" and it is no longer showing the message for an invalid block that needs to be recovered.

If you see a similar issue in some other template too, please make sure that the correct preview post is selected in the "View with" field at the top.

#2453193

My issue is resolved now. Thank you!