PS 1.7.2.4 Back End Page take 5 minutes to Load (modules, product save, shipping, ...) #11186
Comments
|
Hi @matteolavaggi, Could you please try to disable the gamification module, clear cache, check & feedback. |
khouloudbelguith
added
BO
|
Hi dear i've renamed the gamificaton folder to off.gamification just week ago with no improvement on functionality , you mean this? |
|
Hi @matteolavaggi, We need to retrieve the PHP error log and the debug mode report in order to find out what's wrong. Thanks! |
|
Hi, we have provided information about version and server. We dont get any php / apache error in the error log , and debug mode in backend dont print error, so how we can send to you usefull information? we get a timeout error after 4 minutes from proxy so its not easy to debug the problem, any idea to get more information usefull for you? |
|
There also is function to take Your PrestShop account avatar from Prestashop.com... Please look deep into browser console and resource requests - this might help You with this lag/performance issue. |
|
Hi @PrestaShark, Is it the issue that you described: #11145? |
|
There is no information on browser console that can help, simply it take 5 min of TTFB. @khouloudbelguith my login email is different than the one on prestas.com, but i've also disabled from Tools.php the connection to prestashop.com setting 'is_addons_up = true' to false |
|
Hi @matteolavaggi, Have you many products and much data to load? |
|
i have about 30k product, but a dedicated server powerfull. We use with no problem massive import / edit module for handle 500/1000 product at same time. Also other section of Backend work with no problem like category and product page (only the save function has problem) |
|
@matteolavaggi, we are aware of this issue and we are working on it. |
|
Hi dear, so there is any way to fix this on my 1.7.2.4? The problem i have in the module page is not related to combination i supposed! Also i've about 10 to 15 sku with combination on 30K catalogue, and issue on saving it happen on all product, not only when work on a combination one. So i think you are not in the right way to diagnose this problem |
|
@matteolavaggi, did you installed any custom module before this issue occurs? |
|
we setup a cache module, but removed, clean folder and database, clear cache and revert back server to previous, so the issue start before this module installation, we found it because we cant see new order placed by customer :( ! Any idea where to look? this is a redirect problem on the account page |
|
@matteolavaggi, have you tried to contact the module author? |
|
Sorry dear, i've made confusion on 2 issue. This problem on module page start at the installation of PS and is no related to any of the module we install later, at zer day we start with this problem and not yet found a solution |
|
@matteolavaggi, the mode SSL is enabled in your shop? to this Thanks to check & feedback. |
|
Our store is FULL https, i've change the ip but still same problem. |
|
Hi @marionf, I did not manage to reproduce the issue with PS1.7.4.3, PS1.7.3.3. |
khouloudbelguith
added
Modules catalog
|
I can't reproduce it, performance depends of a lot of things |
marionf
added
the
Can't reproduce
|
@marionf performance? this is not performance! this is a controller / symfony bug big like an house ^^! What kind of performance can take 5 minutes to load a page and make fail to save product? we can sorto 1000 product in back office in 1/2 second, load every other page lightning fast! |
|
@jocel1 what do you think ? |
|
according to the description, I would bet it's a session issue where at some point a backoffice page doesn't finish its loading somewhere, and it blockes all other page loading relying on php session (basically all BO pages). We need to fix all the bottleneck which could slow down BO pages, and work on a way to close the user session much (much!) sooner than what we have currently. I'll create a specific ticket for this session issue, my feeling is it's a high priority issue :) |
|
@matteolavaggi FYI I'll try to take a look at the session issue in the upcoming days |
jocel1
removed
the
Can't reproduce
|
Hi, any update dear on this way? @jocel1 |
|
not yet, the session subject is not an easy one |
|
Yes but is an important one :( and this problem still present in the last 6
major release of PS ;)
Il Mar 27 Nov 2018, 18:44 Jocelyn Fournier <notifications@github.com> ha
scritto:
… not yet, the session subject is not an easy one
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11186 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXpl74WfRR1KFNvxDPAAQ33S15Se0Yenks5uzXmZgaJpZM4YBl2v>
.
|
|
Still in ToDo :P 4 prestashop installation, different version on different server, all suck opening module page or position hook transplant page ... good job dev team............................................... |
|
Hi there, Not having an issue fixed immediately (or in a fixed timeframe) does not mean that it won't be fixed, or that we don't care. It doesn't mean that the issue is NOT important either. It just means that other issues have been considered, for whatever reason, more important, so they were (or are being) tackled first. There's an immense amount of work to be done (997 issues right now, and growing!), and tasks take time. And in your case this not something we can easily reproduce, so this is even more complex. Developer time is limited, so if the amount of issues opened in a certain timeframe exceeds the amount of issues that can be processed using the available developer time, tasks will simply pile up. This is common to ALL projects. Due to the number of pending issues, sometimes they may get lost in the pile and be forgotten about, so it's not a bad idea to ping us there from time to time to give us a kind reminder, even if it's been a long while. But here's the upside: PrestaShop is an open source, community project. If you find that any issue is critical for you, and it's important to have it fixed ASAP, then you can invest into having it done. You can hire a developer to fix it, or if you are a developer yourself, you can try doing it on your own. The most important thing is to share that fix with everyone by submitting a Pull Request -- that's what the open source spirit is all about. |
|
The session issue is real, but I'm not sure it's related to the OP's problem. Extreme slowness usually means that the shop cannot access an external resource, and it timeouts. @matteolavaggi Please verify the following:
|
So where prestashop spent all the money they get from addons selling? Not in proeuct develop, not in bug fix... Very bad project hope it will survive next years but i'm not sure. Is one of the most expensive ecommerce platfrom due to module need for every feature, and the bad supported and buggest one ... |
Dev mode is of, this url can be reached. Only the possibility that closing spammy url to the shop can generate trouble is a good way to evaluate the whole project ... i'm very I'm really sorry to have started 2 projects on prestashop. It is not possible that version 1.7.5 has the same problems as 1.7.1 ... an unusable search for example ... while addons sells thousands of modules a day to solve the lack of basic features for an ecommerce. And the development team consists of 20 people .. |
|
|
If you use 1.7.1, you should test and migrate to 1.7.5, and you will see that developers do their work. Its' faster, more stable, and it has many improvements and features required by the community. If you compare to other e-commerce software, Prestashop is one of the most complete out of the box. If you need more features, it usually means you have a specific business workflow. You can actually sell online with a basic Prestashop, a server, a domain name, and a payment solution. You can also buy a few plugins and a theme, and it will be very, very cheap compared to the cost of custom developments. Because the cost of a module is supported by the many who buy it, you will pay only a small part of the total development price. You can also consider Prestashop as a component of a complex project, synchronised with ERP, CRM, factory workload, etc. This case can cost a lot,bbut company are doing that because they know they will have a good return on investment. About Add-ons: most of the money go back to the modules developers. At the end of the month, they pay their bills, and they can continue to develop their modules, support new users, do maintainance, and eventually create new plugins for new features. Running a Prestashop website is not that expensive, compared to other solutions on the market. Open source software doesn't mean that everything must be free of charge. Even Richard Stallman sold copies of Emacs to fund the FSF and GNU. |
This is complete not right. 100% not right.
prestashop addons sell huge amount of module compared to other platform, and there are 2 or 3 developers answering 900 issues ^^ ! (900!!!!, many of them present in the last 4 major release)!!! Ah not last backoffice limited from mobile phone (instead fix bug every new release of PS remove some function to force module buy)... The problem is not PAY for get feature and support, the problem is that the main project has the baddest dev team i've ever seen, and to increase selling rate every release something was removed from the core package ^^ > this result in LOT of third part module > this result in lot of other bug cobined with core bug... Prestashop project has completely lost the direction. Have you EVER take a look on magento configuration / installation guide and information ?! Compare with the prestashop user guide ... My prestashop 1.7.2 backoffice crash with less than 400MB of php memory ... 400MB ?!?! really?! This is enought to drive a shuttle from US to MARS... |
PrestaShop Addons is quite unique in the CMS world: the main marketplace is operated by the company behind the project. The fact that there are over 900 issues is specific too to the PrestaShop project:
the "baddest dev" team you have ever seen. did you actually see them, or meet them? do you really know other dev team ? how could you compare? what is your experience with best practices in collaborative open source software development? if you want to come at the office and meet them, let me know, I can organize that, and I am quite sure you meet awesome people. it's not because you disagree with their priorities that they are bad devs. Again, please test 1.7.5, item location and other stuff like that are back. And look at the 1.7.6 roadmap, the plan is to introduce back many features and modules required by the community. It is possible, now that the base of the 1.7.x is good enough. BTW, if you prefer Magento, why are you using PrestaShop? this is a true question, I am really interested to know the answer, that would be an interesting case. If you are still in 1.7.2, it is really time to migrate to 1.7.5, like many other merchants do. Before 1.7.3, there was some performance issues. It's fixed since 1.7.3 and 1.7.4. However, again, what is the size of your catalog? How many products and variations? This is a critical information to estimate the need in server performance. (traffic is the second critical information) |
|
Dear you write about 10 times 1.7.5, but why dev a 1.7.5 if 1.7.4,1.7.3,1.7.2,1.7.1 still has same bug ?! And also you (right) write that this is not the bad open source project, right but this is one of the open soirce project that get MORE money from pay module, and every module installed make another step harder upgrade. So if the company behind the project operate directly the worlds largest marketplace of addons, why there is all these problem? Because the "company" invest 99% of profit in other than in make good, robust, scalable and upgrade proof software! Still many PS 1.6 on the markem this is crazy ... a seller that must use a 5 years old distribution because the new one is impossible to migrate (and also to operate in mid size ecommerce due to bug) , is a complete failure for a project. Our catalogue is 65'000 sku, no variations, and we start to have performance isse on backend timeout whe we have 1000 SKU. Have you ever try to migrate a 1.7.2 to 1.7.5? We have try 5 times in differente way, no one result in working platform. Unaccessible bo and fo ... so "solve" bug in new ecommerce version that are impossibile to update is a good job? We spent about 3k $ in pay module for every ecommerce we start to manage, plus the hosting cost to handle not good scripting (more power less poblem when scripting is not good). if we compare the price with hosted solution like shopify we cant be happy to have choosen this way. TODAY prestashop is not update proof, this only limitation make all the work to launch new release not usufull for a merchant. Its not so simple, ok, but i'm sure that prestashop company has lost the way, the last 2 years The commercial management of the last two years is to put on the market new versions that do not FACE and solve the fundamental problems, and to sell as many modules as possible. This does not generate robust software and does not generate loyal customers. Talk about open source when at the end the average life of a release is 12 months (and the bugs are not resolved), and the average expense in modules is $ 3000 for each release ... it's an open source that generates much more cash of a lot of paid software. It would need a much more solid development. |
|
So, I told you already: the most important budget of the company is dedicated to improve the PrestaShop open source project and to finish the migration to Symfony. However, yes, you are right, there was a lot of things to fix. Most of the important things are fixed, and there is a roadmap to finish in order to ease the migration from 1.6 to 1.7. That's how the energy of the employee is used since 2018. We have good feedback from people migrating from 1.3, 1.4, 1.5 or 1.6 to 1.7. And of course, it's possible to migrate from any 1.7.x to 1.7.5. But, it some cases (specific modification, overrides, some modules, or very important catalog) the auto-upgrade will not work as expected. This module has been completely rewritten since last summer, if you have a specific issue, please open a bug with details. Also, maybe you should contact an agency in your area and get some help? you could save a lot of time, and time is money. Please compare the pricing for Shopify for such a huge catalog and the features you need: I guess that the cheap starter option will not support your use case. Also, take in account that PrestaShop is open source, so:
Again, all projects have non fixed issues. That's the life of software, open source or closed source. It's just more visible in open source, particularly when a project chose to keep open issues with no recent activity like the PrestaShop project. I am very surprised that you have to buy again the modules at each release of the PrestaShop project. That's not how it's supposed to work at Addons, except if you want to renew your support when you upgrade. And no, our project does not generate much more cash that other open source project. You should compare the prices of our competitor with your use case, and the cost of any custom work on any other open source solution. In most cases, buying modules is still cheaper than a week of work from a freelancer or an agency. Please note, that most agencies and freelancers also buy module to save time and money for their customers... and again, please open an issue about your search issue. is it on the front end on in the back end ? |
|
to finish the migration to Symfony > from 2 years There is no ETA available so this is only 900+1 issue taht still open . Still get a PS solution with much bug than function ^^ and only "NMI" or "TODO" or "ASSIGNED" status to every issue reported .. from a 2 years old release :P ! |
hibatallahAouadni
added
Can't reproduce
|
I think your problem was is module "Merchant expertise" (native Prestashop) it is calling "gamification" in the modules folder. So by disabling it, everything works fine at the backend. |
Describe the bug
When try to open module manage page in back office it take 5 minutes to load.
If you try to access direct module configuration page it work great.
The same extra long tame will take place on product save , shipping service page so its a controller problem of the backend.
Every operation made by direct url (example open shipping agent with direct url and id) work great.
Product save with 3rd parts module like import or massive edit work amazing fast.
Problem is damn prestashop buggy controller of the backend.
To Reproduce
Steps to reproduce the behavior:
or
or
or
There is no error in web server or php log in both scenario.
Additionnal information
INFORMAZIONI DI CONFIGURAZIONE
Queste informazioni devono essere indicate quando segnali un problema sul nostro bug tracker o sul forum.
INFORMAZIONI SUL SERVER
Informazioni sul server: Linux #163-Ubuntu SMP Mon Sep 24 13:14:43 UTC 2018 x86_64
Versione software del server: Apache/2.4.33 (Ubuntu)
Versione di PHP: 7.0.32-2+ubuntu16.04.1+deb.sury.org+1
Limite di memoria: 4G
Tempo di esecuzione massimo: 6000
Dimensione Max. dei file da caricare: 200M
Modulo PageSpeed per Apache installato (mod_instaweb)
INFORMAZIONI DATATBASE
Versione MySQL: 5.7.21-20
Server MySQL: 127.0.0.1
Nome MySQL: Prestashop_1
Utente MySQL: prestashop
Prefisso delle tabelle: ps_
Motore MySQL: InnoDB
Driver MySQL: DbPDO
INFORMAZIONI DEL NEGOZIO
Versione di PrestaShop: 1.7.2.4
URL negozio:
Tema attualmente utilizzato: classic
The text was updated successfully, but these errors were encountered: