I have quite long CRED post forms, created with visual editor and containing lots of conditional display (types conditions not hiding labels so I had to wrap fields in CRED conditional groups), that I actually need to duplicate and will also, later on, need to export and import in another Toolset website.
I just tried the duplicate functionality but the visual editor fields are lost even if not changing the post type which makes it useless for me in this particular case.
I also tried to switch to expert mode before duplicating the forms and back to visual editor after, this way the fields are kept but the conditional groups are lost on both forms except for the first one, which is a little better but still not what I need.
As for the export / import functionalities, it keeps the fields but in expert mode and I loose them if I switch back to visual editor, which means I will have to rebuild the forms entirely when I will need to migrate them to the other website.
Is there a way to duplicate, export and import visual editor forms without loosing anything ?
Thanks in advance for your help and have a nice day.
- Add a New module by clicking on "Add New" button and give your module name
- Then, drag the desired forms you want to the module you created from section "Toolset post forms" or "Toolset user forms"
- Save the module and export the module
- Then, to your desired site to go (make sure module manger plugin is installed and activated) :
=> Toolset => Export / Import => Modules
=> Import the module you exported
=> Check if you able to successfully import/export forms.
Sorry for the late reply, I was away from my office.
Unfortunately I won't have the time to test your solution before next week and thus can't tell you if it will fix my issue but there are a few questions I really would appreciate your feedback on meanwhile :
- Is it considered normal behavior to loose the fields when duplicating forms ?
- The module you mention is part of legacy plugins, how long will it still work with new versions of Toolset ?
- Can I use this system to replace the duplicate function (export and import on the same website) ?
Thanks in advance for your help and have a nice weekend.
As Minesh is currently away today, I will be covering his queue until he returns. - Is it considered normal behavior to loose the fields when duplicating forms ?
No it is not, when you've duplicated the forms using the method Minesh described, you will get an exact copy of your form.
- The module you mention is part of legacy plugins, how long will it still work with new versions of Toolset ?
At this time we don't have any information when this will stop working for Toolst. I know for views created in the gutenburg editor you won't be able to export those views but for views created in the classic editor, those should export fine.
- Can I use this system to replace the duplicate function (export and import on the same website) ?
At this time there is a clone button on your forms list page. If you go to Toolset -> Post Forms and hover over any of your form, you should see a clone button. This will allow you to duplicate your form on the same website.
Well, I did not really find anything working correctly for me :
- I tried to move the form to another website using the "Toolset Module Manager" but the form disappear from the module during the import process
- The clone button works perfectly with simple forms but, if I use it on complex forms built with visual editor, I loose the fields as the visual editor run a reset on the opening of the form clone.
- Normal export / import of the form works correctly but the imported form is in expert mode and, if I switch to visual mode, I loose part of the fields / settings.
There is no workaround to offer to your as of now for such complex forms. I tested with basic forms and it works. You will have to raise a feature request to support complex form import/export that is having conditional displays.
Well I do not really get why Toolset provide the functionalities to build complex forms with conditional display but not cloning and export / import functionalities complex enough to deal with them.
Can we hope that will be fixed in some way in a futur version ?
As a supporter, its not our role to decide what feature should be added in future release or what features are approved. We can just guide you with next steps.
There is no ETA on it, our product manager will review the feature request and they will decided. We get thousands of feature request and in reality not all feature request is going to make part of Toolset.
