Archived topic
legacy header issue when adding block element
12 replies · Started by racheljohn on July 14, 2021
I have a legacy header that when I switch off and use a block element instead it is like its not really shutting off. This was a header that was created by a previous developer for a custom post archive page (Press). I checked the archive-press.php and removed the hard coded header duplicate so now it just says get_header but when I switch off the legacy header and switch on the block element its still showing 2 headers like that legacy one is still on. If I just leave the legacy one on the archive page only shows one header. But I really want to be able to utilize the modern block page hero instead of the legacy header.
I don't know if it helps figure out what the issue is or not but I had similar issues if I try and switch off the couple of legacy hooks to the hook elements it does the same sorta thing (theses are not on the custom post archive) its like its not really shutting them off properly.
Hi there,
Not sure if I fully understand. - your site is showing error 404 so I can't see.
Do both headers disappear when you disable GP Premium?
Have you tried contacting your previous developer and see if he/she can explain how it was added in the first place?
The link should be working again, sorry about that. Yes both headers disappear when I disable the GP Premium.
I have been trying to contact the previous developer but so far have been unsuccessful the info she provided in the child theme, like the website is not even active anymore(502 bad gateway error) unfortunately.
The link to your page is still not working for me.
Can you double check?
double checked and tested the link it is working now.
Hi there,
This is what I see:
https://www.screencast.com/t/FQ4ItmNvIRi
It doesn't seem like having double headers on the home page, is there any specific page I should be looking at?
Let me know :)
its on the Press page so its a custom post Archive page only
I see. Any chance you can provide admin access?
Please use the private info field.
yes it is to my locally developed site so it will probably be pretty slow.
I deleted the legacy page headers in the trash and the issue is resolved.
Likely some sort of caching issue.
Great! Thank you for all the help.
No problem :)
