Prestashop: [BOOM-4298] Large number of product combinations block browser

[prestonBot]

This issue has been migrated from the Forge. Read the original ticket here.

• _Reporter:_ laurentsupport
• _Created at:_ Tue, 14 Nov 2017 11:35:21 +0100

Hello,

we have a client site conntected with icecat database.
At now it haves 4 active shops and abut 60000 articles. From icecat we have about 7500 features.
When client connect to backoffice and operate on product the browser blocks because the Features tab are too large.
Is there a best way to paginate and manage features in admin product page?

Kind regards,

• How to reproduce the issue ?

N/A

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ salma.moakhar
• _Created at:_ Tue, 14 Nov 2017 14:42:34 +0100

Hi Laurent Ndaw,

We tried to work on the pagination declensions but it's not over yet.
We will also work to lighten the product page, it will take time, so unfortunately we have no solution currently.
I close the ticket, feel free to open a new ticket when needed.

Thanks & best regards, Salma

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ lila75
• _Created at:_ Fri, 26 Jan 2018 17:46:02 +0100

I have the same problem, and you can't do anything for us ?

So i have to close my prestashop account and go to see magenta or another one ?

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ khouloud.belguith
• _Created at:_ Fri, 26 Jan 2018 17:55:31 +0100

Hi,

We are aware about this issue and we are working on it.
No, this issue is in progress, it is assigned to our developer Jocelyn Fournier, he is working on it.
Thanks for your patience

Best regards, Khouloud

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ lila75
• _Created at:_ Fri, 26 Jan 2018 18:02:02 +0100

is it possible to contact her ?

i'm in late with my work...

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ khouloud.belguith
• _Created at:_ Fri, 26 Jan 2018 18:07:09 +0100

Hi ,

You can find his address mail Jocelyn Fournier in his profile

Best regards, Khouloud

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ lila75
• _Created at:_ Fri, 26 Jan 2018 18:11:10 +0100

I don't know where is her profile.

Can you send me her address mail please?

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ lila75
• _Created at:_ Fri, 26 Jan 2018 18:12:58 +0100

sorry, i find it.

 

Thank your for your reactivity...

best regards,

Lila

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ yoan - consult'in web
• _Created at:_ Tue, 27 Feb 2018 10:46:00 +0100

Hello,

 

I have the same problem withmy customer, is it possible tu have a return about this resolving?

 

Thanks Yoan

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ joce
• _Created at:_ Tue, 27 Feb 2018 14:02:43 +0100

boom-2950 needs to be fixed first

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ root
• _Created at:_ Wed, 18 Apr 2018 07:36:18 +0200

boom-2950 needs to be fixed first

Ok mr.Fournier,
now you fixed attribute saving problem in BOOM-2950
It is time to fix this one 4298 and take a look on similar behavior I reported at http://forge.prestashop.com/browse/BOOM-5350

I remember similar error on 1.6.* with endless spinning save button
without possibility to have scaleable [server side strength related] number of categories and products
Prestashop will lose it's competitiveness with other platforms.

[mpittiloni]

Hello, do you have any update on this issue? It's starting to be a very important...

[mchbani]

Hi
I have the same issue with 1.7.4.4. any update please?

[khouloudbelguith]

Hi all,

This issue is in progress, it is assigned to our developer.
Thanks for your patience & your understanding!

[tengav]

When we fixed that, the problem seems to be longer.
Is there a workarround here?

[JanicW]

Hello, is there any news about this bug. I really need to add more than 390 combinations.

[mpittiloni]

Hello, any updates?

[Ixreb]

Any news? I'm going to have to scrap an entire project already finished by this bug.

[khouloudbelguith]

Hi @arketik,

Sorry not yet, it is added to our bug roadmap so that it will be fixed. if you think you can do it, please do send us a pull request!
PrestaShop is an open source project, so it can be solved before if someone submits a pull request to solve it.
Thanks for your understanding!

