Latest update not working on Internet Explorer

@winma, I had the same problem then I downgraded to 3.4.30 and it helped. Thank you!
I hope this will be fixed in new versions.

Same problem here with a client’s registration form. Looks like the JavaScript loader is failing in IE. It works in modern browsers.

Same here. Mozilla, Edge, Chrome work. IE not. Before updating WP to 5.6 the page was constantly loading. After updating to 5.6, the page loads, but the form is not shown.

The following in front-end.js seems to trip IE11:

                parseDate: (datestr, format) => {
                    return moment(datestr, format, true).toDate();
                },
                formatDate: (date, format, locale) => {
                    return moment(date).format(format);
                },

I wouldn’t count on this working in later versions. IE11 can’t use this new code and IE11 isn’t updated anymore.

Have the same bug. Does anybody know how to fix it without downgrading the plugin?

Same here.

@winma @sandk @bwold @ulistopper @whataboutpereira @resonablyreasonable @ostapfilipenko @emielb
Can you update your Ninja Forms plugin to the latest version, 3.5.1 and see if you are still having the issue viewing forms through IE11.
If you continue to have issues, can you contact our official support channel (ninjaforms.com/contact)

Thank you for your reply.

However, the form still doesn’t show up on IE11 with the 3.5.1 version. It now gets stuck on another line of code:

front-end.js, Line 5381

define('controllers/fieldRepeater',[ 'models/fieldRepeaterSetCollection', 'models/fieldCollection' ], function( repeaterSetCollection, fieldCollection ) {
    var controller = Marionette.Object.extend({

        initialize: function () {
            this.listenTo( nfRadio.channel( 'repeater' ), 'init:model', this.initRepeater );
        },

        initRepeater: function ( model ) {
        	if ( 'undefined' == typeof model.collection.options.formModel ) {
        		return false;
        	}

ERROR>>>>      	let fields = new fieldCollection( model.get( 'fields' ), { formModel: model.collection.options.formModel },  );
        	model.set( 'sets', new repeaterSetCollection( [ { fields: fields } ], { templateFields: model.get( 'fields' ), formModel: model.collection.options.formModel, repeaterFieldModel: model } ) );
        },

    });

    return controller;
});

Live example (I will probably rollback in a few days if there is no solution).

• This reply was modified 3 years, 9 months ago by Emielb.

let fields = new fieldCollection( model.get( 'fields' ), { formModel: model.collection.options.formModel }, );

Verified broken. The trailing comma is breaking it possibly?

Here’s the fix (until next version):

Modify the file wp-content/plugins/ninja-forms/assets/js/min/front-end.js

1. Line 5381: Delete last comma
   [...]options.formModel } );
2. Line 5476: Delete last comma

   		UniqueFieldError,
   		FieldRepeater
   	) {

• This reply was modified 3 years, 9 months ago by Emielb.
• This reply was modified 3 years, 9 months ago by Emielb.

Same correction as @emielb — I didn’t read all the answers before posting the comment

—

For me on IE 11 (using the console logs) it required to correct two extra comma
front-end.js

line 5381 “model.collection.options.formModel }, );”
to “model.collection.options.formModel } );”

line 5476 “FieldRepeater,)”
to “FieldRepeater)”

After this the form loaded without any error.

• This reply was modified 3 years, 9 months ago by ydealdesign.

@jmcelhaney With version 3.5.1 it works perfectly on IE11: climate-at-home.de . Page is correctly loading. Form is shown. Thanks for the Fix!

FYI: Even after update to NF v3.5.1 my form was not showing in IE11. Applying @emielb’s fix (this one) which simply removes the two trailing commas (which still exist in NF 3.5.1) made the form show up again.

Thank you for posting that fix, @emielb. It saved us some time in tracking down a solution, and it should be included in the next Ninja Forms release.

That said, we can’t promise that you won’t see more IE11 issues going forward. Official Microsoft support for it ends in August of this year, and as we update our javascript code to be more in-line with modern standards, it’s very possible that there might be other conflicts. This is already the 2nd case of IE11 specific conflicts this year, and it’s only the beginning of March.

I realize that none of us can control the web browsers that our customers choose to use, but if possible I would be advising them to look into alternative web browsers.