Jesper Brunholm

I’ve found out why: the website in question has been moved (by way of copying) within the server, and for some reason the files shown in the editor in admin was not the ones that the system used for display.
When provoked a bit (removing the files in old position) the system began using the files I expect it to (those in new position), and I got the expected results as adviced by alchymyth and other.
Thank you very much for the help! ??

@alchymyth: thank you very much for looking into my problem.

The section of content-page.php looks like this in Edit Themes in WordPress admin (after having looked on another file in the editor, thus, I can’t understand how it could not be saved properly):

<?php /*
* <header class=”entry-header”>
* <h1 class=”entry-title”> <** php the_title(); **> </h1>
* </header><!– .entry-header –>
*/ ?>

I’ll have to debug through the php files to see if I can find a reason for the system to use another file than content-page.php (any suggestions are very welcome)

Thank you, but I don’t want to stand the risk of being search engine downranked.
Hiding header elements with css is a major no-no with respects to that.

I’m really having trouble with this. On e.g. https://jespervinther.dk/biografi/ I want to remove the bold Biografi right below the menu.
I’m running a child-theme based on Twenty Eleven (fully updated), with the 6 files listed below in the child-customisation. I have disabled the_title() in the child-theme content-page.php. Does any of you have advice as to what I’m missing here?

Thank you very much for all input, I’m growing desperate :-/

** Child theme files **

• content-page.php
• Footer (footer.php)
• Theme Functions (functions.php)
• Header (header.php)
• Showcase Template Page Template (showcase.php)
• Stylesheet (style.css)

I am sorry to say this, but making H1 content display-none is fairly bad advice with respects to search enginges – the risk of getting banned because you seem to try to cheat your page to a better rank is high.

I am looking for a solution to the same problem, but will not do this with css-workarounds. I’ll post if I find the solution.