[JanicW]

Do you have a timeframe or priority list?

[khouloudbelguith]

Hi @JanicW,

Our product team is responsible for the priority list of all the issues.
Thanks!

[johstrom]

Hi, after reading all of the comments in this ticket and all tickets that you have refered to this one, I understand that many of the issues I have experienced the last year with Prestashop is due to this.

I see that you haven't been able to give a time estimate on this fix, and the link to Jocelyn Fournier's profile you gave on top doesn't work.

I would need to know if this is an issue that your team can solve in a near future or if I need to start looking at other systems, like OpenCart.

I understand that a lot of users of PS have issues in regard to this. Can't you give us some insights from the product team, on the timeframe and their ambitions to solve the issue?

With kind regards,

• Johan.

[khouloudbelguith]

Hi @johstrom,

We have been aware of this problem for some time now. I just wanted you to know that if we didn't fix it right away it's not because we don't think it's important or because we don't care – quite the opposite.

Currently, most bugs on the Product page are very hard to solve, because of a mixture of very old code, design limitations of the current implementation, and several layers of patches and workarounds. The only way we can really solve them for good is by redoing the whole page. Which will take a massive amount of time.
Thanks for your understanding!

[johstrom]

Thanks for your reply. Can you be more specific on the issue here? Is it due to the many categories, many features or what is the bottleneck? Just to know if I can change my site to be lighter on the system.

I wasn't aware of any bottlenecks in the system like this, so I set up this new Prestashop as I wanted it to look like, meaning around 400-500 categories and 2 features with a total of 2700 values. Together with around +300.000 of products eventually (right now around 43.000 products).

Is it the categories or the amount of feature values or both that is the issue?

With kind regards,

• Johan.

[khouloudbelguith]

Hi @johstrom,

About a large number of categories which causes product page slow => it is fixed in the PS1.7.4.0 with this PR: https://github.com/PrestaShop/PrestaShop/pull/8896
Thanks!

[johstrom]

Ok, but I got 1.7.5.1, so the categories issue should be solved, then.

So what's the bottleneck in 1.7.5.1? Why is the product detailed page in this version showing 500 error with a huge allowed memory size exhausted as described in #13564?

[khouloudbelguith]

@johstrom, your issue is the same ticket reported here, a large number of products which block the browser, it is not fixed yet.
Thanks!

[Janoush]

Hello, i have this problem too. Cannot be solved (temporarily) by paging combinations or disable/enable showing combinations in product? We can at least edit products. Variants can import over xml.

[khouloudbelguith]

Hi @Janoush,

This issue is not fixed yet.
It is added to our bug roadmap so it will be fixed.
Thanks for your understanding!

[johstrom]

Hi, @khouloudbelguith - sorry, but I do not think the big issue here is the large number of products. I have another Prestashop site with 100.000 products, without this issue.

The site with the issue has around 60.000 products, but a lot of categories and features for every book.

You wrote above that a large number of categories shouldn't be an issue with latest version. And I know that Prestashop are capable to have +100.000 products without this issue. So: Is a large number of features the bottleneck for this version? Or what is?

My sole question is: what is the issue you are trying to fix, if not the number of products and not the number of categories? Your answer can help me to understand how to build our site with Prestashop and avoid this issue (i.e. use a lesser amount of features etc).

[khouloudbelguith]

@johstrom, your issue is similar to this ticket: #13698?
Is it?
Thanks!

[ramibak]

hello @khouloudbelguith , i have also a store with prestashop platform with same problem ,i have 12 main categories and more than 380 subcategory , i use api importer to import products from aliexpress , and when i finish import and navigate to any part of my website or even to check the imported products , it could take up to 4 min until it opens the page for me and for the other users in my back office , still looking for solution

[johstrom]

@khouloudbelguith I did not get a PHP Fatal error: Out of memory error, but a Error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes)

