Install on Parent & Subsite + Saving doesn’t leave form

[Jonathan Stamper]

Hey Alex – I have DFFS installed on both my subsite and parent site. I have a site collection license and originally installed on one list from the subsite, while the other lists on the subsite I did through the parent. Is this going to cause any issues? Should I move one out and migrate everything over to the specific installation?

Also, I’ve cleared out the very old version of DFFS from the subsite. We removed the “&” on subsite and migrating to the newer Classic DFFS version. On one list, when I save, the save button greys out and I’m not redirected out of the form, unless I hit cancel. However, the updates made do save but the the workflow won’t kick off. I’ve checked all the settings in DFFS (Misc, redirect options, etc.) and I don’t see settings enabled that would cause it. It doesn’t even have enabled rules and none of the fields are required in the OOTB SP list settings.

Let me know if you have any thoughts on the above.

[Alexander Bautz]

Question 1: The only problem with this approach is that you will have to update both /SPJS libraries when updating DFFS. In case you wanted to remove the /SPJS library from the subsite and use the one in the parent, just use the parent DFFS installer to uninstall and reinstall DFFS in the list. There is no need to migrate anything because the config for the forms is stored in the subsite in both cases.

Question 2: Not sure what could cause this issue. Do you see any errors in the developer tools console? (hit F12 > Console before you try to save).

Alexander

[Jonathan Stamper]

Hey Alex, thanks for the information. I ended up uninstalling all from the subsite and reinstalled on the parent. That fixed some of the oddities with updating DFFS and all the lists recognizing the correct one.

The save issue was due to the very old version of DFFS still lingering on the form pages. Also, the new version of DFFS Code CEWP was placed above the form webpart instead of underneath it due to the zone location of the form Webpart showing a large number such as 15. Removing the old and adjusting the webpart location and zones fixed it.

[Alexander Bautz]

Thanks for the feedback – I’m glad you figured it out.

Alexander

[Author]

Posts