Closed mikedotmundy closed 10 months ago
We are also seeing this with Rock v15.2 and plugin v2.4.1.14
Hi @mikedotmundy , @JRichmond27 . This is a relatively harmless exception that's basically Rock saying 'I have a record of CentralAZ blocks in my database, but I'm not finding them on your file system. If you end up wanting to use them I don't know what to do.'
You should be able to resolve it by going to CMS Management > Block Types, and removing the old com_centralaz/RoomManagement blocks.
Thank you @tcavaletto! Glad to know this is harmless, but still rather annoying as it could take 30+ seconds to load the zone editor.
2 of the blocks were there and I removed them. However, this Block did not show up in the list, and it is still throwing an error any time I try to load the zone editor on any page. Thoughts?
It looks like it does show up under com_bemadev
. Is it safe to delete?
Please go through all the tasks below
Please provide a brief description of the problem. Please do not forget to attach the relevant screenshots from your side.
When loading the Zone Editor on any page, it takes anywhere from 20-30 seconds to actually pull it up. So I did a quick search in Rocket Chat, and found this thread: https://chat.rockrms.com/channel/cms?msg=dRaqgNk8C39Z4dADy
So, after reading that I looked at my exception log and found 3 exceptions that happened at the exact time I tried to pull up the Zone Editor.
It seems that Rock is trying to compile some old blocks, but is running into errors.
We originally had the Central AZ Room Management plugin, but have since upgraded to the Room Management 2.0 plugin. So, my question is, is there anything that may not have been migrated properly when installing the 2.0 plugin that is still referencing these old blocks?
Expected Behavior
No error.
Actual Behavior
Error as displayed above.
Steps to Reproduce
See above
Rock Version
v16.0, v16.1
Plugin Version
v2.4.4.14
Client Culture Setting
en-US