Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Leaderboard


Popular Content

Showing content with the highest reputation since 09/22/2021 in all areas

  1. 2 points
    PHP 8 is not supported. I guess this will be the source of the problem.
  2. 2 points
    This is actually a first time issue only. This was always a problem with bleeding edge. When you updated your store to bleeding edge, we never actually saved information about the exact git commit that 'bleeding edge' referred to. Without that information, core updater couldn't really check what files were modified. It always used files from latest stable version (1.2.0), and compared files on your server agains them. Obviously, any and all modifications to core files performed between 1.2.0 and git commit that was used for bleeding edge would be marked as 'modified by user'. Which is not correct. From now on, core updater will store the exact revision inside _TB_REVISION_ constant. _TB_REVISION_ can contain either specific tag (1.2.0), or exact git hash like a09146c3db421e1604dd45dc8d63925c4aee7c4f. Core updater can use this information to compare your files with proper git commit.
  3. 2 points
    Just a shout out really, for high quality, TB compatable modules with great support Some of us veterans may remember Vekia (Milos) from the prestashop forums. He was brilliant with help and support - but he did take a step back from those forums. I have recently purchased a couple of modules from him (pop-up manager and combinations table on the product page). Not only did he give excellent support but he added features to the modules for me also. Brilliant. If you do need any modules, his site is a good place to start. I did heavily suggest he joined us on this forum as he has fabulous insight to the workings of this ecommerce platform - let's hope he does https://mypresta.eu/
  4. 2 points
    I totally agree with the above. Very fast and professional service. In the past I also bought modules at https://mypresta.eu/ and guess what, still working on TB. The Combinations Table module is suitable for many types of shops. Some suppliers get it what support means to customers. https://mypresta.eu/ is definitely one of them.
  5. 2 points
    This idea comes up a lot. Also when we talk about modules. To be honest: I haven't seen any collaboration coming, out with a serious result, since I am in PS World. While this idea makes sense in theory in pratice it (almost) never works. Btw: I worked like 10 hours at the weekend to push my theme project a bit forward. I am very happy with the progress. 😎 IMO I already found a very stupid behaviour that each theme copies from the other themes (root is probably 1.6 PS theme), but was probably never intended to do so. If you have ever looked into the tpl files, you have maybe noticed that some tags are opened in header.tpl and closed in footer.tpl. Very unnecessary... Just use layout.tpl for it. Such stuff is the reason, why I prefer to do it from an empty folder.
  6. 2 points
    @yaniv14 OK. Understood @cienislaw given the discussion over the last 7 months, I am inclined to agree with you. With that in mind, I think it is best to ask: Who would like to be involved in decisions/discussion relating to the new theme? (anyone is welcome — no coding or design skills required) In this group (looking at those who have commented on this thread and discussed the topic with me), I assume the following people would like to contribute suggestions? @veganline, @Mark, @Traumflug, @datakick, @cienislaw, @zen, @wakabayashi, @DRMasterChief, @yaniv14, @Wartin, @AndyC, @toplakd, @superbiche, @Briljander, @Mediacom87, @netamismb, @Billy Please make me aware if this is correct, or if you would like adding to or removing from the list. Once we have a group decided, all (fundamental) suggestions should be submitted within a given time frame (prior to any designs or code being written). I will do my best to document and summarise suggestions. I assume everyone is happy that any disagreements can then be settled by vote. Once the community has spoken, I will do my best to design the theme based on the community's wishes. (It is unlikely that the design will please everyone, but hopefully the majority will get what they need out of the theme). Is anyone available to support @yaniv14 in the near future, should he need it?
  7. 1 point
    You may want to try this module: https://www.prestashop.com/forums/topic/47173-module-list-of-customer-out-of-stock-registrations/page/2/?tab=comments#comment-3277907
  8. 1 point
    The issue I run most often into is the inability to attach files with the customer service messages. Probably I am biased because I sell software. But I can imagine that other people will find it handy too for sending manuals, product previews, etc.
  9. 1 point
    3.3.0 - 10/15/2021 Complete redesign of the generation of emails sent to carriers to facilitate the management of translations with the native system of PrestaShop Improvement of the FAQ with the precise name of the directory of the active template on the store Display of language folders in the FAQ in alphabetical order Added a configuration option for each carrier to display a message when an email is sent to the carrier 3.2.0 - 10/11/2021 Code rewriting following the redesign of the Orders page in Symfony in PrestaShop 1.7
  10. 1 point
    The ajax problem will be, most likely, caused by mixing http and https. Browser might block ajax requests from http to https. Make sure you are logged in to your back office using https:// protocol, and then try update again.
  11. 1 point
    Looks like this commit is the culprit: https://github.com/thirtybees/niara/commit/6abc6b7e555caadb48b02e662ffd8da105a927f8#diff-25beb89b157fe43848421e7b4cf456c7fa1a603879047d3c1e5c636aa5dff62e For some reason the working templates were overwritten with this mess. Probably not an intention. I will revert this commit
  12. 1 point
    Yes, that's the advanced functionality that we plan to put back there in the future, very well hidden so that nobody will use it 😉
  13. 1 point
    Of course I can ask them to look into database 🙂 But fortunately I won't have to
  14. 1 point
    Why? For people that will use Stable releases this is not an issue. The revisions will always match official release tags, such as 1.3.0 or 1.2.0. If you are using bleeding edge, then you will see current exact git commit. This information for machines, not for humans. Revision is precise and it nicely correlates with information on github. I understand that from human point of view, it's nicer to see 1.4.134 instead of d601a7dfa69025341ea598f558885b6cbbd7b7b4. However, nobody would be able to figure out what exactly is part of version 1.4.134, or what are the differences between 1.3.0 and 1.4.134, simply because 1.4.134 would not tracked in repository. With revisions, we can look at github and see it all. What is part of this version? https://github.com/thirtybees/thirtybees/tree/d601a7dfa69025341ea598f558885b6cbbd7b7b4 What are the differences between 1.3.0 and current bleeding edge? https://github.com/thirtybees/thirtybees/compare/1.3.0...d601a7dfa69025341ea598f558885b6cbbd7b7b4
  15. 1 point
    I believe you were on some bleeding edge version before? If that's the case, then rest assured -- this is the one-time issue only. Next update will not be affected. When updating to bleeding edge we didn't actually saved exact git revision that was being used. In your store the only available information was that this is some variant of 1.2.0. Not very useful. During update, core updater asked server for a fingerprints of files for version '1.2.0', and checks it agains files on your server. Of course, every files that were modified between 1.2.0 and the bleeding edge version you have on your store will have different fingerprint, and so they will be considered modified. The new core updater fixes this issue -- we now define new constant _TB_REVISION_ that points to exact git revision or tag. During update, core updater will ask for fingerprints of files for this exact revision.
  16. 1 point
    Updating indeed allowed it to go further. Thank you. The database software is MariaDB 10.4.8
  17. 1 point
    From server log I can see that some clients requests file list over and over again. Looks like the client fails to store the file list to cache. At least thats the only explanation I could came with. This is (hopefully) fixed in latest version of the module. Are you using 1.4.3? Edit: From your log it's evident you are using 1.4.0. Please update core updater module. BTW, what mysql version are you using?
  18. 1 point
  19. 1 point
  20. 1 point
    It looks like DHL has switched to a new API and maybe dropped support for older WSDL if you look in there main wsdl page you will see: <wsdl:documentation> NOTICE: This WSDL is valid for implementations that are in production prior to 14th March 2021. Please note that there is a new WSDL as part of the latest MyDHL API Developer guide. Please contact your local DHL IT Contact. </wsdl:documentation> i am not using dhl so I can't tell much. Good luck
  21. 1 point
    Hi, We have installed stripe module and testing it in in the test mode. During checkout it redirect to stripe website to enter the credit card information and stripe is successfully complete the transaction. Once the transaction is completed and returns back to TB, it shows "Failed to validate order" we checked in stripe module> Stripe Transaction tab it shows "Charge Failed" Any ideas, how to fix this issue?
  22. 1 point
    The root cause is here: /home/veganlin/public_html/classes/Mail.php(293): Swift_Mime_SimpleMessage->addBcc(NULL) The system is adding null BCC address. Now, the question is why. Do you have some module that hooks to hook actionEmailSendBefore? check BCC all mails to configuration option in Advanced Parameters > Emails can you PM me access to your back office?
  23. 1 point
    Disable module mailalerts and try again. If it works, enable it again, and fix its configuration.
  24. 1 point
    The root cause is well hidden... this module does excellent job hiding everything important from everybody Edit file modules/stripe/classes/PaymentProcessor.php, find line this->addError($this->l('Failed to validate order'), (string)$e); and change it to look like this: d("$e"); $this->addError($this->l('Failed to validate order'), (string)$e); The d("$e") should display additional information when error happen. Hopefully we can use this info to figure out what's actually wrong
  25. 1 point
    Looks like when you updated module, its configuration was reset, and it's back in testing mode. The payment intent is stored in cookie, and is no longer valid. Please check module configuration and switch it to live mode, if that's what you are testing. Also, clear browser cache / cookies.
  26. 1 point
    You may have hit the nail on the head. I will change the rounding to each line and see if that make a diffference. Thanks
  27. 1 point
    Good to know, Now pass us the aff links and never log back in! 😄
  28. 1 point
    Thanks. I will try. Well. I finally got it work.
  29. 1 point
    Nah, theme switching will not create such mess. If I remember correctly, back in the day when we were updating from 1.0.3 to 1.0.4 manually, the instruction was to remove these modules from filesystem. But that did not remove references in the database, obviously. I had problems with these modules once, so I had to create consistency check module. That can help you to get rid of these easily.
  30. 1 point
    Thanks. This one is working for me too.
  31. 1 point
    This file: https://forum.thirtybees.com/applications/core/interface/file/attachment.php?id=220 solved the problem for me.
  32. 1 point
    Hi @SeaSky, unfortunately this is not possible with the current module. This kind of data are not exposed Petr
  33. 1 point
    I have been following this thread and wondered if we can gain some insight from other systems. So digging around I found that Xoops has a new theme based on Bootstrap. Now I know that this doesn't relate very well to TB. However we can glean some powerful insight on how these new themes are designed for said opensource systems. Does this help any? Well yes I thinks so as it's a free guide on how other systems are moving forward. Let me go on to add that Joomla now has themes based on Tailwind. I will provide links to the new Xoops theme. You can google for the new Joomla examples. If you think looking at other examples is a benefit or not. https://www.monxoops.fr/modules/xmtutorial/tutorial.php?tutorial_id=15 https://bootswatch.com/4/ https://github.com/thomaspark/bootswatch
  34. 1 point
    Thank you for keeping us updated 🙂 Best regards.
  35. 1 point
    Thanks for the update @Smile. All the best too all of you here. 😷
  36. 1 point
    As last resort I would try clearing the class_index.php file in cache folder. Of course you should return your modules folder to the prior state before that and try this. But I'm out of ideas. Probably check the error logs (highly doubt you will find something worth looking at) and somebody with more experience should log in and troubleshoot for you. If you have new hosting account in the meantime you can try and upload there the last working backup and try with php 7.0 or 7.1. If nothing else helps this will be a viable option to simply redirect your dns.
  37. 1 point
    What I meant with PHP is that module developers might not opt for using templates for some views. Sometimes it makes sense to generate html markup directly from PHP. For example, I've seen markdown interpreter module -- this allowed you to write your product description in markdown language, and the module converted it to html. For that, some php library was used, only customized to inject proper css classes to the output. Bootstrap css classes, mind you. Such module would not work properly on different tech stack, not without rewriting this php customization. With js -- a lot of modules use javascript to construct and replace DOM tree dynamically. In that case, bootstrap classes and building blocks are hardcoded inside javascript code. How hard it would be to rewrite this functionality to work properly with different css framework depends on how similar these frameworks are. For example, bootstrap's rows/columns abstraction are not always available.
  38. 1 point
    Almost all frontend modules will be affected, if the new theme will be based on different technology stack. I assume some of them will be easy to adjust -- simply rewrite the views and use scaffolding blocks from new framework. For some modules it will be much harder, as it might require rewriting parts of js and/or php. It's not reasonable to think that module authors will do this kind of modifications, at least not until the theme is well adopted by the community. Will this new group provide technical support for all these modules, and help with views/js adjustments? If not, I'm afraid the new theme would not be adopted by general audience. Technical people like @wakabayashi might have no problems adjusting those few modules they are using for the new theme, but ordinary merchants wouldn't know how to modify module templates. They want something that works out of the box. Just my 2 cents
  39. 1 point
    I have created a list of group members and added you to the list. Thank you.
  40. 1 point
    from my perspective it's simple: 1. point out where current themes suck and address those issues mobile experience shopping process ux cart... code duplication to achieve the same thing in different places 2. give it modern look with minimal set of features 3. reduce quantity of modules used to achieve that anything else should be in merchant hands or someone hired by him.
  41. 1 point
    That is good news. How do you wish to proceed? Are you happy to move forward with Orchid (in the current style) as a basis for the overall design, or would you and/or those interested like to make suggestions regarding the design and function?
  42. 1 point
    Hello everyone, I changed my product route in the SEO & URL page of the Back Office to a cleaner and shorter URL. {category:/}{id}-{rewrite}{-:ean13}.html is what it used to be, but I changed it to {category:/}{rewrite}.html Now I'm wondering if its posible to make a redirect in the .htaccess file to redirect the old product URLS to the new product URLS. And ofcourse I don't want to make a redirect for every single product manually. Does anyone have any clue on how to do this? Thanks in advance!
  43. 1 point
    First thoughts: Looking good - a great start 1) It does not interfere with the multiple feature module i have 2) works with Advanced search 4 and block layered navigation 3) I did not need to change the table indiex so guess the module I have had already done that 4) Works with store manager Suggestions, while I understand you do not want to 'copy' the multiple features module perhaps what it does will help tidy things up 1) Do you really need to indicate which features are allowed multiple features? If all were allowed then there would be no need for extra columns in the features table. So make it so all are multiple value then just not use when you don't need to for each individual feature 2) We have lots of features so finding them is tricky. Lot's of scroll and ctrl / select to choose. Not easy to see what is selected: The current module has a search feature (narrows down the list as you type and also shows the list of currently selected ones to the side 3) With lots of features the front looks not good Where as the current module sepearates the multiple features with a comma (Seperator symbol can be changed in module) rather than line break making it much easier to see 4) Possibly need a sort by position rather than numerical / alpabetical / index Overall a great start - well done. Now all we need is Block Layered Navigation to allow multiple selection and perhaps ranges (sliders) and all will be near perfect 😉
  44. 1 point
    for export there is the datakick module. But easy import from csv would be nice
  45. 1 point
    Sorry. Already found it by myself. There is a new (when comparing to the Smartblog module I used in PS) selection box that has to be ticked for each post: the available language box. If ticked, the posts show up!
  46. 1 point
    I dont believe, there is a quick solution. I remember how I did it: You generate all urls with the old structure. Copy them into Excel You generate all urls with the new structure. Copy them into Excel Now you generate in Excel a new column with the correct htacces/nginx redirect. Maybe somebody has a better solution. Of course you can only achieve it, with some SQL knowledge.
  47. 1 point
    I suspect that it can have many causes. If, for example, your links to social networks compare, do these links to the products still work, are the images still displayed? If the SEO data after the change to TB still exist, they may have to be re-entered? Probably there is also a problem with the template, that Google previously looked at this better than now. Have the page load times got worse? (possibly at the same time a server change) etc
  48. 1 point
    That is hardly anything that the normal TB user will ever understand.
  49. 1 point
    At least a choise of adding them or dont. Was it not like that long ago?
  50. 1 point
    Wouldn't be AWESOME to be able of running the installer without inserting demo data? :smile:
×
×
  • Create New...