Traumflug

Could you give a few more details? Did the module install? Does the migration process start (panels change, a text view appears) ? What are the last messages in this text log?

Note: merchants wanting to upgrade from 1.0.5 or earlier, please wait until this bug gets closed: https://github.com/thirtybees/thirtybees/issues/619 This likely happens this weekend. Those watching discussions here closely probably saw it already, the updater module got some usability enhancements. Which led to thirty bees Updater v1.3.3 While being there, the similarly written PrestaShop migration module received the same enhancements and also - Fixed display in medium sized windows. - Should work now on PHP 7.2 (with debugging disabled). - Clean up after being done (saves some 98 MiB of disk space). - Make double-migrations impossible by hiding most panels on thirty bees. Before one could actually start over after the migration happened already. This should also give better visual feedback about the success. 1-Click PrestaShop 1.6 to thirty bees migration v1.0.2 Last not least, migrations to thirty bees install now thirty bees 1.0.7, which solves yet another couple of bugs. That's a contribution of @datakick, thank you very much! thirty bees wishes you a glitchless shop running experience.

If I get it right the competitors are trying to soak the non-complient rivals against the goverment. That's not political, that's plain business. Some of these lawyers make a living from finding issues and sending report letters along with their invoice. In some cases it's also used to fight the competition. This even led to some funny court cases because lawyers tend to see abuse where no abuse actually happens, of course. Our Abmahnung eventually got famous enough to find its way into English Wikipedia: https://en.wikipedia.org/wiki/Abmahnung That said, it got better the recent years. Lawyer invoices are limited to € 100.- for the first letter and merchants learned what they have to watch out for. Still our government isn't brave enough to simply remove this silly idea of self-justice.

Does 1.0.7 base on the Prestashop 1.7 ? Nope. Still based on PS 1.6.1.11.

I can confirm this and filed an issue: https://github.com/thirtybees/thirtybees/issues/618 I can't see an error, though. Where do you see this?

The usual trick is to make a test migration (PS 1.4.6.2 -> PS 1.6.1.20 -> thirty bees 1.0.6 -> thirty bees 1.0.7), taking notes on how to do it. Once the quirks are worked out, one can put the old shop to maintenance mode and do it again. Having a step by step list, this can be done within an hour or two. The cart to cart service Lesley mentioned is this one: https://www.shopping-cart-migration.com/

"Versuch macht kluch!" Try it, and you'll find out.

Unzipping these files manually wouldn't work. Just already existing ZIP files get recognized if they have the correct MD5. To calculate MD5 on the command line, one can use md5sum <file>. If it still doesn't work it's a different issue. I just can't see a code path which wouldn't return a message, so I assumed it's a plain PHP script timeout. If you want to play with the code, processing happens in classes/AjaxProcessor.php. First round is ajaxProcessUpgradeNow(), then ajaxProcessTestDirs(), then ajaxProcessDownload() ... and so on.

@norwegian_rat said in Release 1.0.7 is there!: [Ajax / Server Error for action unzip] textStatus: “error " errorThrown:” " jqXHR: " " I had a look at the situation and the good news is, one can download these files manually. Placed in the correct directory, they'll get recognized instead of downloaded again. Here's a module version which should give more helpful hints, please give it a try: 01538431535240tbupdater-master.zip

Translations happen on Crowdin: https://crowdin.com/project/thirty-bees/pl# There's also module Crowdin in-context, find it in back office -> Modules & Services. Not sure how ell this works, though. Currently, translations from Crowdin get picked up on every release, which happens about once each month.

went back to Prestashop and switched off the graphgooglechart module and migrate to Thirtybees 1.06, no help. "switched off", like disabling it? This doesn't remove the module. Either use delete in the modules list in back office -> Modules. Or just move it aside, if you have shell access. Like none cd /home/campersnl1/domains/4campers.nl/public_html mkdir modules.off mv modules/graphgooglechart modules.off/ Good news about this: no need for another migration, this can be done after the migration.

Downloaded ZIPs go into admin/autoupgrade/download/. Extraction of these ZIPs goes into admin/autoupgrade/latest/Perhaps you can look these locations up, core ZIP should be 41686545 bytes (~40 MiB), extra ZIP should be 2817 bytes.

