Forum Replies Created
-
Mod
Oddly, though, I have not had any of the problems that people have been describing with their feeds — because I use FF for a feed reader, not Feedburner.
Okay, a third option:
Incorporate the site title and site description into the header image (with Photoshop or GIMP or whatever image editor you use), do not use the theme’s default site title and site description (just leave these blank in Graphene options), but use an action hook widget to enter whatever you would like for those, and then set their display value to
none.I think I get your point now. So basically, you want to remove the class assignment from the H1 tags?
Okay, I can think of two ways to do this, without editing the theme’s files (which you want to avoid).
One, use a custom function in a child theme’s functions file to strip out the class on these elements. (I’m not entirely sure how easy this is, however. I will be totally useless in helping you to implement this.)
Second, do not use the theme’s default site title and site description (just leave these blank in Graphene options), but use an action hook widget to enter whatever you would like for those, and then position them with CSS. I can help you out with this if you need help.
I also have a list of miscellaneous resources here:
After a bit of hectic CSS self-learning,
Did you see the resources we have listed here? –> https://forum.graphene-theme.com/graphene-support/beginners-resources-possible-sticky
Apologies for all these posts!
We have a few members who use this forum to think out loud. Since this forum is meant to be a repository of knowledge, I think it’s probably a good thing, especially if you include suggestions/hints/examples of what you tried that worked and didn’t work.
If I may make a suggestion: Your links that are
#C4BEEAare a little light on my screen. You might want to make them just a little darker. (Maybe something halfway between that and your visited color.Other than that, it looks great!
No problem.
BTW — the easiest way to disable all plugins is to temporarily rename the plugins folder (via FTP).
Once I knew the crud wasn’t coming from the graphene code, I just went in
and blew away all of the plugins, (and extraneous themes) and re-installed only
what was necessary.
It’s amazing how much unused stuff piles up in your wordpress folder. It’s probably a good idea to go through there every once in a while and clear out stuff that hasn’t been used in ages.
I totally crossed my fingers, and it totally didn’t solve the problem
I am totally LMAO! Thanks!
Well…..
Front page: site title is h1, site description is h2, post title is h1
Other pages: site title is h2, site description is h3, post title is h1
The default h1 tag is the text in the navigation
The navigation menus use lists to create their items, not h1 or h2.
Nobody would search in Google for ‘contact me” So I prefer to change the h1 to something more descriptive such as “Contact Michael McDonald” .
Post titles are always the only h1 items on a post, unless you add an h1 item in your text. (Hmmm…I may have to edit a lotta buncha posts now.) When you create/edit the post, change the post title to “Contact Michael McDonald”.
was dismissed for nit-picking
Yes, extended discussions of SEO make some of us feel a bit, well, stabby, especially when dealing with zero-content sites. Search engines are always tweaking their algorithms to take into account people who try to game the system. Good content and good structure are the keys.
That said, you are talking about good structure here. I don’t understand your comment that Graphene isn’t following SEO best practices, because, with the exception of the front page, it is pretty much following what you have outlined here. If I’ve missed something (and I have a feeling I have; it’s late and I have a splitting headache), please enlighten me.
Cheers,
Ken
BTW, SEO best practices according to whom? (Got a link?)
In reply to: Cannot access wordpress admin-Probably not a Graphene Issue but thought, you have great support
February 24, 2012 at 2:14 am #24739In general, URL’s are case-insensitive. (This is not always the case on some sites that provide free hosting, however.)
There are two basic ways to upgrade your theme (and WP for that matter): from the Dashboard, and via FTP.
Even though upgrading from the Dashboard is the easiest way, the disadvantage is that you can only do this when there is a new upgrade available.
You can upgrade via FTP anytime (and even roll back to a previous release), but you first must have FTP access to your site (not all hosts allow this, depending on your installation), and you must have a current copy of the theme on your computer.
Is it possible to switch to another theme, uninstall+reinstall graphene,
then switch back to graphene theme without losing all the custom configuration ?
There is no need to switch to another theme. If you have FTP access, follow these steps:
1) Download a copy of Graphene from the theme repository to your hard drive.
2) Unzip the file. You will now have a folder labeled “graphene1.6” on your hard drive.
3) Inside that folder is another folder labeled “graphene”. (No version number.)
4) Login to your ftp account and navigate to the “wp-content” folder. Open that folder.
5) Find the folder labeled “themes”. Open it.
6) Copy the entire “graphene” folder (from step 3) to the “themes” folder. If you are overwriting a previous installation of Graphene, your FTP client will ask if you want to overwrite the files. Click on “Yes” or “Yes to All” if it’s avaialable.
7) Don’t do anything until the upload is completed.
There are times when upgrades don’t load all the new files, resulting in all sorts of errors. This may be what happened to you. Reuploading a complete copy of Graphene 1.6 may solve your problem.
Is the configuration information stored in SQL or in files which can be preserved
over the reinstall cycle?
Yes, Graphene stores its settings in the database. As long as you don’t touch the database, your settings should be retained if you follow the steps above. You can also use the “Import/Export Theme Options” in Graphene’s options pane.
I’m not quite sure where the “code-crud” you are getting is coming from. Are you using a child theme? You should never make modifications to either WordPress or theme core files. Any modifications you make should always be through theme options or through a child theme.
Actually, I think what you want is to just eliminate the hover state. To do this, you will need to find the hover codes in style sheet, copy them to your child theme style sheet (or custom css) and make them match the default state for the menu.
It’s going to take some knowledge of CSS and a bit of digging through the style sheet.
