This thread is resolved. Here is a description of the problem and solution.
Problem:
The issue here is that the customer's custom fields were not showing up.
Solution:
Checking this issue the field group was appearing on the Post on the backend but the field was not. It seems that it was being hidden and was the fault of the Jupiter theme. It was recommended that the customer contact the theme's support.
This support ticket is created 6 years, 5 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.
Hi. I prepared a package with "ALL IN ONE IMPORT" because the duplicator plugin does not allow me to create the archives.
If you have problems with ALL IN ONE IMPORT, let me know because I have the paid version with no limitations and I can install it on your test server so it can import everything.
I was able to get the site on my local server and the issue was still there. What I noticed is that the radio fields are there but they are declared as a hidden input type.
Could you let me know if this issue started to occur after the latest update? Or give me an idea of when this started happening.
Correct. This is what i explained. They are there but they are declared as wrong type of <input >
I have no idea, it's a client's website and I never used radio fields before on this website, so I can't tell you if it's a thing that always happened or a thing that just started in the last few updates.
It's the only website i created which also uses maps and views and so on, but i don't think that is the problem.
Do you have the possibility to replicate it on even a fresh install or no?
Because I am quite sure I don't have conflicting plugins but.. :/ who knows
