datakick

@cprats I don't see anything. Is this a result of a product save operation?

This warning has nothing to do with the slowness. You have probably enabled debug mode, not profiling. Enable profiling, and then look at the bottom of the page for performance statistics That should give you the basic idea what's slow in your system

@schmuck-checker MEHR category contains subcategories. Please ensure that Display products from subcategories is enabled Or simply associate your products directly with this category

Could you share url of your shop?

You guys know that thirtybees implements canonical url tags by default, right? So why bother doing all this stuff? The only reason behind this rel="nofollow" suggestion is to get rid of duplicate content warnings (or is there any other reason?). But this is very stupid method to achieve this task, if you ask me. You need to fix all links on your page. If you miss just one, you will get this duplicate warning. Also, if any third party website links to your site using dynamic parameters, you'll get duplicate warnings as well -- you will have to manually block these third party links in your search console. It's a lost battle... Canonical url meta tags, on the other hand, solve this problem elegantly and permanently. When google tries to index url with dynamical parameters, this meta tag tells him that he should index is under different / canonical url.

go to Preferences > General and enable Multistore. Don't worry, you can disable it later go to Advanced Parameters > Multistore select shop and edit it: change shop name go to Preferences > Themes and upload your logo Result: logo will now contain name of your shop, changed in step 4 Now, you can disable multistore again. Unfortunately I did not find any way to edit store name without enabling this feature

Because this module is disabled on mobiles by default :) But it's pretty easy to enable it:

When you upload logo, the file is renamed using shop name: https://github.com/thirtybees/thirtybees/blob/1e34bdafba75c0a60e9f9bfd3ee65498b5b1ecf6/controllers/admin/AdminThemesController.php#L2704 You can either change the shop name, or change the code

@movieseals said in [Free Module]Revws - Product Reviews: I was wondering if it would be possible to make rating the shipping as optional for customers. We have a brick and mortar store as well as an online store and people often come pick up their stuff in store and they are wondering what to do with the shipping rating. It should be possible to implement this, I've added it to my backlog

@30knees said in [Free Module]Revws - Product Reviews: @datakick Thanks for the reply! That's what I also first thought, but I have as a delivery delay 4 days and orders that are 22 days old but still show the message that merchandise hasn't been delivered yet. Please look into tb_orders table to see if this particular order has delivery_date field set. You can use datakick module as well (I believe that you have it): Order's delivery date field is updated when your order goes through status that has Show delivery PDF (strange name, if you ask me) My guess is that your Shipped status does not mark order as delivered. You will either need to fix this status, or change your workflow to switch order status to some other Delivered status few days after shipment. Or you can simply disable Delivery delay option in revws module by setting it to 0

@30knees this is because of Delivery delay(days) option. It's an additional and optional condition based on delivery_date field on order. In settings, you can set how long to wait before review request should be sent. This is useful, because it gives your customers some time to test the merchandise. Also, in some scenarios, delivery_date is actually a shipping date, so this option can be used to offset this difference

@Luv try downloading latest version 1.0.21, it should be fixed

You can simply check if _PS_ADMIN_DIR_ is defined. Alternatively, you can look what controller is currently in use - Context::getInstance()->controlller. Can I ask what you are trying to achieve? It seems really strange that the logic override should behave differently for backed/frontend

This seems to be bug in tbupdater module, it should be addressed. https://github.com/thirtybees/thirtybees/issues/619

@30knees said in Hack stats module to show the combinations of best selling products?: @datakick Shouldn't your module be able to do this? I have the ordered products list, but how do I group and sort that according to the most ordered product? Unfortunately no. My module can create list of transactional data only, it can't summarize it. There are plans to implement this (summary list feature), but it won't happen anytime soon. In fact, I first need to modularize my module a little bit first. It offers too much functionality, and that makes it too pricey for many merchants. Usually when someone wants to buy it, they need one or two functionality at most. But they have to pay higher price for all the other functionality won't even use. Most people want either xml export, or xml import. And almost nobody is using lists, mass updates, or custom fields,... Which is a shame, really, because these features are so powerful. I actually think that the list is the one feature that everyone should use daily.

