Home › Toolset Professional Support › [Resolved] Various Toolset issues and errors in console
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.
Sun | Mon | Tue | Wed | Thu | Fri | Sat |
---|---|---|---|---|---|---|
- | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | 7:00 – 14:00 | - |
- | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | 15:00 – 16:00 | - |
Supporter timezone: Europe/London (GMT+00:00)
Tagged: Access plugin, Types plugin, Views plugin
This topic contains 16 replies, has 4 voices.
Last updated by marcB-6 5 years, 7 months ago.
Assisted by: Nigel.
Hi guys,
in a website i've build i run into various issues all concerning conditionality. I've listed them below.
1. Fieldgroups are showing up in wrong post type.
I have a post type called 'chapter'. In this post type two field groups show up that should not show up there. It is the field group 'course detail page' (part of the post type 'course') and it is the field group 'evaluation' (part of the post type 'lesson'). Good to know; both field groups are conditionally shown.
See screenshot for additional info.
2. Conditional required fields throw an error on saving the post.
In a chapter we have multiple fields that are conditional and required. They are visible based on options in other fields. However, when saving a chapter we get errors from all required fields, even if they are not visible.
See screenshot for additional info.
3. Errors in console.
I get errors in console that seem toolset related. See screenshot.
Both problems seem to be related to conditionality. I experienced similar problems on an other website (see open thread)
I deactivated all plugins. I switched themes. I have a backup of the site created by Duplicator that i can easily share with you.
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
Hi Marc
I thought most of these issues in Types had been fixed, but seemingly not.
Yes, could I get the duplicate of your site? I'll install locally, it will be easier for me to do some testing there.
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
Hi Marc
That Duplicator package failed to install.
Can you create a new one being sure to use the file filters to exclude what's not required, e.g. uploads directory, cache, media files etc..?
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
Sorry Marc, I couldn't install that package either.
Can I get credentials and go in and take a copy with All in One WP Migration instead?
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
Hi Marc
I installed the copy of your site locally and I can see issue #1 (only when adding new posts, not when editing existing ones).
We have similar reports but they are not the same. In any case, I've escalated that so that it can be debugged further.
I couldn't reproduce #2. It is not obvious there *are* any required fields. I created a new Chapter post, gave it a title, didn't set any custom fields, and saved the post without problems. No required fields messages.
Where can I find #3? What page do you see those errors on?
m
Hi Nigel,
Thanks for your work.
#2. The reason that you don't see the errors is that i changed all fields not te be required (since client could not proceed in filling the site). You could for example make one of the fields given in the above screenshot (eg exercise title/exercise intro) required in your installation to see the problem.
#3. You get the errors for example when you create a new chapter.
Hope to hear from you soon!
Marc
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
OK, thanks, I've confirmed and added details to the same internal ticket.
Ok, Nigel. Thanks a lot for your help, really appreciate that.
Now, how will the next steps look like? I have some open tickets atm that are escelated to the devs months ago and still not solved. This problem is quite urgent for my client. Could you give me a timeframe on when you expect an answer and/or a solution? And if that is not possible maybe a direction how we can fix this by ourselves.
Thanks again!
Marc
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
I'll ask the developers to prioritise this. It needs some initial debugging work to identify the problem, then a fix. We had a similar problem recently which has a patch available, but the patch does not work on my copy of your site so it will require a deeper look.
Ok, clear, and thanks for prioritizing it.
Please keep me updated!
Marc
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
Hi Marc
My colleague found that removing the DetailPage? and Has evaluation field conditions, saving the post field groups, then adding them back again and re-saving managed to fix the issue on his local copy of your site.
Could you try the same?
So the solution here should be:
1. remove the conditions to the checkbox from both groups
2. save both groups
3. re-add the condition to both groups
4. save both groups
Let me know if that works.
Hi Nigel,
It worked! Even better; error #2 is solved as well. So thanks a lot!
The only thing are the errors in the console.
Should i worry about those?
Marc
Hi Marc,
Thanks for the update and glad that the first two issues are solved now.
Sorry about the delay and Nigel is on vacation for a few days and will be back tomorrow.
He'll be in better position to guide you around the troubleshooting on issue #3 (errors in the browser's console).
Thank you for your patience.
regards,
Waqar
Languages: English (English ) Spanish (Español )
Timezone: Europe/London (GMT+00:00)
Hi Marc
We have a hotfix for Forms (as well as Types and Views) due today and I expect that to resolve the JS error.
Can you check again adding a Chapter post after applying the updates when available to see if you still see the JS error, and let me know either way.