Greybox
ParticipantForum Replies Created
-
Thank you for your quick answer!!
This is not quite true. I happened to upgrade to V2 on my staging site and import graphene-options-xxx.txt settings from my staging into my real site. Now my real site is forced to use my staging site favicon URL and the favicon file from uploads staging site folder. The old-fashioned favicon.ico in the public root folder is simply ignored if I don’t use native WordPress favicon feature.
Can I just use a text editor to remove “favicon_url” reference from my latest graphene-options-xxx.txt export file and re-import the edited graphene-options file into my real site? It seems that this fix has removed favicon.ico reference from the database on my staging site, but I wanted to check if this approach can be used for my real site.
Perfect! Maybe this should become a default?
On second thought, adding the admin bar will shift the header down. It is not very good when the header is supposed to be exactly in line with the background, that’s why I liked the (Edit Page) option which is not there anymore.
Thank you!
Thank you.
If we set the height that works for one mobile device without cropping, won’t there be a problem with another mobile device with a different resolution?
In reply to: HTTP ERROR 500 after upgrading to 2.0 – Graphene child theme problem
February 4, 2018 at 7:14 am #49032Problem resolved, thank you!!
I see, but I also noticed that my new Export Graphene settings graphene-options-***.txt file still contains reference to my old Favicon file URL. Maybe this reference should no longer be in the Graphene export settings file?
Please help me with this problem!
