A premiere vue, Il faudrait avoir un server un peu plus puissant.
Sur la home, tu es déjà à + de 9 secondes:
La page admin produit a pas mal d’ajax, et demande plus de resource.
Tu peux essayer d’augmenter le timeout de ton navigateur:
Si t’es en local, tu peux activer opcache dans ton php.ini:
D’autres paramtètres sont également modifiable pour de meilleurs performances mais faudrait plus d’info sur ta config.
Et le mieux, serait d’avoir un server plus rapide.
Vorsicht: Falsche Meldung durch angebliche DSGVO-Beschwerdestelle
hier was aktuelles
Li ho contattati a riguardo del modulo di sincronia con ebay (fastbay) ma a parte conoscere thirtybees non mi hanno confermato la compatibilità.
Qualche italiano l’ha testato con TB?
Ci sarebbe anche “prestabay” ma mi ispira di più “fastbay” (oltre ad avere supporto in italiano che non è mai male).
Habeis probado este de prestashop? https://addons.prestashop.com/es/pago-tarjeta-carteras-digitales/6492-tpv-redsys-pago-tarjeta-devoluciones-y-pago-un-click.html
Yo lo compré cansado del oficial y de momento me va bien. El oficial es una castaña y da problemas a mucha gente (a mi me volvió loco con el tema de los SSL)
We are working hard on this complicated module and it’s nearing the end. We do have a number of problems we have to fix in order to make it all compliant with other modules which have been altered to the PS GDPR way. Again, this is a extremely complicated module and it takes a huge amount of our time. We can’t give you a date when it will be finished. As soon as the module is released, both @mdekker and I will be overflowing the whole forum with “hooray the GDPR module is done!” posts.
Actually no need to mod the .tpl files
A quick search a few days ago resulted in me finding this:
A nice solution to the problem without having to tamper with the TPL files
This module might be tweakable for your purposes: Picklist module
It was developed for me by @kubilay and is supposed to enter the tb store as a free community module (together with this DPD DeliSprint export module).
@kubilay Would you be able to put them into the store?
I’d say the checkout itself is quite good, though I’ve had to put in a couple of frigs myself in relation to default states/cities as I have variable shipping prices depending upon location. However, I’d say their support is ‘cowboy’ level as I’ve seen with a number of module developers. Saying that, I’ve been using it since then with no problems.
That Presteam one sounds interesting, might have to take a look at that. When I bought the knowband I think it was the best available at the time.
Most likely not as each country has own laws how invoices can be issued and how they need to be in accounting books.
Thats the part where paid modules kick in with link from your store to your accounting program.
I’m sure there are some for France region as for my country threre are at least 5 optional modules available by local developers.
I renamed shop invoice to “proforma invoice”. Once order is paid, I issue Invoice with my accounting program to comply with local laws.
I think none of worldwide e-commerce solutions will ever provide compatibility with all the laws out of the box in basic package. No matter if paid or opensource.
Thats something for add on modules.
From my perspective it’s more than enough to release new version once every 6 month.
Simply don’t upgrade with every release, then.
Not upgrading means not receiving bug fixes, though. Making releases rarely means holding back these fixes from merchants for longer than necessary. Not sure what value that might have.
If you fear a broken shop after upgrading, that’s a bit a different issue. And one much more worth tackling. The answer to this is, make releases more often. The smaller the release steps, the smaller the chance for regressions, the bigger the chance to get issues fixed timely.
Also, with this high release rate, the submitted code won’t have a chance to mature in the branch
The awful truth is, unlike wine, code doesn’t mature by its self. Worse, even a big QA team wouldn’t help much. This isn’t MacOS, where every user has one out of a small set of hardware, running all the same theme, running all the exactly same applications. Diversity of shop installations brought in by hundreds of modules and themes is way to big to cover them all. With this enormous diversity, only real world installations can find eventual issues.
One answer to this is to make fixing newly upcoming issues ( = regressions) as seamless as possible. Which means many releases. Which is the reason why the upcoming updater module will support upgrading in even smaller steps, commit by commit. And which is the reason why this updater will support rolling back with a simple click. In a mockup I tried such a rollback (e.g. 1.0.3 -> 1.0.2) happened in less than a second, it doesn’t even need a wait icon.
The other answer is automated testing of the basics. Every single commit gets exercised with a test installation and a virtual user clicking through the shop, up to doing a purchase. That’s much better than what we had years ago.
I made a use of CMS.tpl and Created new CMS category containing all the Rights pages
and enabled that CMS.tpl Subcategories are only visible by logged in customers.
Removed the clickable Title link from the information block, so information (with my normal CMS pages) block does not call the cms.tpl
I read some article that css grid is better than bootstrap, available natively in the browser, cleaner html, more flexibility, and it will be the future of web layouting.
I looked into this article and it basically recommends stepping back to having no formatting in HTML. Just like it was recommended before Bootstrap arrived. All this with the knowledge that modern browsers ( < 1 year old) now support reasonable formatting.
While this is certainly a way to consider, it also requires formatting rules for every situation ever happening. Less HTML, much more CSS. Unless you have a very standardized layout like e.g. Wikipedia.
My problem is not with the amount of images for existing product. I need to get rid of the images that are left in the img/ folder for some reason. I have found a script here
https://www.prestashop.com/forums/topic/290936-cleanup-imgp-folder-and-image-folder-questions/#comment-2063626 but although it finds the problematic images it can not delete them for some reason (on my localhost)
Looks like your connection to thirty bees forum was lost, please wait while we try to reconnect.