Turn on SSI includes in SP pages in Edit mode

Is it possible to turn on SSI includes in SP Pages in Edit mode?

Your comments are appreciated

TeamSite 7.3.1
Linux

Find more posts tagged with

Comments

Currently we have TeamSite 6.7.2SP2 in the Production env and in the process of migrating to 7.3.1.

In 6.7.2 SP2 we are using below script to preview html includes in the SitePublisher pages - which works perfectly in Edit and Preview modes


$(document).ready(function(){
 if($("#nav li").length == 0){ 
  try{   
    $(".include").each(function(i){    
    var incParent = $(this).attr('id');
    incParent = "#" + incParent;
    var incStr = $(this).attr('id') + "_func";
    var incFun = eval(incStr);
    var url = incFun('/include_path');

    if (url.match('#')){
     url = url.replace(/#/g,'/');
     url = url.replace(/\*/g,'.');
    }

    $.get(url, function(data){
     if (data.indexOf('      var so = new SelectObj();
      var so_props = '      if(so.hasMultiple==="Yes"){
       so_props += 'multiple="multiple" size="5"';
      }
      so_props += '>'+data+'';
      $(incParent)[0].outerHTML = so_props;
     }
     else{ 
      $(incParent).html(data);
     }
    });
   });
  }
  catch(e){}
 }
});

In 7.3.1 in the edit mode this script enters into try condition and ends without loading any of the includes.....script running in the edit mode is not able to identify any span and div tags.........

Please help me understand if component fragments are not part of the edit page (Component fragments are not injected into edit page dom)

Rick Poulin

Please help me understand if component fragments are not part of the edit page (Component fragments are not injected into edit page dom)

They're part of the page, but they're loaded asynchronously through AJAX. Your document.ready() obviously executes before that, which is why it doesn't find anything. Your approach is fundamentally flawed in that even if you delay your call, updating component datums causes only that component to refresh, not the whole page. If that were the case, your includes would not be loaded again.

If your only requirement is to do server side inclusion of HTML fragments, you should actually keep it on the server side. Use a Java external to retrieve the content and inject it at the right place in your component XSL. This has the side effect of solving your edit mode problem.

Witty

Thanks a lot for your response.....But I'm trying to understand how it is working in 6.7.2 but not in 7.3.1

Rick Poulin

Thanks a lot for your response.....But I'm trying to understand how it is working in 6.7.2 but not in 7.3.1

Well your Javascript is operating on a DOM that doesn't look anything like the final page, and is subject to change without notice. As such, if someone managed to get this working in edit mode previously, it's an unsupported hack at best. If it doesn't work now, it's probably because iwov made some changes to their edit mode DOM and/or edit mode processing. My suggestion is trying to steer you into an implementation that relies purely on supported APIs, which is thus upgrade safe.

The upgrade safe version of your approach is to tell your users that the includes will only load in page preview. A general rule of thumb is to assume that your edit mode will render the same way as a user accessing your runtime with javascript disabled, and that's just the way the platform works (for good reasons).