Tagged: unserializer, wordpress update
-
AuthorPosts
-
April 19, 2016 at 4:37 am #617062
Yigit really helped a few hours ago and did an amazing job, but we just noticed the transparent logo is not showing correctly as transparent on the main News/Blog page on Mobile version.
Everything should already be set to transparent header in the option on the bottom right and in the theme etc.
All the other pages were fixed and look great, but that one page is not showing the correct transparent logo on mobile. Thank you for your help finalizing because it is urgent.
I posted the topic this is from in the private info below because it was closed to responses because we didn’t realize the News page wasn’t showing correctly. Thanks again for your help!
April 21, 2016 at 6:34 am #618930Hi newuser1!
Thank you for using Enfold.
We checked the blog or news page and it is using the same logo as the home page. However, the logo in the news page is not discernible or visible because of the background image.
Could you please provide a screenshot of the issue?
Cheers!
Ismael- This reply was modified 8 years, 6 months ago by Yigit. Reason: moved content to private field
April 21, 2016 at 2:32 pm #619192***URGENT PLEASE HELP, WHAT WAS CHANGED??? WE JUST POSTED AND STARTED SENDING ALL OUR TRAFFIC TO THE NEW WEBSITE LAST NIGHT. THE SITE WAS WORKING FINE AND EVERYTHING WAS SHOWING FINE ON MOBILE ON ALL PAGES AS OF YESTERDAY EVENING.
NOW TODAY ON MOBILE IT IS SHOWING A BUNCH OF CODING AND ERROR MESSAGE ABOVE THE HEADER ON ALL THE PAGES. PLEASE FIX BECAUSE THIS IS URGENT!!!!
IT IS SHOWING THE FOLLOWING ERROR CODES ON MOBILE ABOVE THE HEADER AND THE SPACING IS ALL MESSED UP AND WE HAVE NOT CHANGED A SINGLE THING TO CAUSE THIS:
Warning: Class __PHP_Incomplete_Class has no unserializer in /home/content/p3pnexwpnas10_data02/27/2725027/html/wp-content/object-cache.php on line 520
Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /home/content/p3pnexwpnas10_data02/27/2725027/html/wp-content/object-cache.php:520) in /home/content/p3pnexwpnas10_data02/27/2725027/html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries.php on line 32
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/content/p3pnexwpnas10_data02/27/2725027/html/wp-content/object-cache.php:520) in /home/content/p3pnexwpnas10_data02/27/2725027/html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries.php on line 32
THANK YOU!!!!!!
April 21, 2016 at 2:58 pm #619208I don’t know what was changed, but now it is showing fine. Thank you if you guys changed or fixed something. We appreciate your help.
April 21, 2016 at 6:03 pm #619286We are getting something similar on IE version 11:
Warning: Class_PHP_Incomplete_Class has no unserializer in /home/content/p3pnexwpnas10_data01/14/261231/html/wp-content/object-cache.php on line 520
http://www.onesourcebackground.com
- This reply was modified 8 years, 7 months ago by onesource_marketing.
April 25, 2016 at 10:59 am #621146Hey!
glad you got it fixed.
Have you got the same issue when using a default WordPress theme? please let us know about your results.
Cheers!
AndyApril 26, 2016 at 6:57 am #621929Hi – I’m receiving this same issue and the exact same error line 520…
All plugins are updated, WordPress latest version, and of course latest version of Enfold.If I clear my cache (Go Daddy Managed WordPress), the error goes away…. but then returns.
This seems to have occurred in the last 2 weeks since the last few updates.
This occurred tonight when I was trying to retrieve the Yoast sitemap for my site. It seems to also happen more in private browsing mode, where cookies are not allowed to be set / persistent.
Any ideas on what could be happening? I am seeing the error more and more, getting concerned.
Thanks!
April 26, 2016 at 2:21 pm #622146Same thing continues to happen to us every time we try to retrieve the Yoast sitemap for our site. Everything is updated as mentioned above and we have cleared our cache etc.
April 28, 2016 at 1:55 pm #623722Hey!
have you got the same error when using a default WP theme?
Cheers!
AndyApril 28, 2016 at 3:12 pm #623810@Andy
I spoke with GoDaddy yesterday. WordPress just released a maintenance update 4.5.1. And GoDaddy is rolling it out to update WP across all of their users. I’m assuming this will fix this issue. My warning isn’t constant. I’m on a Mac and use Chrome and the site loads as usual. But others using IE or Firefox have noticed they get this warning on the initial visit to our site. Some say if they leave our site and come back, it loads as usual. When I checked Safari the hero image on our homepage was super zoomed in. But if I left the site and came back, it loaded fine. So it sounds like it’s a caching issue. Again hoping this update will fix this.April 29, 2016 at 4:08 pm #624605Hi!
Have you been able to apply GoDaddy update? If you have, has that fixed the issues?
Regards,
YigitApril 29, 2016 at 4:39 pm #624636Unfortunately, GoDaddy has not updated my version as of today. I hope it happens soon. I was advised to wait vs. installing it manually. I will keep you posted.
May 2, 2016 at 5:42 am #625447Hi,
Ok, thank for letting us know. We’ll keep the thread open in case you should have any more problems.
Regards,
RikardMay 6, 2016 at 3:12 pm #628339Please see urgent request in private content below. Thank you!
May 6, 2016 at 3:38 pm #628355**UPDATE**
GoDaddy has since updated our version of WP. They checked on their end and had no Warning message pop up when accessing our website. They feel it’s a caching issue with the website visitor’s browser. The only thing it looks like we can do is tell clients and prospects to make sure they are using the most current version of their browser (Chrome, Firefox, Safari, IE, Edge). And make sure they flush their browsing history.Since this, we are still getting clients calling in and telling us they have this warning. Not consistently – just random. I have updated my coworkers with this information. The update didn’t really fix the warning. So I guess we just deal with it.
May 9, 2016 at 6:06 pm #629401Hi,
@jend_onesource our devs are informed about the issue and we will be adding if there is anything necessary on our side on upcoming updates.@newuser1 Done :)
Best regards,
Yigit -
AuthorPosts
- You must be logged in to reply to this topic.