jolato

Sorry, please delete this question.

Ok, I found the solution and I’ll share it here. In Simple CSS you enter the following, as an example (reduces to about half the height):

/* Banner – styles used in case the user sets a header image */
.has-banner .site-branding {
padding: 100px 0 60px;
}

Just play with the padding to adjust the height to your liking.

Thanks, it’s nice to hear that these plugins exist. Anyway, to avoid all risks, I would prefer to create a separate test site, explore the upgrade procedure there and see for myself if there are any hidden pitfalls.
My question is whether there exists a reliable procedure to create such a copy of the production blog ? I admit I did this once successfully a long time ago, but I don’t remember all steps. What I do remember is that if you don’t take care of some special config file(s) that contains the name and access information to your database, it was impossible to enter the test blog (i.e. upon entering, one is redirected to the production database or st like that). I think you have to keep the copy of your production config file, edit it and change some link to the new database (copy) and that this had to be done using php admin … not sure anymore.

Sorry, what did you say about maintenance plugins ? You ment the WP upgrade pluging ?

Thanks. So next question, of course there must be some standard upgrade procedure, but in stead of executing this against the production blog, wouldn’t it be better to copy the blog to some test environment, upgrade and check before going live ? What is the common approach to this ?

I would also appreciate if you could show me the link to this upgrade procedure so I can have an idea of the complexity.

Rgds,
Jo

I am still not following. Ok, technically a title tag is just an HTML tag, no problem with that.

But to take it step by step, what does the standard comma separated tag-box under the WP2.2.1-editor do ? Does this improve visibility ? It’s not a title tag-box apparently, since if I enable the SEO title tags plugin, the latter adds a box saying “title tag (optional)” above the previous one. So what does this one do for improving visibility on top of the previous one ?

My goal is to improve visibility, that’s all. If one of them does this job, then ok for me. But think of this: my question just reflects the confusion that exists about these plugins, what exactly they do and what the difference is between them. Everybody talks about title tags but nobody shows what that really means.

After my research on the net for two days I still don’t know how they overlap or complement each other. I know that in WP2.2.1 by default one disposes of a comma separated list of tags to fill in. SEO title tags seems to add a second title tag box and offers a million options to configure nobody cares about. Simple plugin offers another zillion options. No wonder I pose this question. Only the meta tag plugin is an “install and go” approach which I like !

yeah, you’re wright. I use K2 0.9.6 on WP2.2.1.
So far, I was able to change the font size for the whole blog by going to the stylesheet body section and add the font family I want:

body {
font: 72.5% ‘Lucida Grande’, Verdana, Arial, Sans-Serif; /* Resets 1em to 10px */
…
}

But after this change, the title font size is way too big in comparison with the text of posts. I don’t have a clue about how to ONLY change the title font size of each post.

… except for the wp-condig file which I did NOT overwrite

Yes, but I think I set it up that way, see wp-config below and of course I copied all folders from source to “test”, after deleting all files of “test” first:

TEST
define(‘DB_NAME’, ‘patrizia_wrdp1’); // database
define(‘DB_USER’, ‘patrizia_wrdp1’); // Your MySQL username
define(‘DB_PASSWORD’, ‘***’); // …and password

SOURCE
define(‘DB_NAME’, ‘patrizia_wrdp3’); // database
define(‘DB_USER’, ‘patrizia_wrdp3’); // Your MySQL username
define(‘DB_PASSWORD’, ‘j6cM4zBu225i’); // …and password

.. which I did but same result. I suspect that my yahoo accountis POP and not POP3

I have run postie config and it said this:

Unable to connect. The server said – POP3 connect: Error [110] [Connection timed out]
Try putting in your full email address as a userid and try again.

Yes, I was not clear. I used postie to begin with. It always returned the same boring message “you have no new mail”, even after the above set-up etc. So out of curiosity I manually launched wp-mail and also got the same message. Then I learned from someone that this last message was actually a misnomer and I adapted the code of wp-mail.php to have a more meaningfull error message. After that I got the “login failed” message, so I presume that this is also the reason why postie doens’t see any new mail ?

Hope that helps,
Jo

I also can’t get postie (WP2.2.1/Postie 1.1.1) to work, although the postie config doesn’t give any errors. But when I run wp-mail manualy I get “login failed”. Of course could be the pw but that seems to work fine when I log in manually to the webmail. Any idea ? Very new to this.
Thanks in advance,
Jo