URGENT, PLEASE HELP! Unserialize() error on Bluehost hosting

ThemeBurn SupportForumsOpenCart ThemesPavilion OpenCart ThemeURGENT, PLEASE HELP! Unserialize() error on Bluehost hosting

This topic has been marked as not resolved.

Hi,

We are trying to move my site over to Bluehost from Network Solutions, but are getting the following error type for some of my information pages:

Notice: unserialize(): Error at offset 18057 of 32596 bytes in /home5/victoug3/public_html/tb_themes/pavilion/library/DbSettingsHelper.php on line 156

My developer says he thinks it’s happening because, in his words: “theme developers saved all theme settings in single column of tb_setting table in serialize form & used them on front end by fetching form db & then doing unserialized, So on new hosting the data of the column is expend the limit of ideal column that’s why we are getting this error.”

We’ve had Bluehost update the php.ini file to:

- Increase the Max memory from 128 up to 512 M – this is as large as it can go
- Increase the Post size max from 60 to 150 M (this may be higher than the admin limit)
- Increase the Max expression from 30 to 150 (this may be higher than the admin limit)

Still I’m getting these errors.

Could you please, please take a look at what is going wrong and help us?? We need to be moved to Bluehost by June 1 before my hosting on Network Solutions renews, so this has become rather urgent!

Many thanks!

Megan

May 25, 2015 at 10:46 pm #41100

ThemeBurn Support Team,

This has been resolved. I had to re-create the 3 pages on my site that were strangely getting the error. Now they work fine. Still not sure what the issue was.

May 27, 2015 at 6:01 am #41114

Hello,

did you recently upgrade your shop to a newer OpenCart version ? If yes, can you please provide phpmyadmin url and user/pass so we can check the database settings. You can use hidepost to share private information with the support staff.

BR,
ThemeBurn team

May 28, 2015 at 9:39 am #41163
Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.