Are you using the community theme? If not, your theme might need adjustment. JavaScript coming with the Layered Navigation module happens to be a bit weak. Last time I tested it worked only with the JavaScript overrides from the community theme the way it should. These commits led to reasonably proper behavior: https://github.com/thirtybees/community-theme-default/commit/0aa28a7214db4f4c897e6efb4d2c830d9a199c9f https://github.com/thirtybees/community-theme-default/commit/c7c317123325aacf6096296d4b06b735adf8eb06 https://github.com/thirtybees/community-theme-default/commit/543bdc63290b3297287d0d343c39e84e212cce7c https://github.com/thirtybees/community-theme-default/commit/0217d3a5fdf68ea66bde571ca8acff66f9cb43fd

I have webshop on a server on the internet based on TB 1.04 and it is running fine. But when I move it to my localhost I suddenly get 500 errors on the product edit page. One has to adjust Preferences -> SEO &URLs, panel Set Shop URL after such a move.

Because of few bugs in tb core code, it was not possible to upgrade smarty to newer version Uhm, these bugs can get fixed. The more problematic area is compatibility with themes and modules, which is the actual reason why Smarty is still the four years old version. Plan is to shift focus from "compatibility with modules" to "compatibility with PHP" at the end of this year. With keeping module compatibility as much as possible, of course, but not at all costs.

I’m not sure if it’s possible to fix the underlying problem properly. It's certainly possible to fix it. But it's well possible all the exceptions handling code is then just as expensive as the code without full page cache. Time to create a set of performance measuring tests.

Filed an issue for this: https://github.com/thirtybees/thirtybees/issues/610

Just added the 1.0.7 update to the updater module. A test update went flawlessly.

I wish Zencart was this easy to upgrade Such a statement makes me curious why one would want Zencart while thirty bees exists.

The update module didn’t work for me, presumably due to shared hosting. That's currently expected, the necessary files aren't on api.thirtybees.com, yet. I hope I can get this done today.

doesn’t the $this->tplviewvars just get overriden, when you call parent::renderView()? That's apparently the case. Overridden by the class between the override and AdminController.

Glad to see you got it solved! public function initContent(){ parent::initContent(); } This should be a no-op. You can remove it entirely without a change in behavior. public function renderView() { parent::renderView(); $this->tpl_view_vars['dados_garantia'] = '654654654'; return AdminController::renderView(); } Here you call renderView() twice. This should be faster and give the same results: ``` public function renderView() { $this->tplviewvars['dados_garantia'] = '654654654'; return parent::renderView(); } ```

Say hello to thirty bees version 1.0.7. Release notes: - Full page cache should work now again (known bug in 1.0.6), thanks to @getdatakick. - Fixed a security flaw where customers could see shopping carts of other users when Full Page Cache was enabled. - Fixed date format for Arabic. - Fixed a potential time zone misalignment, which led to cron jobs not executing. Thanks to @doclucas and @getdatakick. - Fixed the config.xml vs. Config.xml problem on theme installation. - More PHP 7.2 compatibility. Hundreds of translated strings by @DaoKakao, @toplakd, @yanivmirel, @elund, @m.tomasovsky, @tRACE, @Andreaevangelina, @paintspec, @selwyn, @lutek, @null, @antagony1060, @Khan27, @AmirRzd to German, Russian, Slovenian, Polish, Danish, Hebrew, Czech, Spanish, Afrikaans, British English, Azerbaijani and Persian. Thanks to all of you! Notes to developers: - register() in config/smarty.config.inc.php changed its signature. We didn't find a module using it, but if your module does, use smartyRegisterFunktion() instead. Upgrade procedure using the release package: 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. Delete file cache/class_index.php Go to the config directory and edit the settings.inc.php file, update _TB_VERSION_ to 1.0.7. Now log in to your back office, the upgrade should be finished. You can turn caches back on. ~~That said, a package for the updater module is in the works, so it should appear there before too long.~~ The updater module should list the 1.0.7 release now. Enjoy!

Calling from the basement here ... Remember bugs like this https://forum.thirtybees.com/topic/2038/shopping-cart-menu-not-showing/7 ? api.thirtybees.com hosts a number of files crucial for updating core and modules. As these files get edited manually, it was all to easy for typos to stay undiscovered until merchants see updates failing. No longer. Over the last couple of days a validation script appeared. It searches through all the files for typical typos, files linked but not present and similar stuff. And that uncovered some 20 bugs, which are all fixed now. Also some 80% of the files there were found to be pointless and got removed. thirty bees wishes you a glitchless shop running experience.

... and yes, writing a validator inspecting this and similar files for such typos is exactly what's on my today's ToDo list :-)