Our hosting increased the memory limit to 1024MB, however, the same error was presented as well (this time with the increased value of the memory):

Error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes)

I am too noob to see if it could be the same error regarding categories as ticket 13698, but it surely seems familiar.

[johstrom]

@khouloudbelguith I asked the hosting, and they provided me with the exact error:

(1/1) OutOfMemoryException
Error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 20480 bytes)
in FileProvider.php line 69
vendor/icanboogie/cldr/lib/FileProvider.php on line 69

[mwijngaard]

Hi @khouloudbelguith . I think I'm having the exact same problem (PS 1.7.5.1). A function trace shows that it's definitely due to the number of product combinations. I don't see how categories (mentioned elsewhere in the thread) have anything to do with it. What happens is that the system is building up a single huge form, containing all the product combinations as subforms twice, of which the first time also includes subform containing about 15 fields for each combination. In my case I have a little over a 1000 combinations (which worked fine in PS1.6) so that equals 1000 * 2 + 1000 * 15 + some extra fields = more than 17000 forms. Which is obviously too much memory wise.

Of course the actual fix would be to change the way product combinations work, and not store every possible combination separately in the database, but I understand that that would be very complex. So in the mean time, would it be possible to slightly change the way the product page works? It could for example only load the combination forms when the combinations tab is opened, and only load the combinationdetails properties when they're opened for a single combination. I think this is what Janoush mentioned above. This doesn't seem like a major redesign of the product page to me, or am i getting that wrong?

[khouloudbelguith]

Hi @mwijngaard,

Thanks a lot for your feedback.
this issue now is added to our bug roadmap.
So, our developers will fix this issue in the right way.
Your feedback also will help us to fix the issue.
Below are different ways to help us to fix this issue:

• If you found a module that solves the issue, please add a comment with a link to it so it is possible to share this knowledge with other impacted users
• If you are a developer, you can open a pull request on GitHub with your bug fix

Thanks!

[Janoush]

Any new information about "Large number of product combinations block browser"??? Is fixed yet or not? If not why is fixing takes lot time (about more than one year?). When it comes out 1.7.7? Thanks for reply.

[khouloudbelguith]

Hi @Janoush,

We are working on the product page to fix all issues.
https://github.com/PrestaShop/PrestaShop/issues/13891
Thanks!

[Webgaict]

Hi,
are there a solution?
Thanks!

[Punisher07]

Same problem here.

Save buttons from product don't save if the product have some combinations.

after i removed

submitHandler: function(form)
{ form.submit(); }

from /admin/themes/default/template/controllers/products/helpers/form/form.tpl , the natives modules save naturally (informations, price... - they are saving even with a lot of combinations) , but the non-natives still got the problem (Product extra tabs, booking...) .

If product have few or none combinations, the product saves perfect. (non-natives or natives modules).

Any news?
PS version here is: 1.6.1.0

[khouloudbelguith]

Hi @Punisher07,

Sorry, but as you may already know, normal maintenance support for PrestaShop 1.6 ended in October 2018, which is now in extended maintenance mode until June 30, 2019.

During this period, and in order to ensure the stability of current 1.6 shops, only critical bugs and security fixes will be fixed in the PS1.6.

Thanks!

[Punisher07]

i got it @khouloudbelguith

but, in the newest versions, the bug was fixed?
As i see, here and in the other foruns, it seens may not fixed yet, or not?

[khouloudbelguith]

@Punisher07, no, it is not fixed yet.
It is added to our bug roadmap.

Thanks!

[Webgaict]

An imminent solution does not exist?

[drumstore]

Hello :)

@khouloudbelguith
Is there any chance That Prestashop solve this problem soon ?
Same problem here. www.drumstore.pl i have good VPS server in A2hosting (presta recommended)

