-
Posts
-
Hello,
Something in the header.php is causing a duplication on our recipe pages. If you scroll down to the bottom, you will see where the recipe is duplicated where the footer should be. We are using a page as footer.
Details in private
Thank you
Hi finchkelsey,
Can you give us temporary admin access as well? so we can inspect the backend further.
Just post the credentials in private content.Best regards,
NikkoHi,
Thanks for your patience, via FTP I see that you have a lot of files added to your child theme,
are all of these customized?
What version were these from?
The only way that I can see in finding the error is to create a staging copy of the site and then remove your customized files and add them back one at a time to find which one is causing the error.
Does the error occur if you use the regular footer instead of the footer page?Best regards,
MikeHey Mike,
I’m not sure on all of them, we have a few contributors and some optimizations. I am not sure which files these use, sorry.When I toggle between the child header and the parent header the problem switches as well. So I assume the problem is there. Could you please look at the two header files for me.
If I choose page for footer on either option the conflict occurs, it is not present when widgets are used.
Thank you
Hi,
When I check your child theme I see that you had an old header.php but no footer.php these to files went together so I would expect an error using the old header.php and a new footer.php. But your header.php is disabled right now and you are seeing the error so it doesn’t point to that as the error.
I see you are using Advanced Custom Fields, is this what is adding the recipes?
I mean that your recipe post type only shows shortcodes so are these shortcodes injected into a custom post loop to display?
If so this might be added to page as a footer because the code is looking for a div like “content” or such.
This would explain why when you use no page as a footer and just the normal footer with widgets the error doesn’t occur.Best regards,
MikeThank you, this is helpful.
The recipes are inserted using the pro plugin Cooked, not ACF.
I have fixed the duplication of recipes by replacing files in the child theme, could you please guide me as to what is causing the footer to be ‘missing’ now on all pages.
I am learning, thank you for you help.
Hi,
As I understand your last two posts, you have solved the duplicate recipe issue by replacing some of your child theme files, but now your footer doesn’t show?
So is that the page as a footer, or the regular footer or both?
which files did you replace?Best regards,
MikeHi Mike,
We are using a page for footer.
The issue does not exist when I select widgets.I cannot determine anything in the child theme header that requires it to be active so I have turned it off.
When the site uses the updated parent theme header we get the duplication of recipe in the footer on recipe pages only. The footer displays properly on all other pages.
I have placed the section of code below from the header.php in the enfold theme that causes the duplication.
Any help you could give me to understand what file I may need to edit or if any of this header code can be edited would be greatly appreciated.
Thank you
Hi,
So the footer error only occurs on the pages that the Cooked plugin is used?
Please check if the footer error occurs when the parent theme is activated instead of the child theme.Best regards,
MikeHi,
Ok, this points to one of your customized child theme files as the cause, but you have so many customized child theme files that I recommend creating a staging copy of the site and then remove your customized files from the child theme and add them back one at a time to find which one is causing the error.Best regards,
MikeHi Mike,
We have paid our developer a good amount of funds to determine what I already had. The issue is in the theme somewhere, please actually take a look this time. Please see his notes below in the private section.Hi,
It doesn’t look like your developer tried my suggestion of removing your customized files from the child theme and adding them back one at a time to find which one is causing the error.
I have tried to suggest this earlier because your child theme is using over 40+ customized files, including files from the templatebuilder, and the includes and woocommerce directory.
Any of these files could be causing the error.
When your developer switched to the default WP theme (like twenty-twenty) he was disabling your child theme and the parent theme, which is not isolating the issue or testing which of your customized child theme files are causing the issue.
Please recall earlier when you tested disabling the child theme and only using the parent theme the issue didn’t occur. So we already know that it is in your child theme, perhaps you didn’t point this out to your developer or perhaps he didn’t understand.
Please ask him to try this.Best regards,
Mike
- You must be logged in to reply to this topic.