Traumflug

Here's a shop running on MariaDB: https://store.thirtybees.com. Apparently not a problem. Regarding languages you could try to not delete, but just disable US-English.

Maybe on Windows OS? This OS is a known source of trouble, because it uses non-standard directory separators. And also not supported by the thirty bees team, we just accept patches. In case it comforts you a bit, British English is translated by just 5%, so you'd get 95% US-English anyways: https://crowdin.com/project/thirty-bees/en-GB# Strings for these menu entries are in file tabs on Crowdin.

After I updated the contact form still can be send w/o confirming the captcha as in 1.0.2. Is actually an email sent or does the form simply re-appear? Buttons being clickable without solving the Captcha is expected, but no email should get sent. Instead, the page should re-appear, together with an error message:

Some files have to be fixed manually on your side in order to be pushed to our BOs? You can test this manually. Direct your browser to http://api.thirtybees.com/updates/modules/all.json . This downloads the JSON which a Check for update on the module page downloads as well. Search for 'nocaptcha', a couple of lines later all known versions appear. If it works now and didn't before, it might be a glitch caused by the server move. The new server got the new version a couple of hours later.

The new upgrader will be just as fast with a backup as without one. Magic? Nope. KISS.

As much as I try, I can't reproduce this. This brother elaborating a bit on what he did would help a lot.

Weird. Let's track this: https://github.com/thirtybees/thirtybees/issues/591

I still encounter the same problem (just a few minutes ago) Thanks for the report. Indeed I found another 8 instances.

Recently a paying customer asked me to fix reCAPTCHA in his shop. After entering keys, the captcha on the configuration page would simply disappear. Looking into the source code I found many fixes, but no releases. So I catched up on this and made nocaptcharecaptcha v1.1.0 It should also appear as upgradable in your back office. In my developer installation this module works now fine. Except for a small graphics glitch (missing icons) in these message bubbles leading through the installation process. That's already fixed and will go into the next release. Looking at various issue reports in this forum I'd love to hear how well this module works for you!

Big thank you for this list, @musicmaster!

Come on, PHP wants to be a beginners language :-) In this case it's JavaScript, though. A click on the picture should change the menu. As long as the menu is set correctly when the user clicks Add to cart, shop software will pick it up correctly. No additional PHP required. If it's just three colors you might get away with per-color product images. Each combination can have a distinct cover image (tab Combinations on the product editing page) and changing the menu will change the main image to this cover image.

If you copy the project to your Modules directory it immediately crashes your TB. You don’t even need to install it. Such behavior puzzled me in the beginnings as well. It's true, the main module file gets loaded by module handling code, even with the module uninstalled. In this case one has to run a ./build.sh to get the missing pieces. Which in turn requires composer and npm to be installed on the operating system. P.S.: Alternative is to move the module aside, of course. That's why I have a folder modules.off right next to folder modules. Moving module source code into another folder is sufficient to make the module harmless.

Recently seen something like this when browsing to one of the thirty bees pages? That's the unfortunate result of a vulnerability in one of the WordPress modules, which thirty bees had in use on the thirtybees.com site. Good news on this one: module removed, distributed virii all removed as well. And this was quite a number, some scripting found like 6000(!) instances all over the place, across almost all thirty bees hosts. Infected files were PHP, HTML and CSS ones. On top of this, chances are good for thirty bees moving to a new server in a couple of days. This will also introduce user privileges separation between each of the virtual hosts, then, prohibiting infection from one host to another.

Can anyone help me in this situation? Yes. Install thirty bees. Even if PrestaShop is still a bit more popular, trying to fix an abandoned version is pointless. Like many others do: https://trends.builtwith.com/shop/thirty-bees/Market-Share

php AdminController::__construct(); Calling non-static methods statically is deprecated, see: http://php.net/manual/en/language.oop5.static.php Also not sure whether it actually does something. Probably a no-op.

