Traumflug

The system says: This functionality has been disabled. Typical message when running in demo mode. It's defined by _PS_MODE_DEMO_ in config/defines.inc.php.

Here's a commit which claims the exact opposite: https://github.com/thirtybees/thirtybees/commit/48521e43c18ba4da2071655b8aa5b5191ab73954 :-)

A must for me is 1 page checkout and I see 1 is being offered soon Actually, there's one coming with the default theme. Go to back office -> Preferences -> Orders and find field Order process type. Right the first field, a submenu. There one can select the type of checkout.

You can limit carriers to weight ranges. As emails are of zero weight, customers can choose the free delivery service for emails, only. Not sure if this hint goes into the right direction. Having a carrier limited to vouchers would most likely need some custom code. P.S.: if customers choose another product together with a zero-weight email, they're limited to the non-free delivery service.

This should work out of the box. However, when testing on 1.0.6 and using default theme with the multiple page checkout I can't see an issue. I'm just not sure what the "following overview page" should be. The page after carrier selection is the one asking for the payment method, no carrier selection visible. One can see the carrier selection only by the shipping price given.

I meant proud because you have people that take care of the project. Can't see any care taken in this thread. Just blaming, without any work towards a solution. Remember @alwayspaws ? She wrote a nice little welcome message to everybody joining this forum. The helped translating from the developer to the merchant perspective, for getting shops into production. AFAIK she even wrote outside this forum to tell the world about how helpful thirty bees is. This is taking care.

You should be proud of having people in the community that [...] tells you what you can improve. Proud? Certainly not. Because we know (almost) all of this already. I love the community if I wake up in the morning and see stuff like this: https://github.com/thirtybees/thirtybees/pull/573 https://github.com/thirtybees/thirtybees/issues/551#issuecomment-414070564 https://github.com/thirtybees/community-theme-default/issues/61 This actually helps.

community-theme-default just received the fix provided by @yaniv14, so it'll go into the next release. Thank you very much! P.S.: or was the fix provided by @datakick ? The commit message reads Petr Hučík, thanks go to this person :-)

Did you notice the quick access menu in the top header of back office? That's perhaps not entirely what you want, but comes closer. One problem with such a quick access button is that there's at least a dozen settings regarding caching. And I'd love to see this large set reduced. For example, there's Never recompile template files vs. Recompile templates if the files have been updated. Is the latter actually slower? If not, the former option can get removed. Nobody wants old templates in use.

to $this->keys = json_decode(file_get_contents($keysFilename), true); Dang. I mean I've had a look at every single usage of json_decode() to find exactly such issues. Looks like I missed a spot. Thanks for the help!

Hmm. @yaniv14 can't reproduce this on 1.0.6, see comment on the Github issue. Which leads to the question: what is different between your installation and Yanivs? Any additional modules? A custom theme? Does it happen with new products as well (it might be result of something stored in the wrong place in the database)?

Blank page usually means a fundamental PHP problem, like a syntax error. There should be messages in the Apache/NginX/PHP-FPM log. Location of this log depends on your hosting, it's not the one in logs/ inside the thirty bees installation.

https://github.com/thirtybees/thirtybees/issues/574

This version is still killing full page caching. So, it is just not much of use. Many other ecommerce solutions don't even try to have such a feature. A shop works just fine without it.

One can go from 1.0.3 to 1.0.6 directly, but has to do these extra steps in the database and module removal described in the 1.0.4 upgrade instructions: https://thirtybees.com/blog/version-1-0-4-has-been-released/

PHP Warning: readfile(/homepages/31/d658016058/htdocs/img/favicon_1.ico) A request for favicon_1.ico means you have Friendly URLs turned on ('1' is the shop ID). If you can, it might help to go to back office -> Preferences -> SEO & URLs and turn this off. Then save this setting, turn it back on, save a second time. This will reset some stuff around this setting, e.g. refresh the .htaccess file. There's also a chance your hosting doesn't come with the mod_rewrite Apache module. In this case, Friendly URLs has to be kept off.

It shows “This page isn’t working.” Can you make a screenshot, please? I'm not aware of such an error message being implemented in thirty bees.

what if I update all the files to 1.[0.]6 and still remove the for-mentioned files and replace Sounds like a good idea. At least if finding the problem fails.

One thing to try is to turn off non-thirtybees modules. There are two switches on back office -> Advanced Parameters -> Performance to do this, Disable non thirty bees modules and Disable all overrides. If the shop works with these two switches turned on, you can keep history fairly easy: Get the 1.0.6 release package. Remove folders modules and overrides entirely and replace them with the ones coming with the release. Install required third party modules again.

Which error is it now when turning on debug mode? Can't be the same as before. One can have debug mode turned on all the time until such stuff is sorted. Worst case customers see error messages.

Then you have to go to the file system and remove it there. It's the modules/googleshopping/ folder. Remove it entirely, but keep a backup somewhere outside the shop. And then cross fingers this module didn't install overrides. Getting rid of them without having the module is pretty complicated.

Find it in the list in back office -> Modules & Services and select Delete from the menu. Not just Disable or Uninstall.

Obviously a problem of this googleshopping module. Ignoring that these security relevant classes are probably pretty dated, you can try to rename these constructor methods to just __construct(... (two underscores in front). What is the constructor method? Well, the method (function) with the same name as the class. If the class is called RSA, then its old-style constructor is function RSA(.... Also identifiable by the line number given in the deprecation message.

You likely noticed discussions already, now it has happened. Say hello to thirty bees version 1.0.6. Release notes: Fixed a serious bug which prohibited checkout in some cases. Refactored the translations packing machinery, Crowdin translations for front and back office are back in business. This also uncovered 8 additional languages. Added equipment for module vatnumber v2.1.0. In case you don't use the community default theme, see release notes there on how to get this for your theme as well. Documentation for PHP vendor packages no longer go into the release package (55 files less). Those 11 modules not getting installed by default no longer go into the release package (176 files less, tiny performance improvement). One can still install them by clicking 'Install', of course. Fixed various bugs, of course. Upgrade procedure is the same as with the v1.0.4 release, but no database upgrade and no messing with modules required: Download the ZIP package. Unpack the package. DELETE the install directory from what was unpacked. RENAME the admin directory to the same name as your current admin directory. Perform a FULL BACKUP on your site. TURN OFF all caches on your shop or or set it to force compile. Upload the files that are remaining from the zip archive to your site. Go to the config directory and edit the settings.inc.php file, update _TB_VERSION_ to 1.0.6. Now log in to your back office, the upgrade should be finished. You can turn caches back on. Enjoy!

I tried it on my shop. It broke most of the major modules we use. Excellent! Well, I mean 'excellent' in the way that we have some real evidence now. Bugs visible and reproducible can get fixed. Let's start with this: https://github.com/thirtybees/thirtybees/issues/571 Bonus points for more step by step instructions on how to reproduce and screenshots. With some luck we can fix all of them even before rolling out Smarty 3.1.32.