Forum Replies Created
-
Mod
Try disabling your plugins and reloading your page.
You haven’t edited theme files, have you?
Mod
Yeah, but “traffic” does not equal “regular readers”. There are plenty of sites I only visit once because although they may have the information I need/want, it is too difficult to find it. Usability is the key issue.
Mod
In reply to: Graphene theme – Google chrome doesn't work correctly
October 9, 2014 at 1:44 am #43587It’s a browser caching issue. Apparently, Chrome is keeping its cache longer than IE. Empty the browser cache and everything should be fine.
Quote:Every thing works great in IE.There’s something you don’t hear everyday, lol.
Mod
Quote:the header on a mobile the header text is jumbled“Jumbled” can mean a lot of things. Can you please provide a link (preferably), a screen cap, or a more accurate description?
Mod
Quote:Is there a limit to the number of menu items you can have?No, but you may be running into memory issues on your server.
Quote:I have a total of 76 menu items (posts) along the 8 columns.At some point, a menu that large becomes unusable to your users and a real disincentive for them to stick around or come back. You may want to rethink your approach to this.
Mod
In reply to: Location Needed – Where To Call Funtion (Within Post)
October 3, 2014 at 1:05 am #43558I don’t know what code you are using to create that function (?), but you could add it to a Graphene action hook widget area.
Mod
Site shows up fine to me.
Put code in between backtick (
Code:`) characters. It’s usually located above the Tab key on your keyboard. I have fixed this for you above, but your code may have been permanently altered.
Mod
http://docs.graphene-theme.com/Slider_options
Moved to Support
Mod
That worked in Firebug. Be sure to clear browser and server caches before refreshing the page.
Mod
In reply to: Header Image Disappears on "Search Results not found" page
October 2, 2014 at 11:30 pm #43564Oliver,
See this post:
https://forum.graphene-theme.com/graphene-support/no-header-at-not-found-page#post-41430
You can use that solution in the mean time. It will be fixed in the next update, however.
