Traumflug

All hints to this channel were removed already. No mentioning in the Readme ( = Github front page), no mentioning anywhere else. People appearing there either find it by googling or follow old links.

That's what I see everywhere. Fear, but no actual testing. There are no significant database changes.

So far my impression of this discussion is that some people are more into leeching free software rather than running and growing their own business. Not a single post along the lines of "I'd like to do this or that, but I can't, because thirty bees doesn't cut it". Why would future plans of thirty bees matter? One of the great features of thirty bees is its entire independence from any server. No dependency on a central server, no dependency on cloud services, nothing to renew regularly. Even if the thirtybees.com server had an extended outage, your shop installation would barely notice. And thirty bees is even a bit better in this regard than PS. A thirty bees installation won't ever go away. One can hardly imagine a more solid foundation for doing investments, for growing a long term business. Nevertheless, merchants have to grow their business them selfs. thirty bees won't do it for them.

Pardon. I thought I'm talking here to people with some knowledge in CSS. Here's a snapshot of this area with developer tools open, theme is Niara: As one can see in the lower half of the screenshot, there is a HTML input element of type 'checkbox'. The blue line marked in the list of HTML elements is also the element marked on the web page in the upper half. As one can see, the checkbox visible on the web page is not the HTML input, but a SPAN:before element. This technique is called 'overlay', AFAIK. The setup shown in the screenshot works, of course.

Theme exporter got a lot better with thirty bees 1.1.0, but it's not perfect yet. There are a few bits missing in the theme configuration. Easiest way to duplicate a theme is to duplicate its directory with all its content, then editing its config file to change 'directory' and 'name'. That done, the duplicated theme can get installed, it shows up in the list. And yes, installing themes on disk was broken before 1.1.0, they simply wouldn't show up in the list of installable themes.

Since thirty bees 1.1.0 that's expected. Before, themes using the same image name would overwrite each other's image types. Now each theme installs its own set, allowing distinct image types in distinct themes. The only unfortunate thing here is that the new mechanism uses the theme name for the distinction. Using the theme directory would have been the better choice. Two themes can share the same name, but not the same directory.

Shifting checkboxes out of the way is intentional. Their appearance is hard to change, so they get moved out of view and replaced with some icon in the visible area. Usually this works fine, unless CSS breaks.

Next step is to look into a few of these log entries to find out what the reason for this them is.

Thanks. This at least explains what the idea is.

What's the point of presenting yet another page a customer has to agree with? Checkout page is just showing the cart and a 'proceed' button, so it's not exactly obvious what value another page of that kind adds.

What exactly means "stopped working"? Do the requests for these files result in a 404? Are the <script> lines for some parts missing? Some malfunction? Software rarely stops working out of the blue, without any change to the code.

It's perfectly fine to use headings of a certain size multiple times. Else one could have only six headings on the entire page, after all, and no two of the same size. H1 is usually used only once, for the page title. All others as often as needed. "Short description" means short description. No headings at all, just one or two regular paragraphs. That said, there are no technical restrictions. Use what matches your design best.

Regarding a module one obviously has to ask the module developer/community.

Original templates are in mails/ in the file system root. These get overwritten by updates. Overrides, not overwritten by updates, go into mails/ in the theme root.

Is there a module involved? In my developer installation I see no 'Address Alias' field, there is apparently something generating this field in your installation. An obvious debugging step would be to uninstall this module. Another thing to look up is back office -> Localization -> Countries -> (click country). Parts for the formatted address can be changed for each country individually there.

It's Open Source. They can arrest developers, but not the code. For details on the raid, see https://www.zdnet.com/article/russian-police-raid-nginx-moscow-office/

This test uses a PayPal server and PayPal decided to shut it down. Hence it's no longer working. It's an optional test, though, not prohibiting an installation. Simply ignore the warning and proceed.

Four of these products would be 10 x 10 x 20 or 20 x 20 x 5 or 20 x 10 x 10 or ... Having so many possible combination explains why it's quite tricky to calculate "do they all fit?" Here we look at multiple items of the product only, often there are products of distinct size, which makes calculations even harder.

Software rarely changes its behavior out of the blue. What were the last steps you did before these images vanished? Some change in hosting, perhaps?

There is Module::getNotThemeRelatedModules() in AdminThemesController which intends to do something similar. Automatic detection is better than a handcrafted list, of course, still the new code might duplicate more existing code than necessary or allow to deprecate more of previous code. Regarding these additional warnings: a simple "Theme configuration was unclear about the following modules, please review whether these modules are (un)installed the way you need them: <X>, <Y>, <Z>, ...," would be sufficient for my taste, but I take we have quite distinct opinions about what to burden merchants with.

What you call 'usability' was pure luck. Themes not defining what they need relied on the previous theme doing the right thing. Even the default theme had three distinct flavors: the one in config/xml/themes/themenname.xml, the one in the theme's config.xml, installation when doing a fresh shop installation was yet another flavor. Highly unreliable behavior.

Here's an explanation of the issue and also some hints on how to fix it (on the thirty bees side, less as a merchant): https://stackoverflow.com/a/36146836

Nice idea, but probably not doable. I see no chance to detect whether a module isn't mentioned because the theme developer doesn't want it to be installed, or whether it isn't mentioned by sloppiness. Fixing themes is trivial, though. Install the theme, get its appearance right, then exporting it creates a correct config.xml.

Well, it should be redundant. A class preparing values for display shouldn't have to recalculate numbers. It should just display the ones existing in the database already. If reverting this commit makes a distinction, the revert likely just covers some other issue which puts these wrong numbers into the database first place. Another topic with a revert would be the loss of precision, because removed code was obviously not subject to the price rounding audit.

Core Updater checks validity of all thirty bees core files. Just click 'compare' without changing the version. This calculates all the distinctions between files on your disk and the official distribution. Files not matching get reported as in need of modification. Note, however, there are modules out there which do such infiltration as part of their operations, so one always sees changes.