datakick

sorry, that's classes/ConfigurationTest.php

This is an issue with TLS12 check. It stopped working due to external changes. In version 1.5 / bleeding edge, this test does not exists anymore. Edit file and delete line 130. Original code public static function getDefaultTestsOp() { return [ 'Gz' => false, 'Tlsv12' => false, ]; } should look like this public static function getDefaultTestsOp() { return [ 'Gz' => false, ]; }

Indeed, that's a bug. Javascript method that translates string is in this case called before the translations are provided. I have to delay this, and translate string only when error happens.

My guess is that your server raises some warning/error very early because of server misconfiguration -- maybe relate to that tempname() notice that should not be there. Thirty bees tries to handle the error, and during that error handler tries to access database. This fails, because db connection is not configured yet. The original error is not reported, and instead new error regarding database connection is raised. If true, it is obviously bug in thirty bees. Unfortunately, I can't reproduce this issue, so I'm not sure what to fix. @Alexander001 could you assist? Please edit file classes/db/DbPDO.php Find line die(sprintf(Tools::displayError('Link to database cannot be established: %s'), utf8_encode($e->getMessage()))); And replace it with die("<pre>$e</pre>"); That should tell us the origin of the problem. That's not real server, that's a joke. Their free plan severely limit number of concurrent connections to the server. Modern browsers can easily trigger a lot of concurrent requests, and their server just can't (won't) handle it.

No, that's correct. There shouldn't be this file. I asked because if this file existed, it might explain your issue.

Hard to tell. Do you have existing file /config/settings.inc.php ?

Hi everyone, I've just released a new module to strengthen back office security - two factor authentication module. https://store.getdatakick.com/en/modules/back-office-two-factor-authentication With this module, your store employees will have to enter authentication code during login to back office. The code changes every 30 seconds, and the only way to obtain current value is to use Authentication app on your phone -- there are many free authentication application available, for example Google Authenticator or FreeOTP. This functionality makes your back office more secure. It protect your store against brute-force attacks, mitigate impact of weak or leaded passwords, etc.

You have entered invalid server name for your "database server address"

This issue is usually caused by product miniatures listing. Product miniatures are displayed on category pages, but they can be elsewhere as well. For example, related products or crossseling on product pages. Some theme adds rich snippets metadata to these miniatures with itemType="Product", so google consider these as a full-fledged product description section. Which they are not -- they don't contain all the data google needs, hence the warning. In my opinion, the best fix is to modify your theme, and remove these rich snippets from product listing template. Relevant file is product-list-item.tpl. Remove all itemprop="***" itemtype="***" itemscope

You have to modify the module code. Replace all references to Attribute class with ProductAttribute.

Enable debug mode and (or) install collectlogs module. That will tell you what's wrong. Probably some module that is using Attribute class. That was renamed in 1.4 for php8 compatibility reasons

It's not possible - current database table schema doesn't permit this. It's not possible to have two rows in table tb_image with the same id_image, hence it's not possible to associate the same image with different products.

I bet it's about link. Spammers these days don't post link immediately, they simulate "engaged discussion" with hope their post will not be deleted. If not, they will return after few days or weeks and edit the message ti contain link. You can spot these quite easily, as they don't know what they are talking about. It's usually "thank you this helped me very much" kind of reply. AI helps them a lot, unfortunately . They just ask the original question, and copy-paste whatever AI generates. It's smarter than anything they could come up with themselves. It will make moderator work harder. We are thinking about disabling edit functionality for post older then few hours.

These are not errors, but warnings. And all of those are already fixed in bleeding edge. I saw in other thread that you downgraded to 1.3. That's not the right solution. Using PHP7.4 on 1.3 will not fix these warnings, it just masked them. You should update to bleeding edge, install collectlogs module, and keep track of all these warnings. Report those that originates in the core as github issues and we will fix them -- you can then install newer bleeding edge to check that the issue was fixed. Warnings that originates from third party modules should be fixed as well, otherwise you will not be able to safely update to new PHP versions in the future. Once all warnings has been fixed, it's safe to switch to higher PHP version. Bleeding edge thirty bees core + most native modules runs without any warnings even on PHP8.2. I have this php version on my production server and I didn't see any notice in the error log for a few weeks now.

If you are on 1.3, then you had to downgrade your PHP to 7.4. I think it's the PHP downgrade that fixed this problem, not tb version -- see this comment: I recommend you upgrade to bleeding edge (1.5) using core updater and install new mail transport module. That should fix this issue, and will allow you to use PHP8.1

Yes, it was deprecated in 1.6 or in 1.5, I'm not sure. The functionality was kept in the core, but enabled only for uses that had some scenes active, with the intention to remove it completely. I agree with this, actually -- there is no reason why this should be part of the core. If it's useful for somebody, we could extract the functionality to some module. But it should be removed from core.

???

This looks like server issue, not application one. cURL error 6: getaddrinfo() thread failed to start Looks like curl can't resolve domain address for api.thirtybees.com Check your server configuration.

You can check database schema using core updater. However, they don't probably mean "non-standard database". They will have issues with any database schema that is different to that at the time of module development. For example, in thirty bees, column tb_category_shop now has active column, but in ps16 db schema this column does not exists. If their module contains some hardcoded sql command to insert new categories, it can fail, because the value for this column will not be provided. That does not mean the database schema is 'non-standard'

You have to investigate. We don't know what your server stack looks like. It could be misconfiguration of any component, really - cloudflare, nginx, proxy server, cache server, apache, php-fpm, or even application issue (some thirty bees module). I don't think this is core issue, as nobody else is affected.

The only enhancement in 1.4 related to webp is ability to upload webp images in file manager. That is not related to product images. Product images do not support webp as a source format. Only as target format. @wakabayashi has been working on some enhancements in this area, which I believe will fix this limitation.

It's a module, so you have to chose 'Installed modules translations' and not 'Front office translations'

Controllers can (and often do) use helper function like Tools::parseNumber to process input values. This allows merchant to enter formatted strings that includes spaces and different separators, for example "$1 012,10". In core and native modules we try to use these helper methods everywhere user can input values. But of course, there are places we missed. You can file issues for those.

Look to file /vendor/composer/platform_check.php It should start with something like this: <?php // platform_check.php @generated by Composer $issues = array(); if (!(PHP_VERSION_ID >= 70400)) { $issues[] = 'Your Composer dependencies require a PHP version ">= 7.4.0". You are running ' . PHP_VERSION . '.'; } This is the stop-gag measure that prevents your store to run on older / non-supported versions of PHP. If it says 7.4, you are good

That's strange. Try to manually edit settings.inc.php and change value of _TB_BUILD_PHP_ to 7.4 Then go to core updater and try update. It will probably display something funny (manual modifications warnings, etc), but you can ignore these and perform the update.