Hello!
What became changed exactly in 2.7 related to archives? I moved to 2.7 and on the second day noticed that my custom types type archive and taxonomy archives became empty!!!!! Reverted back to prev version - and everything ok. Pls, explain, what changed exactly?
I think you refer to Toolset Access 2.7?
I did not notice changes in how archives are handled, but then, I do not know precisely what settings you used in Toolset > Access Control over single post types or their archives (read permissions)
Can you eventually send me a copy of the site with https://toolset.com/faq/provide-supporters-copy-site/, and let me know where precisely to look for the issue?
Or, if you have precise steps I can follow, I can replicate those and see the problem so to report it.
Thank you!
Hmm, my website is quite big - several thousands of posts + pics. Maybe you just take a look at current access settings for the first glance?
We can try this, I re-activated the private reply again for access details.
Wait, I believe I see something similar to your case.
I simply control the native Posts with Access and set guests to read them.
Then, I visit the Views styled archive (home/blog) for posts and see "no results found"
This even as Admin.
Toolset Access 2.6.2 does not have this issue.
I reported it to the developers. If you want to be sure it's the same issue, the archive should be visible again as soon in Toolset > Access the post type is NOT under Access control.
Let me know if you agree with the description.
Yeah, sounds similar. I couldn't see it as admin either. But I didn't try to switch off control of Access plugin because of security reasons.
I have replicated the bug I mentioned above and reported, and despite your situation sounding similar, I am not sure.
On this archive hidden link I see the content.
Also on other archives like hidden link
Since you have Access 2.6.2 I cannot verify the issue on the site.
If you can you would have to update Access, remove control over those post types, and check if you can see the content.
However, if security is a concern please wait for a fix and test only then.
This is fixed in the jsut released version 2.7.1
Please can you confirm?
My issue is resolved now. Thank you!
The erratum has a patch now. The fix in the core will come next week presumably. For now, you can apply the patch shared in the erratum.