Docs

[Eric]

Hey I found yet another issue (which occured either from the automatic wordpress update or from when you guys were trying to fix some of my font issues).

Originally I had added some css and some code to the functions.php file, which drops the navigational buttons to the bottom, added some text above it, and I tweaked the size/positioning as well. Now I checked my css and all my customizations appear to still be there, and I also checked my functions php, and the code is still there as well (although I noticed that it had been changed slightly, which I then fixed). However despite those changes, my navigational buttons/arrows are still not appearing on the blog posts pages.

Any idea as to why this happened? And how can I get them to reappear? I once again disabled cloudflare until I can get to the bottom of this, so there’s no way that was causing the issue.

Please advise. Thanks.

[Eric]

This reply has been marked as private.

[Rupok]

Hi there,

Thanks for writing in! Regretfully, at this time I am not entirely certain what it is you would like to accomplish based on the information given in your post. If you wouldn’t mind providing us with a little more clarification on what it is you’re wanting to do (a link to a similar example site would be very helpful, or perhaps some screenshots), we’ll be happy to provide you with a response once we have a better understanding of the situation.

[Eric]

This reply has been marked as private.

[Christopher]

Hi Eric,

I checked previous topic and found related one. Please check this thread : https://community.theme.co/forums/topic/customizing-my-previousnext-buttons-in-blog-posts/

Hope it helps.

[Eric]

Hey thanks for the reminder. As it turns out my _content.php file was somehow deleted from the child theme as well, and by following the steps I was able to resolve the issue. However just to make sure this doesn’t happen again, I have a few follow-up questions.

First off, how is it that the three files (located in WP Content > Themes > X Child > framework > views > ethos) could have gotten deleted? I definitely didn’t delete them myself, and aside from you guys accessing my FTP to help me with some issues, nobody else had access to it. Is it possible one of you guys accidentally deleted it while working within my FTP? The only other thing that could have done it was the automatic wordpress update but that shouldn’t have affected any of my child theme files.

Secondly, once I re-added my _content.php file, I noticed that the navigational arrows still weren’t appearing, which is when I realized that the code within the content.php file (located in WP Content > Themes > X > framework > views > ethos) was causing the issue. The issue is resolved now but I’m just a bit confused because isn’t the child theme’s _content.php file (located in WP Content > Themes > X Child > framework > views > ethos) supposed to override the other file? I was under the impression that none of the files within the X folder really matter since I’m using the child theme. One thing that I noticed is that the content.php file in the regular x theme folder is called ‘content.php’ whereas the content.php file in the child theme folder is called ‘_content.php’, so do you think that could be why my ‘content.php’ file was affected? What I’m thinking (and I could be wrong), is that because the file names are different, for this particular file I wasn’t running it through the child theme, which would explain why the wordpress update affected my content.php’s code. So if that’s the case, should I rename the ‘_content.php’ file within the child theme to ‘content.php’, and in doing so would this file now be running through the child theme?

I really don’t want to have these issues happen again so if you could please explain how my files could have gotten deleted and also how the x/x-child folder dynamic works, that would be greatly appreciated.

I really just want to make sure that I understand how it works so that I could prevent these issues going forward.

Thanks!

[Nico]

Hi There,

1. Not sure why it is deleted but I believe before we delete something or to transfer something from you code, we usually ask permission to the owner.

2. Little confuse of query. As far as I know, your child theme ethos _content will overwrite ethos _content main theme. content.php in the global is different from the _content.php for stacks so to edit content for specific stack edit _content.php instead of editing the content.php.

3. Child theme installation guide – https://community.theme.co/kb/how-to-setup-child-themes/

4. Customization guide – https://community.theme.co/kb/customization-best-practices/

Feel free to ask us again.

Thanks.

[Eric]

This reply has been marked as private.

[Rad]

Hi there,

Maybe there is some confusion, that’s because _content.php is only available from /x/framework/views/global/ folder. While content.php is under /x/framework/views/ethos/ folder, and now, it creates an impression that _content.php is deleted since it’s not available from /x-child/framework/views/ethos/, maybe you’re just looking to different folder. And from your provided code, it clearly says // VIEWS/ETHOS/CONTENT.PHP and it’s not // VIEWS/GLOBAL/_CONTENT.PHP.

Thanks!

[Eric]

Hi thanks for the reply. So does that mean that it’s set up properly, or is there something that I should change?

My original recommendation was to ‘copy _content.php from framework/views/ethos and put it in the same path inside child theme’ (while rewriting the code). Then I was told to ‘update the code inside content.php file’ (presumably in the /x/framework/views/ethos folder). There was never any mention of the ‘_content.php’ file within the /x/framework/views/global/ folder.

Also just keep in mind that there is a ‘_content.php’ file within the /x-child/framework/views/ethos/ folder, but like I said, it’s pretty much a duplicate of the content.php file (with the slight alteration that was mentioned above).

If there’s any adjustments that need to be made please let me know, and if there are changes, if you can try to be as detailed as possible.

Thanks!

[Paul R]

Hi,

Can you provide us your ftp login in private reply so we can check.

Thanks

[Eric]

This reply has been marked as private.

[Rad]

Hi there,

Yes, I checked the thread and it was a type. It’s actually referring to content.php and not _content.php. I’m just not really sure how did you copy a non-existing file, so I thought you’re referring to /x/framework/views/global/_content.php.

I checked your files and it still _content.php, please rename it to content.php or actually just remove it since it’s no use. You can see from the code that it says // VIEWS/ETHOS/CONTENT.PHP and not // VIEWS/ETHOS/_CONTENT.PHP. Please follow the correct file name.

Maybe you’re just confused to where you added your custom code and you thought it’s deleted. You actually placed your custom code to parent’s /x/framework/views/ethos/content.php and you’re looking on your child theme. Hence, when you changed your child theme’s content.php to _content.php, the navigation works and it’s because the parent’s content.php becomes active and it’s where your custom code is. Try deleting _content.php and it will still work because you placed your custom code to parent’s theme.

Thanks!

[Eric]

Hi so if I rename my ‘_content.php’ file to ‘content.php’ within the /x-child/framework/views/ethos/ folder, would that mean that the child theme will be active? I don’t want to have future wordpress updates affecting these codes so if it can be avoided I’d rather not have the parent’s content.php being active. So what will I have to do to have this code actively running through the child theme?

As you said in your comment, in the code it says ‘// VIEWS/ETHOS/CONTENT.PHP’, so will that code only work in the parent theme? And if that’s the case, could it be altered to work in the child theme instead?

Like I said, I want to make sure that this code will not be affected by future updates, so if you could help me make the child theme active for it then that would be greatly appreciated. And if you provide directions please be clear, just to avoid more confusion.

Thanks again!

[Rad]

Hi there,

Yes, it will be but instead of renaming. Just delete it and copy /x/framework/views/ethos/content.php to your child theme, you have your customization there and it will be there permanently in your child theme.

It will work on a child theme, that line code is just a note indicating which file.

Thanks!.

[Author]

Posts