This support ticket is created 3 years, 6 months ago. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
Hello and thank you for contacting the Toolset support.
To better assist you with this issue, I'll need to login in order to see the errors, currently, all your pages are behind login wall. Your next reply will be private to let you share credentials safely. ** Make a database backup before sharing credentials. **
Regarding updating the WooCommerce Views plugin, can you try manually and see if it will succeed. Go to your downloads page https://toolset.com/account/downloads/ and download the files, then upload them manually in Plugins->Add New. WordPress will ask you if you want to replace the existing plugin with the downloaded one, confirm and continue.
Because FTP access was not working for me, I installed WP File Manager to rename the debug log file, and activate debugging. The debug log only has one notice that repeats. The one you shared in your first message.
If we change WooCommerce Views settings, we can get the product page working, and other products such as:
- hidden link
- hidden link
I can't really tell what can be causing this issue, but I'll suggest the following:
- Update Toolset WooCommerce Blocks/Views to the latest release. Either automatically or manually.
- Deactivate all other plugins temporarily for testing. I guess that you will need to keep the "UpSolution Core" plugin. To check if it is not caused by another plugin.
If that does not help find the root cause, I'll need to take a copy of your website for local debugging.
Thanks for getting back at me, and good to know. That's why I couldn't find it at first I guess:)
I will update the plugin(s) and let you know how it goes. It's a large website, so creating a copy will take some time, so you know;)
Did you get the parent/child view issue working yesterday with a snippet f.e. like you mentoined?
Did you get the parent/child view issue working yesterday with a snippet f.e. like you mentoined? Do you mean to display the child taxonomy terms?
I run a test on my test site, and I was able to display only the child taxonomy term. For example, for a product that has the following categories:
- Clothes (parent)
-- Men (child)
I was able to display on the "Men" term, without displaying "Clothes", even when Clothes' term is also added to the product. I only used one taxonomy view, to which, we pass the child term ID using the custom code above.
If you prepare a staging site, I'll give it a try.
Thanks. Well the only problem I have is with the shortcode, which isn't rendering correctly. I have a test environment available at utilicht.jellit.nl. You can use the same login credentials as before.
I replied to you about the child categories on the other ticket. Check my reply there.
Regarding the blank page issue, it seems that the issue is coming from the "product_table" shortcode, probably, because the acf shortcode does not return the expected data.
If we deactivate this shortcode by one of the following techniques, the page loads without issues:
- Either by deactivating the plugin.
- Or by changing the shortcode. For example, adding underscore before it to make it unavailable:
But, the shortcode works for other products, so, I guess, there is an edge case when the shortcode crashes without triggering issues or without completing with and exit(0). Can you check with the product table plugin's support for additional assistance?
Thanks. Seems like the include="[wpv-post-id]" is causing the issue, but only if the are a lot of rows (product variations) to display. If i change the include to a random number the page shows up, so I guess things get stuck wit a lot of rows to process..
