No option to hide "ID" on ediform.aspx & problems with overlay (18 October 2015)

Forums Classic DFFS No option to hide "ID" on ediform.aspx & problems with overlay (18 October 2015)

Viewing 3 reply threads
  • Author
    Posts
    • #8880
      AdamP
      Participant

      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
      jQuery 1.11.3
      vLookup Frontent 2.253
      SP2010 Standard

      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">&nbsp;</DIV>

      I’ve not seen this before when setting up DFFS.

    • #8885
      AdamP
      Participant

      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

      
      
      // <![CDATA[
      document.write('<script type="text/javascript" src="/_layouts/1033/init.js?rev=BjQJs0OCQh3Zfydsdw2MYw%3D%3D"></' + 'script>');
    • #8908
      Alexander Bautz
      Keymaster

      Hi,
      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:

      <div id="dffs_formTableOverlay" style="width:100%;height:100%;background-color:#ffffff;position:absolute;z-index:9999;cursor:default;"> </div>
      
      <script type="text/javascript">
      if(document.forms[MSOWebPartPageFormName].MSOLayout_InDesignMode.value !== "1"){
      	(function(){
      		var div = document.createElement('div'), o = document.getElementById("dffs_formTableOverlay");
      		div.id = "dffs_loadingOverlay";
      		div.style.cssText = "padding-top:100px;text-align:center;width:100%;height:100%;background-color:#F5F5F5;position:absolute;top:0px;z-index:9999;cursor:default;background-image:url(data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAYAAAAGCAYAAADgzO9IAAAALElEQVQIW2NkwALOnDnznxFdHCRoYmLCiCIBEwQphksgC8Il0AXBEtgEQRIAsDsXagWOqrQAAAAASUVORK5CYII=);";
      		// Change this to have your own overlay message
      		div.innerHTML = "DFFS is loading...";
      		document.body.insertBefore(div, document.body.firstChild);
      		if(o !== null){
      			o.parentElement.removeChild(o);
      		}
      		setTimeout(function(){
      			var oDiv = document.getElementById("dffs_loadingOverlay");
      			if(oDiv !== null){
      				oDiv.innerHTML = "<span style='font-size:20px'>This took forever!<span style='font-size:12px'><br><br>Click to close this overlay.</span></span>";
      				oDiv.onclick = function(){
      		   			this.parentNode.removeChild(this);
      				};
      			}
      		},10000);
      	})();
      }else{
      	var o = document.getElementById("dffs_formTableOverlay");
      	if(o !== null){
      		o.parentElement.removeChild(o);
      	}
      }
      </script>

      The last error you posted is not known to me, and this script is not used in my code.

      Alexander

    • #8914
      AdamP
      Participant

      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).

      Adam

Viewing 3 reply threads
  • You must be logged in to reply to this topic.