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.


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Traumflug

  1. Well, I see 4 subcategories and 7 pages with 21 products each, so ~147 products. Except for one subcategory image missing there appears to be nothing wrong.
  2. Traumflug


    One can hire developers and a clear statement that the project currently named thirty bees isn't going to be abandoned. If you prefer another developer and don't care about the future of thirty bees it currently offers nothing for you, that simple 🙂
  3. Possible? Yes, of course. Editing the template is likely not sufficient, though. One also needs to move PHP and JS code to the other template and find a place to store this phone number without an address. Another option might be to move to a 3-step or 1-step checkout, depending on your taste. @toplakd has done great work in this area and maintains a thread explaining the work in this forum. That said, making a phone number mandatory is known to make customers reluctant. They want to buy something. Usually as anonymously as possible, to not risk joining a phone or other marketing campaign.
  4. Traumflug


    Great stuff is always "unfinished". Remember the first iPhone? Far behind what one could do with this hardware, still it started a new era of computing for everyone. Because these few things it did were implemented extremely well, everything else was postponed to later models. Merchant's Edition probably won't start a new era for everybody, still it follows this strategy. This forum is a working forum already, low urgency to duplicate it.
  5. Traumflug


    Yes, this is true. Many modules not PHP 7.3 compliant, though, logging the typical warnings behind the scenes next to working just fine on the public surface. Also usually fairly easy fixes.
  6. Traumflug


    Not sure how to answer this. Seen this 'Goodbye' thread, and perhaps some of these spontanously appearing chats? People talked about "plans", but actually meant their personal wishlist. A wishlist-festival! On top a couple of people who tried to switch a few simple knobs in order to pull developers in for their own favor. Working on tb means hearing complaints and unfulfillable wishes every day. "I want this!", "somebody should do that!", "why is this still not done!!1!!!" ... and all for free and yesterday, of course. Somewhere in the depths of Slack is a channel with lots of developers, most at least partially building their business on tb. Same experience there: "when will this be done?", "should do that!!", "why didn't do somebody XY already???" ... and zero contributions from them, not a single line of code. A quite daunting experience, one needs a thick skin to survive in such an environment. Ah. No hesitation to shell out money towards the old PS universe, but not even thinking about investing these bucks into the tb project. I better stay silent here. Perhaps the recent stirrup is a cleaning rain shower for the project. Because there are also these other merchants and developers. Those developers who don't complain, but show up with code. Those merchants who don't lament about free modules not working perfectly, but pay a developer to get these modules there. It's a joy and a satisfying experience to work with them and for them. Thanks to all of them, they move the project forward!
  7. Traumflug


    This third 'Disallow:' in the old version looks like broken code, as there's nothing noted on what to disallow. The other two directives disallow Google crawlers. Usually not what merchants want.
  8. In back office -> Preferences -> SEO & URLs, 'Base URI' should be set to this subfolder. Example from my development installation:
  9. Dann beschreibe doch, was diese "Schwierigkeiten" sind. Nur dann kann man sie auch beseitigen oder beschreiben, wie man sie beseitigt. Der Plan ist, diese Cookies früher oder später ganz zu entfernen. Ein Cookie, das auf einen leeren Warenkorb verweist, macht keinen Sinn. Einen leeren Warenkorb abzuspeichern macht auch keinen Sinn. Hat man das nicht mehr, braucht es auch kein Cookie-Opt-In mehr. Das ist allerdings ein eher komplexes Stück Arbeit, weil die Cookie-Geschichten tief in Core verankert sind. Will man Google-/Piwik-/wasauchimmer-Analytics oder auch schaltet die tb-eigenen Analysefunktionen ein, braucht man wohl einen Opt-In. Sowas speichert und analysiert ohne technische Notwendigkeit personalisierte Daten, das braucht Einverständnis.
  10. One can add any HTML code. The leftmost button ('Code') allows to edit raw HTML directly, all other buttons are mostly for convenience.
  11. I'd backup by other means and try again without making a backup. There's a switch for that under the button for proceeding. Removes the need to solve the problem 🙂 Solving the problem would require to catch this failed response in the browser's developer tools and if this still gives no good hints, to insert debugging code into the migration module until the problem is found. Obviously a time consuming process. BTW., one can scroll the log in this grey-ish box, latest messages are at the bottom.
  12. The address this tool tries to load would be much more interesting than the decoration of the 404 response.
  13. Ähm, in der Datenbank fummelt man besser nicht manuell herum. Dafür gibt es Klassen, die das machen, in dem Fall die Klasse Order. Die darin enthaltenen Produkte sind OrderDetails, die jeweils dieser Order zugeordnet sind. Und dann gibt es da natürlich noch eine ganze Menge Anhängsel, von der verwendeten Währung bis zu einem Flag, ob es sich um ein Geschenk handelt.
  14. Traumflug

    Free UPS module

    See https://www.merchantsedition.com/#portfolio, click on Custom Modules. Not that it'd be easy to crowdfund a module needed by just three or four merchants, still doable, of course.
  15. Scheint nicht besonders dringend zu sein, wenn niemand eine Meinung dazu hat, wie so ein Modul funktionieren soll 🙂
  16. Yes it would, and for tb developers that's a hard to solve problem. In the PrestaShop days the option seen most often was to simply not update. tb got quite a bit better on this, one can update core software without updating the theme. Three ways to do it properly until thirty bees found a better way: - Carefully maintain a log of your changes in order to be able to re-apply them after an update. Having backup files right next to the original is fine. - Use Git or another version control system to keep that log and apply/unapply it as needed. - Use back office -> Preferences -> Custom Code. That's a bit harder, because JS and CSS added there gets applied to all shop pages. One has to figure a unique CSS path for that specific item one wants to change. But it's update-safe.
  17. A first step would be to look up whether these images exist on the server. Product images are stored in img/p/, then folders for the image number. One can find the image path in back office -> Catalog -> Products -> (click product) -> Images, hover over the image to see its URL. Images can be corrupted, zero size, missing, whatever.
  18. These recent irritations around the project currently named thirty bees accelerated my efforts to come up with a solid and reliable ground to connect developers with merchants and merchants with developers. Code written and features of the software were and are great, many merchants do their best to help others, just as many developers. This deserves a liberation from business and investor games. Say hello to Merchant's Edition Merchant's Edition has the goal to move the idea of open source into the business area. It's open to any developer working on the core software and basic modules. Their share grows not by the amount of money they provide, but by the work they put in. They can connect directly to merchants and vice versa. Merchant's Edition helps to connect them together. Next step: provide a chat for both. Those knowing me also know I prefer to do things right over rushing into something 80%. Look at how blazing fast the already provided site is. During development I learned a lot on how to make web pages faster, much of which can eventually be applied to shops running thirty bees as well. Published now already, to show that things around thirty bees are moving forward. Chat is then expected to be the same: fast and secure. Probably based on Matrix and Riot. You as a shop operator can get support right now. These nagging warnings all the time? We'll fix them. Need an extra feature? We'll write it. No time for technical maintenance and updates? We'll do it. Done by those who know the software best, from the ground up. Your contact: contact@merchantsedition.com
  19. Thumbnails regeneration never times out, it just takes time. This is one of the things where thirty bees removed one of the well known PS pains. For investigation on what's going on, looking at the URL of one or two images and comparing it with images actually on disk is a good start. One can also turn off Pretty URLs to see these URLs directly, without Apache changing it on the fly.
  20. Zu solch einem Modul habe ich mir immer mal wieder sporadisch Gedanken gemacht. Mir ist jedoch bislang nicht klar, wie da eine sinnvolle Strategie aussehen könnte. Eine Möglichkeit ist sicherlich, ähnlich einer normalen Bezahlung eine sich wiederholende Bezahlung bei einem Bezahldienst auszulösen. Da wäre der Shop dann nach der ersten Bestellung aussen vor. Und das geht natürlich nur mit Bezahldiensten, die solch eine Funktion haben. Eine andere Möglichkeit wäre, per Cron-Skript jeden Monat / jedes Quartal / jedes Jahr automatisch eine reguläre Bestellung im Shop auszulösen. Eine Produktart mit Verfallsdatum, das durch weitere Zahlungen verlängert werden kann, stelle ich mir dagegen eher aufwändig vor. Da bräuchte es dann Webseiten mit einer Übersicht für den Kunden, wie der Status solcher Dauer-Bestellungen ist. Kündigungsmöglichkeit, "Kontostand", Zuordnung unverlangt eingehender Zahlungen und dergleichen mehr. Wenn jemand eine gute Lösung kennt, gerne auch in einer anderen E-Commerce-Software: ich bin ganz Ohr.
  21. thirty bees also has it's own log files. See `log/` in the web root. There it collects short versions of what should also appear in the browser. Yet another source for error messages is back office -> Advanced Parameters -> Logs. One can filter by severity there.
  22. I'd try to set product minimum quantity to 1, not zero. This is back office -> catalog -> products -> (click product) -> quantities -> tab 'Availability settings'. Or back office -> catalog -> products -> (click product) -> combinations -> (click edit on a combination). If it's already set to 1 there, it's a module bug.
  23. Dropbox, radiobox and colors are attributes defined by the merchant. Customers can select, but not change them. What you probably want is a customization. There customers can enter something and order the product with this something. For example, text or photos on a t-shirt printing service. Adding customizations is a two-step process. Enter the number of fields first, then save, then define how these fields should look, then save again. Needs a bit experimenting.
  24. Yes, it should be this way. Actually the selection is generated in `Product::getNewProducts()` in classes/Product.php. To keep core code unchanged, one could request a larger number there, then do a random selection in the module.
  • Create New...