Dave333

Glad it helped Chairbeat.

Andrew,

The lack of any indicator leaves the visitor thinking each of the nav items are single page links. If ther are no sub menu indicators you rely on the user hovering over every nav item to accidentally discover a sub menu. If they are not interested in one of these links that has a drop down sub menu, without the indicator they will not hover over the link to discover a whole sub section of the website. It makes no functional sense to not make this clear to your visitors and to instead have them guess, or accidentally discover parts of your website.

The presence of downward pointing arrows gives at least some indication that there are more nav items below.

Downward pointing arrows are the most common indicator for sub menus. If you can think of a more appropriate indicator, please offer them as suggestions.

You are free to have your own opinion and I have no interest debating it with you. I’m just offering the suggestion for future updates to Twentytwelve. Developers of Twentytwelve can take it on board or not. I do think Twentytwelve is their best default theme yet and is a great base to start from. This is just a small suggestion for improvement.

I’ve been wondering about this myself. Seems an odd thing to remove.

Thanks Andrew. Done.

I can’t agree. The drop down arrows indicate that there are a sub menus, it is a functional necessity, not a “favourite feature”.

Without them the user has no idea there is a whole list of pages under that heading. The absence of the arrows is unnecessarily hiding whole sections of your website from view.

It’s got nothing to do with what one likes or doesn’t like, or in the eye of the beholder. It is about basic functionality, or lack of.

Thanks Emil!

That worked really well. However, it’s only one colour, the dark #444 is only usually used for the active menu item. So I changed it to this:

.nav-menu li > a:after {
    color: #888;
    content: ' ?';
}

.nav-menu li > a:hover:after {
    color: #444;
    content: ' ?';
}

.nav-menu li > a:only-child:after {
    content: '';
}

I really don’t understand why this wasn’t part of the theme to begin with. I guess there are lots of improvements. Still, this is their flagship theme, you’d think they’d make it perfect to demonstrate how excellent WordPress is.

Thank you for that. It seems overly complicate though for the simple addition of an arrow, which I suspected would be a CSS tweak to add an image background to the heading of a sub menu.

Thanks Stefano,

I’m happy to describe my first impressions and difficulties experienced.

The first thing I did was go to the first tab, Welcome & Support, to read about how to set it up. The First Step says:

Newsletter works out of box. You don’t need to create lists or evenly configure it. Just use your WordPress appearance panel, enter the widgets panel and ass (typo) the Newsletter widget.

The spelling error in the first step raised a bit of a red flag, making me wonder if the rest of the documentation was going to lack attention to detail.

I added the widget to my sidebar but all I got was a small round grey image. I wasn’t sure if I had missed something in the very basic instructions so I went and read the first step again. I wondered again about the lack of attention to detail and thought perhaps you had accidentally omitted some of the instructions.

I then went back to the widget and read the details on the widget:

The subscription form is created according the subscription panel configurations and appended at the end of the introduction text. If you want to place the form in the middle of introduction text above, use the {subscription_form} tag.

So I added {subscription_form} into the description, thinking perhaps this was required in addition to the instructions under the First Step.

At this point I was confused but sure I had done as instructed but didn’t understand why it wasn’t working.

It turned out that the small grey image that the widget created on my sidebar was the Subscribe button. I found the setting on one of the many pages that allowed you to add text to the button, and a blank box to enter your email address. However, I have just gone through all the pages in the settings of the plugin twice and I can’t find those settings again.

I suggest that you don’t claim that it works out of the box by simply adding the widget to the sidebar. Even if I were able to do that and get a Subscribe button and a box for the user to enter their email address, I would still need to create a newsletter and configure the other settings for the subscription to actually mean anything.

I’ve solved the problem.

It turns out that I should have changed the db_version setting to match 3.5, which is 22441 and NOT the previous version (21707) as instructed by the Codex.

I don’t know if the Codex is therefor incorrect or if my situation is an isolated weird case. Perhaps someone else will find this information useful.

I have experienced the same problem. All featured posts that are not supposed to be visible on the home page are now showing. Also, the most recent post is appearing at the bottom of the home page, due to all the featured posts appearing above it.

It was only after disabling the plugins one by one that I found the WP e-Commerce plugin to be the problem.

If I disable the WP e-Commerce plugin then the featured posts are no longer visible on the home page, which is how it should be.

I upgraded without a hitch on the first 5 sites, then on the 6th one I was told that WordPress Database needs updating. I went ahead as prompted but was then taken to a white screen with the WordPress logo.

Now every time I try to login to the admin on that site I get the same message and the same blank white screen.

I found this link for downgrading to a pervious version of WordPress in another thread:
https://etuts.org/manually-downgrade-wordpress/

I don’t have any shortcode in my functions.php file either. I tried adding this one inhouse gave but still can’t get captions working. Is there something I need to wrap these two lines of code with? Does the code have to be added at the top of the bottom of the functions.php file?

I’ve got the same problem with duplicate titles caused by this plugin. Uninstalling the plugin did the trick.

Documentation would be very helpful. Without instructions on how to use it, all the work creating the plugin is wasted.

I keep getting told I don’t have permission to view the stats, and I am the admin, I have the highest rights that a user can have.

Then I was told I entered the wrong API, but it is the correct API. I even got them to email it to me to be sure. It won’t even accept the API emailed to me by WordPress!

Jetpack is such a pain.

I think the best thing to do is delete the buggy, virus-like Jetpack and go with a 3rd Party plugin for statistics and any other features that Jetpack pretends to offer.

Well, I will never trust jetpack or any other cloud service with my data if I can’t make backups myself.

Exactly! When the stats were kept on my server using WP Stats I never once had a problem in all the years I’ve used it on over 8 websites. With the promise of all the greatness that Jetpack would bring I stupidly went and installed it on half of those sites. I should have only tried it out on one website as I’ve now spent many hours dealing with all the problems caused by Jetpack.

WordPress, if you are going to insist on pushing such a crappy service such as Jetpack on your users the least you can do is support them and help your users through all the bugs and problems it causes.

Better still, just ditch it. There is no need for WP.com and WP.org to be combined. WP.com offers nothing that WP.org doesn’t already have. It was a stupid idea to begin with.