datakick

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.

Go to Preferences > SEO & URLs and enable Emit SEO fields

Maybe your config/settings.inc.php file is not writeable? This is where core updater saves information about revision and php build.

You have to go to core updater settings and change target php version to php7.4. Then you can downgrade your php version. Looks like your php8 is not installed properly. You need pdo extension enabled. You probably don't.

Your server respond with 301 REDIRECT for 'add to cart' POST request 🤦‍♂️ and ask your browser to fetch page to https://<domain>/en/?rand=<rand> Browser do exactly that, and perform GET request for that page Now, this is GET request without original POST parameters, so nothing is added to the cart.

I agree. I just want to see different implementation of such feature, and not pollute transactional data with guesstimates. Order table should contain facts only

Number of rules you can create. Free version allows you to create 2 rules only.

my consequences module can do that. It allows you to create rule that will attach file before email for specific template is sent.

This is wrong. You always exit from foreach with a return, during the first iteration. You want to return only when error is encountered. Add {...} to your if statements, like this: foreach ($banned_in_email as $string) { if (strstr($from, $string)) { $this->errors[] = Tools::displayError('This email address is not allowed'); return; } }

Both are issues with your theme That's enough. Just don't post your admin dir anywhere. It was visible in your previous post -- I have edited it already to remove this sensitive information.

This error message suggests that you were logged-out during update. This can happen because coreupdater is a module that depends on core which is being updated. If something related to authentication process (encryption algorithm, cookie serialization, etc) changed in the new version, the current back office session is invalidated. That's quite stupid. No, it's very stupid. One of the high priority task on a todo list. We need separate updating tool that does not depend on core. Such tool could be even use to migrate ps16 directly to latest thirtybees. Anyway -- you should run core updater again. If there are no changes listed, go to Database tab and apply fixes. At least all missing tables and missing columns -- that would be performed automatically, but was not due to the logged-out bug.

So you probably have access to some control panel. It should contain some SQL tool (PHPMyAdmin or similar). Use this to connect to your database, and run this query: SELECT * FROM tb_employee; That will list all employees in your database. If this does not work, you have different database table prefix -- the table can be named like tb123_employee, ps_employee, or whatever. Look into the list of employees, and find the employee email address for which you want to change password. Let's say it's [email protected] Then run this SQL query (change email address with the one you chose in previous step) UPDATE tb_employee SET passwd = '$2y$10$tGwJd/0V1mZJM0ZlHYdUkebHMr/5dJzl3N0UAt2e3IfWwQP.JJPmC' WHERE email = '[email protected]'; that will change passwords for this employee to changeme1234 Now you can go to your admin login page, enter the employee email address and this new password, and you will be able to log in. Then go to your preferences in upper right corner dropdown menu, and change your password to something more secure.

Good points. In the upcoming version of module there is a new validation for prefix, and that it matches country address. We could also implement regexp check, if the vat formats for different countries are know. That should fix the problems you mentiioned