gtra1n

Well, perhaps it’s not a permissions problem, but it’s absolutely NOT an incorrect password/username combination – they are stored in and copied from 1Password. Trust me that after several dozen entries I have eliminated that as the source.

Also, I’ve created a dummy Editor level user, tried those credentials in Blogsy and Byword and get the same problem. This is why it seems to me to be a permissions problem, attached to a very specific protocol.

Okay, I actually solved this by trashing the Blog page, so clearly I was missing the point that the blog is built in and a Blog page is something superfluous. Confusing human and code languages again!

I have changed functions.php back, but more specifically I made the ‘show_home’ argument “‘true'”; this matches the file on my localhost installation, but the functions.php file at my server installation showed the argument as “‘home'” – this was not an edit that I made, but perhaps the source of my original problem. I have no idea how that change got into the functions file.

Now, with ‘true,’ my fix is holding, but I do want to point out that the edit you are warning against actually did fix the problem, and the problem was an actual case of the software not responding as indicated to actual settings.

I fixed this by changing the ‘show_home’ argument to “Home” in functions.php of the Twenty Eleven theme. This gave me a navigation bar title of Home for the static home page and Blog for the blogposts page (previously, nav bar labelled each as “Blog”).