Table CollectionAttributeKeys doesn't exist after upgrade
Permalink
Hey everyone,
I think others have had similar issues, but none of the advice works for me :(
I've just upgraded a site to 5.4.0.5 and I've managed to resolve most of the issues. The only one I'm left with is the search block (core block). When I perform a search I just get the above error back. I notice that the upgrade has deprecated this table, but surely the code has been updated accordingly?
I had overridden the block, but I have now deleted my override and tried adding a fresh search block and still get the error message.
I've also tried running the indexer from the dashboard. It's been running for about 30 minutes now :S
Any ideas??
I think others have had similar issues, but none of the advice works for me :(
I've just upgraded a site to 5.4.0.5 and I've managed to resolve most of the issues. The only one I'm left with is the search block (core block). When I perform a search I just get the above error back. I notice that the upgrade has deprecated this table, but surely the code has been updated accordingly?
I had overridden the block, but I have now deleted my override and tried adding a fresh search block and still get the error message.
I've also tried running the indexer from the dashboard. It's been running for about 30 minutes now :S
Any ideas??
Finally discovered that the issue was contained within an override we had put in place back when the timed release settings didn't work for the page_list model. Thankfully, this has now been fixed, so I've been able to just delete my override and everything started working again :)
Result!
Thanks for your help tho - didn't know about the Log::addEntry(). So usefull!
Result!
Thanks for your help tho - didn't know about the Log::addEntry(). So usefull!
If the cache is clear and it's still giving that error, I'd probably put some temporary Log::addEntry() calls in concrete/blocks/search/controller.php to see if that sheds any light on the situation.