SocialBlogsite

If you know what a Style Sheet is and know that SEO rules, then you should know that the safest way to iconize a menu item or style each page/post list items with a different image/graphic/icon is by its slug, since it’s the only thing that you will ALWAYS keep the same, or search engines would lose your page’s index and value.
<h4>Some tips to save you the time with your theme development:</h4>
<ul>
<li>This can not be achieved with WP provided template tags.</li>
<li>Menu item ID# won’t get you the actual post ID#</li>
<li>Menu item title is EMPTY at least you name it differently by hand.</li>
<li>Page/Post ID could change by moving, re-importing and other content handling, breaking your style sheet.</li>
<li>Class names are possible since WP 2.9 but they need to be added MANUALLY, and?</li>
<li>?menus need to be activated and theme changed for them to work.</li>
<li>A new blog won’t take those menu classes from your theme.</li>
</ul>
There’s a limitation on current wordpess version that removes post-title and post-name from menu-items in database, to prevent them to be confused with the actual page. Yes, they are stored in the same table, and until all the functions are revised to be safe not to confuse nav-menu-items with posts or pages, you can’t get the name nor title nor url! Not with single wp template tags.
Although WP considers the ID of the post as the more safe and CONSTANT piece of data you can use to refer your article as, but that’s inside your WP installation, not extensible to the real world. The post or menu ID could change due to several factors like backing up your site, moving domain, replacing page, new menu items created, etc., but there’s something you will NEVER allow to change: the PERMALINK.
Consequences of changing the url of your post are so severe, that our best clients are those who let their website in hands some hacky guy who promised?miraculous rankings on search engines and they lost 50% of value (for a company depending on 2M internet sales).
Post and Menu IDs could change, breaking the link with your Style Seet rules, and losing your custom logos.
You might want to rather pay extra your developer to keep permalinks the same, than IDs.
So now the most SAFE and CONSTANT piece of data, for you, is the permalink, not the ID. You should do ANYTHING to get it done this way, regardless of what your programmer says is safer. He works for your Google rank, not for WordPress, so listen to me, not them.
After banging my head for days trying to get a solution for this, I realized nobody does it because WordPress doesn’t provide the data (yet).
If you are a WP guru, or a coder monkey like me, check the article about this plugin’s release for the code what will allow you to hack that wp class that can’t get the title:
If you wouldn’t hack your .php files, here’s a ready-to-use plugin, soon to appear in WordPress pages.
It’s very simple, but it adds your page / post’s slug ( sanitized-name-of-your-page ?or ?your-manually-entered-permalink ) to the class of the li that contains it. It also takes a little bit until your SEO defines the right permalink for your posts and you will still have to re-adjust the Style Sheet after his changes (until next release when this plugin will keep track of changes) but once the permalink is defined (they should be defined before making the post live, anyway) your icon / style will remain together with your menu item, regardless of the above scenarios where your post ID could change.
<h4>Features</h4>
Adds a pagenamed_name-of-your-page class to each menu / list item for you to style them different, working-around WP limitation on not saving page name or title or url of the related page in menu items DB rows.
Better than using IDs, since the permalink MUST stay FOREVER for Google indexing, while menu and page ID are important only inside WP database.
<ul>
<li>Adds a pagenamed_name-of-your-page class to each menu / list item for you to style them different.</li>
<li>Works for either custom menus or page listings made with the previous wp_list_pages() function.</li>
<li>Extra code to remove unwanted useless classes from menus (Need plugin editing)</li>
</ul>
<h4>Future features</h4>
<ul>
<li>It will keep track of changes made to permalink to update the stylesheet (even though is not recommended for an old page, to prevent losing indexed value in google)</li>
<li>Option in admin panel to remove unwanted useless classes from menus.</li>
</ul>
Don’t forget to rate it and tell it works! ⟩⟩⟩⟩⟩⟩⟩⟩⟩⟩⟩⟩
<h3>Instructions</h3>
Easy: Install and activate. No options yet (future releases will)
Check out <a href="http://socialblogsitewebdesign.com/wordpress-plugins/pagenamed-menu-classes/" rel="nofollow ugc">PageNamed Menu Classes plugin page</a> for bug reports, updates, help, and to find other interesting plugins.

PageNamed Menu Classes

The very first plugin to style your menu list or page listing items differently. ( i.e. custom icons for each menu! )

moxu

I created this plugin because i wanted this feature (to set a specific locale for frontend) out of my themes. I’m assuming i’m not the only one who would preffer to have the backend en_US only, so here it is…
It’s not tested with other versions of wordpress except 3.4, but it should work without a problem at least from 3.0 onwards.
This plugin assumes you’re not using a translation plugin , so, if you have bilingual or multilimgual blogs, use with caution (and let me know … especially with qtranslate 🙂 ).
I’t not multisite tested/ready yet.

LanguageBack

Simple , minimalistic plugin that lets you set different locale for frontend and backend.

PageNamed Menu Classes vs LanguageBack