field processing indicator puzzle

field processing indicator puzzle

LimpEmuLimpEmu Posts: 16Questions: 6Answers: 0

I am wondering whether there might be a conflict between having bootstrap loaded and using the default display controller (lightbox). The page was previously developed without bootstrap styles, works without problems without bootstrap, and I do not want to change the current setup as lightbox is fine and looks good.

The problem I am running into is that for some strange reason, the field processing indicator for one of the fields is active when a record is opened in editor. The field, that the field processing indicator is active for, is the one field with a dependency.

I was able to turn the field processing indicator off (see below), but I am wondering why I am encountering this problem.

Mainly I want to make sure that there is no bigger problem that I should be aware of. Is there a list of known issues relating to loading bootstrap and using the lightbox display controller?

Thank you for your kind feedback,

editor.dependent( 'resolve', function ( val,data ) {
   if (data.row.resolve == "Y") return {
        messages: {'resolve':'<span class="spit">'+data.row.resolvestatus+'</span>'}
    /* get rid of field processing indicators! */
    var prcssInds=$('.DTE_Processing_Indicator');
    for (var i=1; i<prcssInds.length; i++) {
        if (prcssInds[i].outerHTML.indexOf("field-processing") >= 0) {


  • colincolin Posts: 3,280Questions: 0Answers: 584

    Hi @LimpEmu ,

    I believe that's a bug in Editor 1.8.0, which will be fixed in pending 1.8.1 release due out early next week. If your callback doesn't return anything then it assumes the callback is still processing - you could modify your callback or try again when the release is cut (should be a day or two),



  • allanallan Posts: 48,657Questions: 1Answers: 7,068 Site admin

    Actually, the 1.8.1 release won't change the behaviour, but it will clarify this in the documentation.

    If you don't return anything that Editor assumes you are going to use a callback function to tell it when an async command is complete.

    Add return {}; to your function to resolve the issue.


  • LimpEmuLimpEmu Posts: 16Questions: 6Answers: 0

    Thank you for your responses!

    I see your point Alan, when the condition isn't met I am not returning anything! Added that, and voila, problem fixed!

    I apologize for my late reply, I do not get e-mail notifications and was absorbed in other puzzles ...

Sign In or Register to comment.