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.

Traumflug

Administrators
  • Content Count

    1,322
  • Joined

  • Last visited

  • Days Won

    35

Everything posted by Traumflug

  1. For transparency, add transparency to the color values (note the 8-digit numbers instead of the default 6-digit ones): Result (with probably too much transparency):
  2. It's "EU Cookie Consent", right in the backoffice list of modules:
  3. No, not sure. I mostly know this from seeing _PS_MODE_DEMO_ in many code files.
  4. Trick #412: Add (please choose) as the first attribute and set available quantity with this attribute to zero. This way a customer can't order the default combination by accident. Adding such a first choice is obviously a worthwhile feature request: https://thirtybees.com/feature-request/
  5. Annoy the customer who complains and say it does not work. If there's no 'add to cart' button, there's also nothing not working.
  6. How do I know if the images were processed by ImageMagick or not? Regenerating thumbnails processes them. If you want to make sure they were actually processed by ImageMagick and not the simpler way, turn off IM first, regenerate thumbnails, note the exact size of a few images, then regenerate with IM on and compare with the previous sizes. JPEGs generated with different methods are always of slightly different sizes.
  7. If these things require no payment I'd replace the "add to cart" button on the product page with the code snippet wakabayashi suggested. Requires some theme modifications (product.tpl), of course. I don't see a need to tweak FrontController. Virtual products can have files associated already, just the link has to move from the backyard to the product page. All the ordering machinery is never used then. @wakabayashi is it technically possible to use smarty variables in html? Yes, of course. That's the whole point of Smarty. If you mean "inside HTML tags", like <a href="{$product.download_link}" ..., then also yes.
  8. There's a demo mode, accessible on the dashboard page in the upper right corner. AFAIK this disables stuff like completing a purchase.
  9. @Traumflug is working on 1.7 theme compability. Don't expect anything soon. It's a complicated matter, especially the set of Smarty variables offered to templates. This set changed by some 90% between 1.6 and 1.7 and offering both depending on the theme version is a rather intrusive change.
  10. :thumbsuptone4: for doing such a video! :thumbsuptone4: for showing how to clone a shop and for working on that clone! :thumbsup_tone4: for the module doing the migration so seamlessly! To those who have a clone already or want to try on a test installation: start at 10:20 in the video.
  11. Traumflug

    Split Payments

    That said, as a good merchant I should have offered you to implement all four features, take the cash for all of them and implement only the one needed thing.
  12. Traumflug

    Split Payments

    Right. So you don't want an entire module, but enhance the existing module to allow subscriptions as well. Split payments are (hopefully) transparent to the user, so no module change required. Invoices can be done by 30bz, so no change required either. Entirely different perspective for a developer.
  13. Traumflug

    Split Payments

    @Havouza now I only need a programmer to make the module https://docs.payza.com/reference#prestashop
  14. But i don’t understand the logic to deleted and recreated. the reason why. It's the simplest way to do an update. Such updates happen rarely, so there's no need for performance optimization. For Tags I’ve found another logic to develop the solution Code, please! :relaxed: Ideally as a pull request, but patches uploaded here are also welcome.
  15. No need to feel sorry, multiple reports put more emphasis on the matter and confirm the first report. In the Ubuntu tracker, bugs with duplicates even get bonus points.
  16. I create a standard “tb in a box”, back it up, and restore it in another domain. Simsalabim, working Yes, absolutely!
  17. People usually write code which fits their needs. They have no magic crystal ball to find out which other uses one could come up with in the future. The code in question was written in 7/2015 (reformatted later). Now it's 2017 and you found such an additional use, so this code apparently needs a review. If you can come up with better code, not breaking previous usage, I'm pretty sure it can be accepted for thirty bees 1.1.0.
  18. In multistore this applies to the first shop. All defined domains load their related shop, all other domains load the first shop. Maybe this feature makes using multistore obsolete in some cases, because defining multiple URLs just to make one shop accessible from multiple domains is no longer necessary.
  19. P.S.: another use case is when copying a shop from one domain to another. No need to adjust shop URLs set to automatic, then.
  20. Doing my first steps with PrestaShop worked pretty well. Went to http://localhost/, ran the installer, eventually started editing the theme. Ah, right, mobile users! Picked the phone to see how it looks there, connected to my desktop and ... u-oh, "This page can't be opened, because Safari can't find the server" Bummer. What happened? Well, at installation time, domain name was localhost. Installer picked this up. Shop software insists on this domain and redirects to it, even if the shop is accessed from another address. Accordingly, http://mydesktop.local gets redirected to http://localhost, which is an entirely different host on the phone, of course. A long googling session later I learned how to fix this misalignment, still I couldn't resist to teach this shop software proper manners. Domain *automatic* was born. This is how it looks in Backoffice -> Preferences -> SEO & URLs: Having it enabled means that thirty bees will no longer try to redirect traffic just because the domain is "wrong". It'll just proceed. It's turned off and works as before when an actual domain name is entered in these fields. What do you think about this feature? Useful? Might it break other use cases? Thanks for your comments. Related Github pull request: https://github.com/thirtybees/thirtybees/pull/250, it'll go into thirty bees 1.1.0, then.
  21. Is PageCache in this class index? The section should look like this: php 'PageCache' => array ( 'path' => '', 'type' => 'class', 'override' => false, ), 'PageCacheCore' => array ( 'path' => 'classes/PageCache.php', 'type' => 'class', 'override' => false, ),
  22. Excellent! Let's assume for now these error messages are a result of you upgrading the database in this unusual way :-)
  23. PageCache::flush() exists: https://github.com/thirtybees/thirtybees/blob/1.0.x/classes/PageCache.php#L173 Are there overrides involved? cache/class_index.php deleted (will be re-built automatically) ?
  24. Line 286 in AjaxProcessor.php is this: php $this->nextQuickInfo[] = sprintf($this->l('Files will be saved to %s and %s'), $this->getCoreFilePath()); Two %s and just one argument indeed look like a bug.
  25. Sounds pretty similar to this one: https://forum.thirtybees.com/topic/340/upgrade-error-500
×
×
  • Create New...