I have noticed that, quite frequently mysql serwer is going away. here are few lines from the log:
[19-Sep-2019 12:36:52 Poland] PHP Warning: PDO::query(): MySQL server has gone away in /home/drumstor/public_html/drumstore/classes/db/DbPDO.php on line 156
[27-Jul-2019 23:33:52 Poland] PHP Warning: PDO::query(): MySQL server has gone away in /home/drumstor/public_html/drumstore/classes/db/DbPDO.php on line 156

The frontend goes down then and we have to clear cache manually to get it back working.

I know that presta is free, so I cannot complain but I invested lot of money in presta modules and development.

thanks :)

[khouloudbelguith]

Hi @drumstore,

This is a major issue with the top watchers label.
We are working on the product page to fix all issues.

13891

Thanks for your understanding!

[ftardio]

I'm facing the same problem. In a shop using products with multiple attributes, you can get more than 2k combinations. I use a module to generate combinations, because the main interface is unable to manage it properly. But when a change in some main features is needed (change price for example), you have to wait several minutes to get all combinations loaded in background, sometimes the server goes out of memory, memory used by browser scales to more than 2 Gb, and most times you get an error when trying to save changes.

It's not usable that way. Developpers know it. And after 1 year and a half (or maybe 2 years), there is still not solution for that. Annoying. :(

[maofree]

Hi
can I know if it is present some fixes?

[marionf]

@maofree

To fix this issue it's planned to add a pagination system: #16103 during the re-migration of the product page

[maofree]

yes it is a good idea

[5koder]

We should also be able to filter the combinations. Please also add a filter.

[marionf]

@5koder there is already an issue for that, please follow: #16108

[Janoush]

Hello, i have another idea. My product combination have for example 26.000 combinations. I dont need all combination in sql, only information about value. So simple way is make dropdown or button label in "customisation". I take minimal memory usage and frontend be fast! Not all need 100% product combinations. Can you make it? it won't be hard to make it!

[marionf]

Hello @Janoush
Your request is different from this issue, you are talking about product's customization while this issue is about back-office product page performance
Could you please create a new issue ?

[blaz-blazer]

Hi, what's the status on this issue? At the moment Prestashop doesn't seem to be suitable for online shops with products that have more than 60 combinations as the saving time is incredibly long (+120 seconds) and managers can't work like this. Having +60 combinations is not that rare; 10 colors and 6 sizes is all it takes. In which version are you planning to fix this?

Regards,
Blaz

[marionf]

Hi @blaz-blazer
It's planned to be fixed in the 1.7.8 with the symfony migration of the product page

[blaz-blazer]

Thanks for info @marionf. Do you have an ETA for version 1.7.8? I know it's hard to predict but just an estimate.

Blaz

[marionf]

The 1.7.8 is planned for the end of the year

[maofree]

hi
this is a big problem, at this moment that page cannot manage many data

I've seen if there are many combinations and many images I need to associate only a part of images for each combination, to get the possibility to save the changes.
I thought I had solved but today I get the same error, to solve I need to remove all combinations and start again and reduce the data for each combination, It is not possible to wait other 10 months to solve this problem

[maofree]

that error happens with 1 language, to solve it I need to remove all combinations are restart again setting less images (or removing other things).
removed all combinations the page returns to work.
Now I've added a new language, so the error returns also without combinations.
it is not possible to work in this mode for site with many data for some products

after some tests I solve this new error, removing all text from the long descriptions of both languages

so the problem is the limits on this page

[ahmelg]

I have the same problem. I have version 1.7.6.5 with products with 702 combinations, it crashes when I save.
Have you solved the problem?

[5koder]

@ahmelg same here. I really need a workaround

[jbenezech]

A dirty workaround for those who can afford it: https://github.com/jbenezech/PrestaShop/commit/004cc66947e2cde4b582d86a85c1c48f174a5113

Of course you won't be able to update combinations from the product page and of course you'll have to re-apply the patch when upgrading prestashop, but until they finalize their update (with pagination), you should at least be able to edit products normally.