-
AuthorPosts
-
April 20, 2016 at 5:43 am #617983
Hi-
I have noticed that the header for my site looks different in private browsing mode on mobile (ios, iPhone using Safari). Often the little icons at the top for pinterest etc just show empty boxes… and the menu hamburger box also is empty, but still functions.Here’s a screen shot with an example:
It looks fine in “normal, non private browsing mode” and also looks fine in Chrome mobile browser in incognito mode.
Any idea what would be messing up the rendering? Has anyone run into this before?
Here’s a link to a sample blog article for your reference so you can replicate… sorry if it makes you hungry ha ha!
http://www.thomashenthorne.com/le-comptoir-san-rafael/April 21, 2016 at 1:54 pm #619142Hey!
Have you checked it on another device? i can’t reproduce the issue on my end.
Best regards,
JosueApril 22, 2016 at 9:38 pm #620227Thanks Josue. I am seeing it on our other iPhone as well.
Today in “Incognito Mode” on chrome desktop I saw this error at top of page and menu froze:
“Warning: Class __PHP_Incomplete_Class has no unserializer in /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-content/object-cache.php on line 520Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-content/object-cache.php:520) in /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-content/plugins/optima-express/iHomefinderStateManager.php on line 35
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-content/object-cache.php:520) in /home/content/p3pnexwpnas08_data02/27/2854827/html/wp-content/plugins/optima-express/iHomefinderStateManager.php on line 35”
Cache cleared, all plugins updated.
Are the two related?
Everything works fine in normal mode where cookies can be set.
Thanks!
April 22, 2016 at 10:40 pm #620250Hm, no i don’t think that’s the source, the issue looks like it’s related to CORS (http://kriesi.at/documentation/enfold/enable-cors/). Here’s what i see btw – http://screencast.com/t/DagfnuBp (i’ve checked on Android too).
April 22, 2016 at 10:47 pm #620252Thanks for the response!
I cleared the Go Daddy cache and then reloaded the page and the error was gone… Enfold and Go Daddy seem like a fighting married couple sometimes… ha ha…. Go Daddy doesn’t let Enfold upload photos and displays these errors… I do wonder if there is some sort of cache configuration that needs to occur with Go Daddy to make it play better with Enfold? It seems like the HTTP errors (different thread you were helping me on) go away temporarily if I clear the Go Daddy cache, but then they come back about a minute later.
Thanks for your help…. I won’t worry about this since it’s just in incognito / private browsing mode and seems to go away when cache cleared.
April 22, 2016 at 11:10 pm #620254Glad you managed to sort it out, have a nice weekend :)
Regards,
Josue -
AuthorPosts
- You must be logged in to reply to this topic.