There’s code somewhere sending a Location: header to /thenotebar/blog/composition_year/2005/ when the same is requested. Check your .htaccess file for related 302 redirects. There could be JS code on the page sending a Location command, but it’s hard to check when you can’t load the page. There could be PHP code sending the Location: header with the other WP headers. Since you disabled most plugins and core code wouldn’t do this, it’s either wpml or your theme if not .htaccess.
Try switching your theme to one of the twenty* default themes. If no joy, rename your .htaccess and make a new one with only the WP rewrite rule set and nothing else. With this .htaccess and a twenty* theme with no plugins but wpml active, if you still get too many redirects, the only possible source is wpml or hacked core code.
Hi
Thanks for your answer
I tried everything you mentioned
I have now a standard .htacess, the taxonomy concerned is a custom one, but I have also others I created the same way as this one, and they work all fine… The taxonomy pages, they all contain the same code, as they are adapted duplicates from the theme i’m using, so I completely control what it contains
i also completely re-uploaded the wp-adlin and the wp-includes to that if there was some core hacked code it would be erased
the problem is still the same
I was thinking about deleting this taxonomy and creating a new one to replace this one
What do you think ?
Puzzling indeed. Try visiting the permalinks settings screen. Doing so regenerates the rewrite rules. Maybe that will flush out the circular redirect problem.
If that doesn’t help, I suppose you can try replacing the taxonomy if it’s not too much trouble. I’m not sure it would help, but I’m out of ideas. Going “all in” on the permalinks screen 🙂
Hi thanks again for your help
I tried the permalink thing, but no result….
actually, I had also problems with custom fields, and got aware that my site had probably been hacked…
having, not a lot of content, I decided to restart from scratch, and created a new DB, reinstalled wordpress and so…
Now I created a few custom taxonomies for Easy Digital Download, just the way I did on the previous website…
And now I still have problem with the term archive page…
I created a taxonomy-composer.php file in my child theme
and wordpress doen’t read it and point directly at taxonomy.php
here is the link
https://kompozitor.fr/thenotebar/composer/test/
I did exactly the same thing, duplicted the archive page from the theme and copied it in my child theme after changing the taxonomy names…
was working perfectly on the previous install, and here nothing
I don’t understand
Check the file permissions for taxonomy-composer.php. The user PHP runs as must be able to read the file or it will be skipped over and taxonomy.php will be used. Themes and plugins can alter what template is loaded, overriding the normal hierarchy. Try with all plugins deactivated and making your child’s parent be one of the twenty* default themes. I’m assuming the taxonomy registration is part of your child theme. Relocate there if not.
Be sure the first term passed to register_taxonomy() is really “composer”, which is what is used to construct the template name, even if the rewrite tag and labels are something else. It’s conceivable that this term is not “composer” even though the rewrite tag and labels all indicate it should be “composer”.
Indeed when I copy the taxonomy file and switch to twenty19 it reads the file OK
I guess there is something in my theme…
What should be the chmod permissions on the folders and file, just to be sure there is nothing there ?
Where can I check the register_taxonomy thing ?
Sorry for all these basic questions but it’s the first time I go that deep on the technical aspects with wp
Ok
I found
I use WPML
If you dont declare the new taxonomy as translatable then the wpml navigation engine skips the taxonomy templates
Grrrr, so much mess
anyway, thaks a lot for your help, it’s been very supportive.
May I annoy you ,more if I encounter new problems ?
File permissions on folders is usually 755 and on files 644, but variations are possible for certain files or even certain servers.
You’re welcome. You’re always welcome to open a new topic in these forums. Seeking out individual volunteers is frowned upon. If I see your user name anywhere here, I’ll try to answer if I’m able.
