Hi,

This may not be one for you, but one for Hikashop, but since the latest update to Joomla 3.6.5, I now get the following error when moving through the checkout process in Hikashop.

Unfortunately, I also took the opportunity to update a number of modules/components at one go, so I am not sure whether this comes from the Joomla or the components updates.

The new error is:

0 - Input_0:689: ERROR - Object literal contains illegal duplicate key "getSelected", disallowed in ES5 strict mode },getSelected:function(){return this.selectedRows;},serialize:function(){var a=this.previous.apply(this,arguments)||{};if(this.options.selectable){a.selectedRows=this.selectedRows.map(function(b){return Array.indexOf(this.body.rows,b); ^^^^^^^^^^^ Input_0:696: ERROR - Object literal contains illegal duplicate key "getSelected", disallowed in ES5 strict mode c++){if(this.options.selectHiddenRows||e[c].isDisplayed()){this[g](e[c],true);}}return this;},deselectRange:function(b,a){this.selectRange(b,a,true);},getSelected:function(){return this.selectedRows; ^^^^^^^^^^^

Googling the result leads to several different threads, some of which blame the template, others the extensions.

If you happen to have come across this before, I would be grateful for any pointers. I will post with Hikashop as well to see if they can explain it.

Grateful for any help.

Best wishes


Richard

I should just mention I have restored an older site to get this working again (successfully) so you may not see the error, and will work through the updates one at a time to see if any recreate the problem.

If you come across a solution to the problem meantime, please let me know.

Many thanks


Richard

I found one thread on the t3 forum, but they say that was an issue with server cache.

Are you running the latest t3 plugin on the site?

I found some other threads related to chronoforms and artiosef.

The template doesn't define strict mode so I think it must be coming from another extension.

In the console you should see a link to the right of the error which should let you know which file it's coming from, which should help to pin it down.

Regards,

Rob