Traumflug

Is there perhaps another category or a product with the same name? This would result in the same URL. There's a module 'Duplicate URLs', which detects such issues.

Does it help to ignore the message? Older module and core code used to test for TLS 1.2 support in a way which no longer works due to the used service vanishing. It's safe to ignore the message if TLS 1.2 is actually supported.

... where 'latest version' means Bleeding Edge 1.1.x. thirty bees currently receives bug fixes only, so Bleeding Edge is more stable than Stable.

'Bottom left' = category 'Line and Braid'? Works just fine here, a click loads the category page for Line and Braid products.

There's also Merchant's Edition, which makes sure this software won't die, no matter which negotiation games are happening in the background.

class_index.php gets generated automatically. Actually it's a good idea to delete it if trouble about missing classes comes up.

The real life scenario is that one can fix all the bugs generating messages. Did this recently with a shop with no less than 103 modules of all flavors installed. Some bugs were harmless, others caused parts of the software working the wrong way.

Messages get written for a reason: to allow fixing the issues behind them. And one should really do this. Out of the box, a thirty bees installation doesn't even create a log file.

Well, the easiest way to migrate would have been to use the migration module which keeps all the settings. Glad to see you managed it anyways.

Likely a hoax. A professional (which he claims to be, "my customer") would try an installation elsewhere and look at the result before repeating it on a customer's host. And if she had actually used thirty bees, he'd know that there is no "admin module". Regarding "module" I get the impression that some other shop software calls everything "module" and needs a custom written module for something as simple as selling printed t-shirts. Apparently an e-commerce software which leaves wishes open, as these guys start to appear here.

Look at the very bottom of your screenshot. There's JavaScript reporting some syntax error. Fix that first, before looking for other issues.

Recently several merchants had trouble embedding videos in their shops. For example in product descriptions or in blog posts. It's true, there are pitfalls one can trip over. One has to find the right HTML code in the video portal and copy that into the right place in thirty bees back office. Enjoy!

Everything should be a straightforward process :-) As one can see easily in this thread, 5 merchants have at least 6 opinions on what that exactly means. Which in turn requires more knobs and buttons, making the process less straightforward. That said, image handling in thirty bees could certainly advance with an overhaul of the image handling system. To make formats other than standard resolution JPEG first class citizens as well (PNG, high resolution, WebP, mixes of that). To keep original images rather than processing them to the same size. To allow non-square images. Likely a long process, and one easily breaking themes. Forming the future is hard work, still worthwhile work!

To go with high quality, one has to start with PNG. This option to always use PNG, even if uploaded as JPEG, isn't helpful. It just raises file size. PNG is nice, excellent for graphics-type images. But enormous file sizes for typical photographs. Not sure whether 5 MiB and bigger images are really helpful.

After uploading images one can replace them with any version one wants. Only missing images will be generated automatically. That's obviously some extra work, but may be worth it if image quality is important.

Just ignore it and proceed. This test uses a PayPal service which used to work fine, but was removed from public a few month ago.

One can hook any module displaying something to the left column, not just a specific one. Home page of the Niara theme is without left or right column, though.

For finding this out, processing one image is sufficient 🙂 One can interrupt the processing by clicking on these blue buttons in the image regeneration panel.

There's a switch for this in back office -> menu -> Advanced Parameters -> Performance, called 'Disable non thirty bees modules'. That said, there are like-named modules by thirty bees, so it might well be modules "enhanced" by some theme developer.

Forget the decoration, neither GitKraken nor PHPstorm are necessary. To get started, copy one of the themes: cd themes cp -rp community-theme-default my-new-theme Which one doesn't matter. Both are technically almost the same, just (S)CSS is quite distinct. Then edit config.xml inside the new theme with your favorite code editor (vi, nano, geany, gedit, sublime, whatever): cd my-new-theme geany config.xml Edit fields name and directory in the upper few lines. Each appears twice. Name is arbitrary, directory should match the actual directory. Save the file. Why these edits are necessary? Well, PrestaShop decided it this way 10 years ago and changing this would easily break existing themes. At this point you can install the theme already. It'll look like the one you copied, but it's the new one. Then you can build the theme: npm install npm run compile-css npm run format-js npm run copy-index npm run clean-up First command is needed only once, second command is the essential one, the other ones are tidying up code a bit. As you didn't change anything yet, a new build shouldn't change anything. Now you're ready for editing the theme. Template file (.tpl) file edits take effect immediately. JavaScript files as well. Just reload the page in your browser and the change is there. Regaring CSS: don't edit .css files, but the .scss ones. After each edit, rebuild the theme, then reload the page in the browser. At this point you're in the middle of development already. Cheers!

PM sent.

Fractional quantities are not supported, AFAIK. But one can sell single centimeters, then let the customer adding such centimeters using the up/down button. Tweaks, like starting with 100 cm or adding 10 cm per click or displaying 100 cm as 1.0 m are a matter of JavaScript in the theme (product page, checkout page). This leaves just one issue open: a customer wanting two lengths in one order. E.g. a piece with 150 cm as well as a piece with 200 cm. Shop logic would join this to one piece of 350 cm. Other than this it should work well.

Bleeding Edge as of when? This version changes with every commit pushed to the Github repository. Which means, one should update every now and then.

There were 11 bugfix commits over the last month. Not as much as there could be, but also more than nothing.

Try a look into product-list-item.tpl. This template gets included by a number of other templates showing product lists.