Well done, @spacewalkingninja ! Do I understand correctly that you edited database table 'configuration' with a database editor and wrote a NULL into the row for PSADVANCEDPAYMENT_API ? I had a look on whether we could enhance the PHP code a bit to avoid disappointments like the one you experienced, but found only writings of PHP values *true* and *false*. Which should result in a string "1"/"0" in the database.

There is no 'PSTB1.6'. Here we talk about thirty bees. Current version is 1.0.6. ... and usually people have their own problems and work on that. If you want somebody else to take care of your shop, see https://store.thirtybees.com/services

It’s always best to use overrides when possible. Best is to get bug fixes into core. Which requires a fairly clear description of what the actual problem is, together with the changed files in an issue report.

You have to remember those online retail giants are also working internationally and conform with international laws as well. They don't. The evaluation done by me above was made while being connected from Germany and the interface doesn't comply with our local laws. Such shops target perhaps 70% of the available market and just ignore the other 30%, in the hope to get more business out of the 70%. Quite possibly this works out, still it leaves 30% in the rain. Which opens business opportunities for competitors. thirty bees isn't a shop solution for just end consumer toys, it's a solution for any kind of business. Each kind of business has a different 70% set, so it can't predict on which set of consumers should be targeted. Only merchants can do this and finding this set is a major part of their business operations. There's another reason why offering a fairly feature complete rather than a reduced default installation is a good idea. There's a lot of competition, so merchants searching for software likely have a checklist about which features they need. Then they search around and look up whether their checklist is met. If there's something missing they move on to the next. It's very unlikely they spend a couple of days to learn about how to add this or that must-have feature for each of the software candidates. Third reason is, removing widgets is much easier than adding ones. If thirty bees wants to improve, it could show better how it can get adjusted to particular merchant needs. That's probably the reason why add-on themes are so popular. They don't add shop features, but they come with an interface allowing to change appearance without touching code. Sometimes at a fairly high cost of performance, still merchants like it. ... and please don't take this posting as an official statement. It's one opinion among many.

With my moderator hat on: Had to lock this topic and remove the last couple of postings. Too far off topic and quite a bit heated. If there are issues left on the actual topic, please try again with a new thread.

You’re nitpicking. That's probably my second name :-) That said, if it's just graphics, what's the problem, then? Juggle a bit with CSS and schwuppdiwupp, these fields in the default theme get rounded corners, shadows, whatever one can imagine. If there are too many fields, here's a little secret: Go to back office -> Localization -> Countries and click on a country. On the lower half of this page is an editor "Address format". There one can add and remove address fields. Remove them there and they're gone from the dialog presented to the customer.

Best design of a checkout goes to chewy.com for sure. No guest checkout and "best design" doesn't really match. P.S.: also: Can't enter a company name. Can't enter a VAT number. Can't enter a different name for the shipping address. Only one payment method. No carrier selection at all. While it's a nice looking GUI, pretty crippled in functionality. Not sure what to learn from there other than the evergreen "get nicer graphics".

As we just discussed in the chat, modifying the code as explained does work. It works for some themes. Not so for others. If it was just a matter of uppercasing this c, I had changed it already.

While researching for the new updater module I found it'd be better to document in public rather than taking personal notes. Result of this effort: yet another wiki, Traumflug's A couple of fairly complete pages appeared already, e.g. Back Office Menu Entries Using Helper For Options Helper Field 'text' Do Web Requests With Guzzle Also many many red links (linked, but missing pages) :-) Goal is to document coding techniques in HowTo style. Simple, executable examples. Pictures on how the result looks. A style inspired by Mozilla's really great guide on how to write Firefox extensions. Feel invited to correct mistakes, add sections or even to write entire pages. Creating an account is free and unrestricted. It's DokuWiki, with a Syntax similar to that of Wikipedia.

Make sure you didn't remove this by accident, it directly follows the code section you posted above: php if (!defined('_PS_MODE_DEMO_')) { define('_PS_MODE_DEMO_', false); } Having _PS_MODE_DEMO_ undefined means that PHP takes this sequence of characters as a string and a non-empty string other than '0' evaluates to true.