All of my archive pages are not customized, like Toolset is no longer controlling them. For example, hidden link is just looping through all Members. On the Toolset Dashboard I still see the Members Archive in the list, and when I click on the link it takes me to the same custom Archives page. The first bit of HTML in the Loop Editor box is <h1>Members</h1> but the Archive page does not display a title like this. It's like it's ignoring it. I'm seeing the same thing with other Archive pages.
The only issues I'm seeing are with Toolset pages, and I'll admit I haven't looked at them in a while. I've disabled a few plugins to try to see if there is a conflict, but nothing has been successful. Thanks!
Hi,
Thank you for contacting us and I'd be happy to assist.
To troubleshoot why the archive pages are no longer controlled by Toolset, I'll suggest the following steps:
1. Please make sure that WordPress, active theme, and plugins are all updated to the latest versions.
2. It would be interesting to test this with all non-Toolset plugins disabled and a default theme like Twenty Twenty-One.
If it's fixed, you can start adding the disabled items, one-by-one, to narrow down to a possible conflicting one.
3. In case the issue still persists, I'll need to see how these WordPress archives are set up in the admin area.
Note: Your next reply will be private and please make a complete backup copy, before sharing the access details.
regards,
Waqar
I have all of my plugins up to date. Unfortunately, my site is very large and I only have a production environment. So, troubleshooting is difficult. I wouldn't be able to disable many of the plugins, but I can work on it in off hours.
I am concerned about making changes that make the primary pages behave even worse, so I am trying not to migrate Toolset data to the most recent version. Primary pages provide revenue, and they are all working very well at this point. I'll do some more testing on my end.
NextGEN Gallery is also in use on the archive pages I was working on. They just released an update that fixed my issues on those pages, so it was a plugin conflict. Thanks for your help, this issue no longer exists.