@basix101 said in Updater v.1.3.3 "thirty bees' caching features are disabled": Edit: The "Update Thirty Bees" button is missing because of the disable cache error! Edit file /config/settings.inc.php, find line with _PSCACHEENABLED_ and change it to look like this: define('_PS_CACHE_ENABLED_', '0'); Note that this constant is not used anymore tb core, but tbupdater module still use it to determine if the cache is turned on/off

You can disregard this warning, it's a minor compatibility issue

The second issue - php warning - is fixed by https://github.com/thirtybees/blocklayered/commit/e83e3992eb6411f5dc4b072ce7fd4fc78845df48

Since the download took only 1 second, I assume the problem is in misconfiguration of your server. You probably do not have curl installed, or you might have some firewall that prevents the operation. I just tested it, and it works. Download took 93 seconds though, so I had to extend timeout limit on my nginx.

hmm, this one is caused by fix in the smarty engine. When iterating over array ends, smarty will keep the item variable alive -- referencing the last processed item: {foreach $list as $carrier} ... {/foreach} // at this point $carrier still references the last carrier in the $list The problem is when $carrier variable already exists before {foreach} statement. In smarty 3.1.19, original value was overwritten. That was deemed as a bug, and was fixed in newer version. Now the original value is restored. That means: ``` {assign var='carrier' value=1} {foreach $list as $carrier} ... {/foreach} // at this point $carrier contains value 1 ``` There isn't much we can do about that, really. We can fix this particular issue with OPC, but it's not really possible avoid this kind of bugs in general. https://github.com/thirtybees/thirtybees/issues/617

@dosbiner thank you for the info, this is quite strange error message. Do you have override for either controllers/front/ParentOrderController.php controllers/front/OrderController.php If not, could you disable all non-thirty bees module and try opening checkout page again?

Until this is fixed, you can bypass this validation. Edit file modules/stripe/stripe.php, and change lines 959..971 from php protected function tlsCheck() { $guzzle = new GuzzleClient(); \ThirtyBeesStripe\Stripe\ApiRequestor::setHttpClient($guzzle); \ThirtyBeesStripe\Stripe\Stripe::setApiKey('sk_test_BQokikJOvBiI2HlWgH4olfQ2'); \ThirtyBeesStripe\Stripe\Stripe::$apiBase = 'https://api-tls12.stripe.com'; try { \ThirtyBeesStripe\Stripe\Charge::all(); $this->updateAllValue(static::TLS_OK, static::ENUM_TLS_OK); } catch (\ThirtyBeesStripe\Stripe\Error\Api $e) { $this->updateAllValue(static::TLS_OK, static::ENUM_TLS_ERROR); } } to php protected function tlsCheck() { $this->updateAllValue(static::TLS_OK, static::ENUM_TLS_OK); }

It seems that endpoint https://api-tls12.stripe.com no longer exists -- domain can't be resolved to IP address. Github issue: https://github.com/thirtybees/thirtybees/issues/614

I'd like to ask for your cooperation with testing new version of smarty engine. As you might know, current version is rather old, and is not php7.2 compatible. There is a plan to upgrade smarty engine to newer version soon. This move is potentially dangerous, even though smarty syntax should be backwards compatible. It would be great to detect and fix any issues before this change is released. I've tested the new smarty engine on community theme, and it seems to be working correctly. But it's important to test other themes, and modules, as well. How can you help? First of all, this call for help is targeted for those of you who have dev / test environment. You can, of course, do this on your production site as well. It just bears some risks :) You will also need ssh access to your server Here are steps: upgrade you shop to 1.0.7 - there are few bugs in older versions that prevent using newer version of smarty. ssh to your server, and install composer: edit file composer.json, find entry smarty/smarty and change version from 3.1.19 to 3.1.31 (this is not the latest version 3.1.33 because that one has known bug) run composer update delete content of directories /cache/smarty/cache/ and /cache/smarty/compile/ switch to php72 [optional] Test your site and report any bug or issues. Please let us know even if you don't find any problems, so we know that it works fine with your theme.