ArnoAnou

It indeed was an error in the theme that came with the WordPress 5 update. The respective php just needed a one-character-change: from “get_the_date( ‘[some character I already don’t remember]’ )” to “get_the_date( ‘c’ )”.

Thank you very much for your help!

Worked well! Thanks Ben!

To add to this: Editing css and even php is made pretty easy by the developer, thanks to well-arranged and annotated code and the fast support. As a non-coder I never had such a nice experience working within php code and creating a child theme. Thanks!

So, I hesitated to do this because I expected a whole lot of difficulties, but I finally did it and it worked like a charm. Thank you Ben for your help. I never edited php without any problems before and I just did. Wow!

Maybe you want to have a look at it? There’s a before-main-content widget containing the newsletter form. It’s just shown on the blog page (thanks to a plugin) to not be to pushy and because it doesn’t work with the hero-image-template of the posts and pages (just looks weird between title image and article). There’s a after-main-content widget between content and footer containing the tag cloud, it is full-width on the hero-image posts and pages and I didn’t figure out how to change it without changing in on the front page, but we kinda like it. Plus there’s a footer widget containing a search bar.

We wanted to do this because of the full-width-two-column layout we chose for the blog page and the hero-image templates without sidebar we chose for articles and pages. Because of this we had no widget areas left on the blog page, and just “inline” widget areas for posts and pages. Which for us weren’t good places for either of the widgets I mentioned. (I’m mentioning this because that maaaaaaay be thoughts other users might have too.) I’m so happy it works and that it looks fine. Thanks Ben!

Thank you Ben for doing all this! I’m gonna mark all this as resolved. There are still one minor issues to note, but it shouldn’t really bug anyone, so, just for your information:

I still had some css in place, so I didn’t notice, that the backgrounds of the heroimage sidebar templates still work differently than those of the other two hero image templates: The white background of the the former includes the comments, the white background of the latter does not.

My solution:

.hero-image .main-content-container {
	background: #ffffff;
}

Thank you Ben for your help!

• This reply was modified 6 years, 9 months ago by ArnoAnou.

Oh, one more thing (again, sorry): If I have a dropdown menu in the secondary navigation the hero-image title will appear in front of the dropped down menu.

Don’t worry, that’s not what I’d call a delay. That was pretty fast, thank you very much!

One last question: Is it possible to use the hero image template for pages, too?

One bug (I think so): The date on the author-sidebar shows the current date, not the date the post was published.

A different solution would be to make the background of the comment section all white, too. But without changing the background for the blog.

(Edit: Found out, all other hero image templates do have a white background for the comment section.)

• This reply was modified 6 years, 10 months ago by ArnoAnou.

Thank you! I like it!

However: The background color which before was right and left of the article now only starts just right above the comment section, which looks a little weird in contrast to the rest of the page. I tried to solve it with the following css, which kinda worked for the article but it messed up the blog page. Do you have an idea?

.post {
	background: #b8b2a0;
	box-shadow: none;
}

.post-content {
	background: #ffffff;
	outline: 1em solid #ffffff;
}

.post-author {
	margin-top: 5em;
}

Everything works just fine! Thank you so much for your help! That’s some A+++ service. Thank you Ben!

• This reply was modified 6 years, 11 months ago by ArnoAnou.

Okay, the problem was me the whole time. Looks like the Firefox page search doesn’t search in scrollable windows or something and it never occurred to me to think I could search this code better than the software.

I have the function from line 105 onwards. On line 117 it says:
<span> <?php echo esc_html_x( 'said:', 'COMMENTER said:', 'ignite-plus' ); ?></span>
Is this the line I want to delete?

Everything else worked just fine. Thank you very much!

We updated but some questions remain. Sorry!

* I still can’t find the “ct_ignite_customize_comments” function in the functions.php. If I search for the name of the function or the code I’m supposed to delete there are still no results. Line 75 reads: “‘name’ => esc_html__( ‘After Page Content’, ‘ignite-plus’ ),”.

* To change the “Published” text I now have the right file but don’t know the lines to change and how to do this (Sorry, still a php noob).

* To change the “Write a comment” text I too have the right file and don’t know how to proceed. In line 20 (not 22?) in the comments.php it reads “<?php comments_number( __( ‘Be First to Comment’, ‘ignite-plus’ ), __( ‘One Comment’, ‘ignite-plus’ ), _x( ‘% Comments’, ‘noun: 5 comments’, ‘ignite-plus’ ) ); ?>”. Can I just put it like this: “<?php comments_number( __( ‘CUSTOM TEXT’, ‘ignite-plus’ ), __( ‘One Comment’, ‘ignite-plus’ ), _x( ‘% Comments’, ‘noun: 5 comments’, ‘ignite-plus’ ) ); ?>” ?
Line 43-45 and 65-67 reads “

<?php wp_list_comments( array( ‘callback’ => ‘ct_ignite_customize_comments’) ); ?>

“, I don’t know what to change here.

Sorry, I don’t know if it’s right to come here with such specific questions and requests. You’re doing some fine work on some very fine themes and I probably shouldn’t be tying your time to this. But since you keep on giving . . . I can’t help but ask again. Thank you so much for the support you gave, just tell me when it gets exhausting (I can’t tell) and I should start find a php course and su. ??

Best,
Arno

Oh, I didn’t think of this. It’s ignite 1.76 instead of 1.80. I’ll be talking to my co-bloggers to renew the license (since one of them is planning on setting up a new blog, we will possibly consider the VIP package.) I come back to this when a decision was made. Thank you so much for your help.

About the technical stuff: Should the empty file be called just content without a file ending or content.php? / Yes, you’re right: “Write a comment” (re-translated from German “Schreibe einen Kommentar”) is the text just above the comment form.

Dear Ben,

thank you for your fast answer. I successfully deleted the tagline. However, I can’t seem to solve this:

* I can’t find the “ct_ignite_customize_comments” function. There’s a “link” to it in the comments.php but no function in the functions.php. I guess I’m searching in the wrong files? Also I have no search results for the code I want to delete there. I also searched the ignite support pages but didn’t see something similar there, too.
* As for changing the “Published” text (s. old thread): My content.php file doesn’t have a line 89 (it just has 45) and line 16 is just “/article”.
* Also, I want again to change the “Write a comment” and while it seems that I did this by myself 2 years ago I fail to find the file and line to do this again.

Thank you for your help!