I am trying to: Create a WordPress archive for a custom post type and taxonomy.
Link to a page where the issue can be seen: hidden link or hidden link
I expected to see: An archive page with content and custom filtering and search based on my custom post type and fields.
Instead, I got: Nothing. I have tried multiple times to add custom search fields but the loading icon just spins round and round and never loads the field. Also, no content is loading in the loop. The archive itself never allows me to press the "Update" button after it has been published. Even the name of the archive is strange. It gets named "Classes, Series-preview-1614028940". I have been meticulous in my development, using a local testing site and mirroring my movements. On the local site, everything pulls up as it should. But, in my production, it is the complete opposite. The screenshot attached shows the strange name. The second screenshot shows the edit screen when I try to add a text field search. It never goes beyond the spinning icon. I have contacted the hosting company. Perhaps it's the block editor? Would I be able to bypass the block editor and manually code this archive? Or, perhaps there is a companion filtering plugin one might recommend? Thank you for your help.
A quick update from the hosting company. They noticed a lot of errors with the WordPress archive builder (see screenshot). Also, here is their official recommendation...
If nothing of this works, I'd recommend a conflict plugin test to isolate the culprit. #
The following flowchart can help help you with the process: hidden link
Also, it might worth contact ToolKit support to check that everything is fine at their side."
Hello. Thank you for contacting the Toolset support.
There is something wrong with your server setup as even I try to setup a new WordPress archive its not working and it takes too long time to load the archive in backend as well.
- Can you please try on another server?
- I also tested with my test site and the taxonomy archive works just fine:
=> hidden link
Thank you for taking to time to look into the issue.
Are you recommending that I move my site to a new hosting company? This would prove to be extremely problematic. In other words, not something I can do easily and may require me to abandon Toolset completely.
Perhaps there are more specific steps I might be able to take with my hosting company to help get this resolved?
When I try to create a new archive - I see the following error on browser's console:
Failed to load resource: the server responded with a status of 403 () /wp-json/toolset-views/v1/views/906?_locale=user:1
It seems your server is blocking the ajax calls made. Can you please first check your server's error logs and see what URLs are blocked when you try to create a new archive and then contact your server admin to unblock such ajax requests.
If that is not possible then you should switch to classic mode to create the archive. Does this makes sense?
Thank you again for taking the time with this. I have contacted my hosting company and relayed your message. They say they are not blocking any AJAX calls.
However, they had me turn off the "Web Application Firewall" setting and it worked! Once the WAF was off I was able to see the create and save my template and view it on the front end.
This is great, but what would make it awesome would be if there was a way to keep WAF on. There is a URL Allowlist that accepts relative URLs. Keep in mind it does not allow for queries like "?_locale=user:1" in the URL.
I tried "/wp-json/toolset-views/v1/views/906" but that did not work. Their technician suggested that you might be able to guide me on the exact URL(s) that needs to be whitelisted relative to the root domain. Is this something you can provide? I recognize the view ID is in the URL. I can change that so long as I know the relative path.
By the way, when you say "switch to classic mode to create the archive", how exactly would I do that? I do not see an option for switching to classic mode anywhere in the Toolset Archive block editor. But, I could be missing something. Could you kindly point me in the right direction?
Again, thank you so much for your time Minesh. I really appreciate it!
This is great, but what would make it awesome would be if there was a way to keep WAF on. There is a URL Allowlist that accepts relative URLs. Keep in mind it does not allow for queries like "?_locale=user:1" in the URL.
I tried "/wp-json/toolset-views/v1/views/906" but that did not work. Their technician suggested that you might be able to guide me on the exact URL(s) that needs to be whitelisted relative to the root domain. Is this something you can provide? I recognize the view ID is in the URL. I can change that so long as I know the relative path.
===>
I checked with our Dev and they asked me that we will require to know what URLs are blocked when you activate the "Web Application Firewall".
If you can activate the "Web Application Firewall" and ask your hosting what URLs are blocked when "Web Application Firewall" is active they will try to investigate bit deeper.
By the way, when you say "switch to classic mode to create the archive", how exactly would I do that? I do not see an option for switching to classic mode anywhere in the Toolset Archive block editor. But, I could be missing something. Could you kindly point me in the right direction?
==>
If you navigate to:
- Toolset-> Settings => General Tab => "Editing experience" section:
- Enable option "Show both the legacy and Blocks interface and let me choose which to use for each item I build"
The above option will allow you to select what mode you want to edit Content Template and WordPress Archives.
I checked with hosting and they were able to whitelist the IP addresses that Toolset was using and it worked like a charm! Now I can have both the WAF and Toolset.
Problem solved...on to the next 😉
You have been a great help Minesh. I can't thank you enough.
