Hi, I recently navigated to my live website, and got this error. I don't believe I made any changes to any code to have generated this error. This does bring to my attention I need to turn off development mode, however, I feel I didn't create this error on my part. Not sure if this will help in further development of OctoberCMS but I'm loving the system and want to continue to use it and contribute to it's improvement.

I did fix this by logging in and updating the CMS. On update I'm assuming the correct files got rewritten and the CMS found the class it was looking for, however, what if there was no update available? How would I have gone about fixing this? Any idea what caused this?

I updated from build 162 to 165.

ERROR
We're sorry, but an unhandled error occurred. Please see the details below.
Class 'Cms546dfd239d44b_3927014416Class' not found
/home/{myusername}/public_html/themes/{mythemename}/pages/home.htm line 157
TYPE:PHP Content
EXCEPTION:Cms\Classes\CmsException
151
STACK TRACE
#    CALLED CODE    DOCUMENT    LINE
1    Illuminate\Exception\Handler->handleShutdown()    

Thank you, Bideo Wego

Same problem here, I also don´t know how to fix this.

Same here, using latest "stable" version. Until now I only got the exception after I make a change to a page or partial in the backend and then switch to the frontend and refresh the page. If I then go back to the backend and resave the page or partial, the exception disappears.

Me again. I could figure out that my problem was using a central in memory cache (redis driver in app/config/cache.php) where the generated class names (like above Cms546dfd239d44b_3927014416Class) are stored in. The php classes on the other hand are stored on the filesystem, which is pretty bad if you are using multiple webservers with different filesystems but just one central cache, where you get the list of classes from. Really strange behavior ... Anyway going back to cache driver "file" everything seems to be fine again. I will have a deeper look at this problem after holiday.

Happy christmas Tim

Hi Tim,

Thanks for reporting back! I'm also using Redis (as well as Zend OPcache), so that might be the cause indeed. Unfortunately I can't just switch to file based caching as I also use it for other stuff on that same server.

Happy christmas to you too,

Santo

So, I got this error every other day, and updating the CMS would do the trick, however, during the RC1 downtime, how do I fix this?

I do this. The issue doesn't occur now.

php artisan cache:clear should solve the problem. Not sure why it occurs but it's pretty common.

Last updated 9 years ago