Traumflug

Does it come with a configuration file Config.xml, uppercase? If yes, rename this to config.xml, lowercase. This issue was fixed for thirty bees v1.0.7, where both variants work.

But for debuging, instead of having ‘500 error’, where you want in your app (e.g. at the end of config\defines.inc.php), you can add : No file edits necessary. There's a switch in back office -> Advanced Preferences -> Performance: Debug Mode, which does the same.

Well, the updater downloads the exactly same file, from the same location. Seeing that there are issues with incomplete ZIP file extractions every now and then makes me scratch my head a bit. Hard to tackle.

Ui, da hat jemand herum gefummelt. Mal gucken, was passiert ist ...

Was the title changed to '[solved]' ? If so, what is/was the solution?

PDF templates are in pdf/ and ./themes/<theme>/pdf/. The latter override the former.

Are you clicking on 'Save'? These fields should certainly change. In case you want to look this up in the database, URL settings are in table tb_shop_url, there should be only one row (for monoshops).

Something I forgot: one also has to adjust URLs in back office -> Preferences -> SEO & URLs, panel Set Shop URLs.

Moving the shop is simple. Like none cd /var/www/html sudo mv shop oldshop sudo mv testshop shop But this also switches to the new database. If you want to use the old database with the thirty bees shop you should use the migration module: https://store.thirtybees.com/shop-modules/administration/prestashop-to-thirty-bees-migrator That's fairly quick, takes like 10 minutes. If you want to use the migrated database with your test shop, switch the database by editing config/settings.inc.php in the test shop.

Catching and reporting exceptions is always helpful, thank you for doing so. I don't have a solution handy, so let's track this: https://github.com/thirtybees/thirtybees/issues/625

So every thirty bees/PrestaShop site has some sort of pre-made theme with it? They all start with the default theme. Many shops install an additional theme then and use this. See back office -> Preferences -> Themes. And can I change small things in html/css instead of the whole site? Yes, of course. That's what many people do. Be aware of the cache when editing templates, see back office -> Advanced Preferences -> Performance. Keeping backups of the original files is also a good idea. A theme is code, so it occasionally receives bugfixes. Another recommendation is to duplicate the theme before modifying it. Which route to go depends on coding preferences.

"back office" is the usual term for what you probably mean with "admin control panel". "front office" is what shop visitors see. This news column gets assembled in controllers/admin/AdminDashboardController.php, method ajaxProcessGetBlogRss(). Related template is adminXXX/themes/default/template/controllers/dashboard/helpers/view/view.tpl

For additional themes, look up PrestaShop 1.6 themes. All of them should work.

I've deleted the duplicate topic.

Expect some 3 to 6 months of work to get a theme completely rewritten. community-theme-default is the starting point: https://github.com/thirtybees/community-theme-default One has to deal with all the Smarty templates, JavaScript variables and such stuff, of course. Due to the nature of a shop, writing static pages is no option.

Making the field blank won't restore the default. Is this what you try to do? Here are the default values: none Route to products {categories:/}{rewrite} Route to category {rewrite} Route to category which ... {categories:/}{rewrite}{/:selected_filters} Route to supplier {rewrite} Route to manufacturer {rewrite} Route to CMS page info/{categories:/}{rewrite} Route to CMS category info/{categories:/}{rewrite}

there is still a file in home/controllers/admin/AdminAddonsCatalogController.php Is it safe to delete it Yes, this file is no longer needed. There is a file consistency check in back office -> Advanced Preferences -> Configuration Information. Currently this lists missing and modified files. I took your post as an opportunity to make it list obsolete files as well. Will be in the v1.0.8 release. If you can't wait, replace controllers/admin/AdminInformationController.php and admin-dev/themes/default/template/controllers/information/helpers/view/view.tpl with recent copies from thirty bees' Github repository.

One step towards the answer is in file modules/wtcategoryfeature/wtcategoryfeature.php, line 68. Without having the module it's hard to find out what's going on. Did you contact the developer?

https://www.prestashop.com/en/previous-versions Excellent hint! Actually I found this page as well, but I didn't recognize that this "PrestaShop v1.7" field is a menu. With your hint I looked even closer, and now I see them as well :-) Problem solved, thank you!

thirty bees needs your help. In order to extend the PS -> thirty bees migration module to deal with earlier releases we'd need installation packages of these. On Github I can find only ones back to PS 1.6.1.6. I'm aware these earlier releases are no longer installable, because they refuse to finish the installation if they can't download translation packages. This doesn't matter. Important is the content of these packages. So, if you happen to have one (or more) of these ZIPs lying around, please send me a copy. PS 1.6.0, PS 1.5, perhaps even PS 1.4. My email address is [email protected]. Thank you very much!

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

It is recommended to upgrade jquery to version 3.0.0 or higher. ... which pretty much translates to "it is recommended to break all themes and front office modules". I had a look at this "vulnerability". It's exploitable only if the calling code has a bug as well.

This is what I deleted: public function getHrefLang($entity, $idItem, $languages, $idLangDefault) { [...] When removing code, one can remove code inside a function. If one remove the function its self, callers obviously fail.

This menu item is obviously provided by a module, thirty bees has no such item: Modules and Services is where one can get all modules, so I'm not sure whether this module provides something meaningful. Perhaps it simply became obsolete.

No need for making this optional. On the first try this directory doesn't exist. If it exists and some ZIPs are inside, they still get MD5-summed to make sure they're complete. Module tbupdater works this way since a year already.