October 20, 2015 at 18:07 #8880
I’ve just done a fresh install of DFFS (18 October 2015 version)
DFFS Frontend 4.358
DFFS backend 4.357
spjs-utility version: 1.253
vLookup Frontent 2.253
There are two things I’ve come across which seem a bit strange.
1) On editform on a document library I don’t see the option to do anything with the ID field – I wanted to hide it, but there is no entry in the dropdowns on the rules tab, and “ID” doesn’t appear in the Field Table tab as a valid field.
On dispform, it functions exactly as expected – ID field in field table and in the dropdown menus.
2) DFFS frontend overlay seems to be causing an issue with the form while being edited – white box in front of everything else on the form – see attachment.
Inspection of this area with developer tools shows
<DIV id=dffs_formTableOverlay style="CURSOR: default; HEIGHT: 100%; WIDTH: 100%; POSITION: absolute; Z-INDEX: 9999; BACKGROUND-COLOR: #ffffff"> </DIV>
I’ve not seen this before when setting up DFFS.
October 20, 2015 at 18:28 #8885
I’m also seeing errors in the console (for both dispform and editform – both refer to editform.aspx);
SCRIPT70: Permission denied File: EditForm.aspx, Line: 19, Column: 1
Which is the document.write line after CDATA
October 21, 2015 at 23:04 #8908
Thanks for the feedback. I’ll add the ID as selectable in EditForm – it went missing in one of the previous *fixes*.
The overlay is also a change in one of the lates releases to try to prevent a flash of the unformatted form before DFFS kicks in – I’ll add a fix to the next release, but you can use this code in the overlay CEWP:
The last error you posted is not known to me, and this script is not used in my code.
October 22, 2015 at 19:06 #8914
You’re quite right Alexander, the last error seems to be an issue specific to the site collection I was testing in – as yet unresolved, but nothing at all to do with DFFS.
In production I’m still running a previous version of DFFS so I’ve still got the older code for the overlay (no flicker issues experienced).
You must be logged in to reply to this topic.