Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem on Magento 2.3.5 #1

Open
hewgim opened this issue Dec 10, 2020 · 3 comments
Open

Problem on Magento 2.3.5 #1

hewgim opened this issue Dec 10, 2020 · 3 comments

Comments

@hewgim
Copy link

hewgim commented Dec 10, 2020

Hi there,

I've just installed this extension on a Magento 2 development site running on Magento 2.3.5

When I first installed it, it seemed to work, but since I've done a full deployment to production mode the sales order grid just doesn't appear even though the page says that there are x number of rows. I get the following javascript error: TypeError: undefined is not an object (evaluating 'mode.template'). When I swap back to developer mode, I still get the same problem.

I've tried to debug the code and was wondering if it may be a clash with the Magento_AsynchronousOperations module which seems to extend the grid listing component itself.

Do you know if this extension has been tested on Magento 2.3.5 with the Magento_AsynchronousOperations module enabled ?

Any help would be much appreciated.

Kind regards

Mark

@angelflo
Copy link

angelflo commented Apr 8, 2021

Hi,
Did you find a solution to this ? can you confirm the bug ?.... I would like to install this extension on my magento 2.4.2 version

@carlos-reynosa
Copy link

It looks like the issue is that the columns need to be manually selected again and then the rows will appear.

@robaimes
Copy link

robaimes commented Oct 28, 2021

This issue is also present on 2.4.2-p1, presumably also in 2.4.3.

After a little debugging the problem is somewhere in the js/grid/controls/colors component. Loading the grid for the first time after installing this module always produced the error and I could only make it work by using the element inspector to remove the loader element, then configuring a colour to make the bookmark config update.

Playing around with the storageConfig property of that component seemed to make it work a little better, but not reliably. Might be barking up the wrong tree there though. I think the problem may be that this component is trying to update the localstorage/bookmark config on initialisation/too early as opposed to only when a colour is changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants