chan

No, it is on a shared hosting, but a reliable one. Probably there are some problems with the modules, but with the theme as well. And it seems much too much work to try to figure that out. Since the shop is currently running stable PS 1.6 on PHP 5.6, my suggestion to the site owner was to keep it like that for the time being and to start working on a move to Woo. So it seems we will completely skip the Thirtybees experience. Only in case that the hosting company will completely stop support for php 5.6 before we're ready, we will then, as a temporary measure, go to PHP 7.4 and migrate to TB 1.4 Thank you all for the help!

I don't doubt it that datakick is THE person to work on something like this. But the point is that this shouldn't be something that complicated. I mentioned above some specific issues that don't work even while following datakick's instructions. It is a small shop with only few products, so I am not sure that it makes sense to go this route at all. Seems like the old theme is not compatible - the xml config file gives error and I couldn't find any instruction whatsoever regarding this. So if I need to create the theme from scratch, it seems to me that it makes more sense to do it in a more widely supported system.

Problem is, I don't manage to fix the errors as I'm in that vicious circle as described. Kind of feel like a dead end with thirty bees for me in this project. As I wrote, we give tb a try since 5.6 was the last version that ps 1.6 supported. If I don't manage to make the change to php 8.2+ I'll have to recommend to the customer a migration to another platform.

datakick - many thanks for the very detailed reply! Obviously I do want to move to php 8.x but so far I don't manage. Something is breaking terribly and I don't manage to find what that is. The whole reason to give TB a try was that an old prestashop site that I created years ago became unusable (beside on php 5.6), and we had to find a solution. So basically TB seems like a great solution - forking of the PS 1.6 strain with the possibility of continuity. With the "collectlogs" module - do you mean the "collect php logs" module? I installed it and so far didn't manage to fix any of the warnings and depracations that were noted there (code noted with line numbers seem to be inaccurate - I don't find that code in the noted files...). One of them had to do with the old paypal module by the way, so I uninstalled it and now there isn't seem to be a current paypal module offered by TB in the module list. One of the depracations warnings is this: Message: Unparenthesized a ? b : c ? d : e is deprecated. Use either (a ? b : c) ? d : e or a ? b : (c ? d : e) Location: classes/module/Module.php(871) : eval()'d code line 695 I guess this is a generalized error message since I couldn't find an exact occurrence in all of the files. Is there a way to find out which modules are incompatible? (I'd kind of expected that thirtybees will be able to point to them...) Do you think that if I manage to fix all of the errors mentioned in the php logs module the php change will go smoothly? should I do it gradually as some suggested here? (i.e. 8,8.1,8.2,8.3) Another issue has to do with the theme - the shop used a slightly modified PS default theme. It is working, but if I change theme and try to go back - I get a config.xml error and there is no way to go back to the original theme. I find this weird. Is there any solution? (by the way, the new theme config.xml file is MASSIVE - there is almost no way I could re-create something like this from scratch. Is there some tutorial as to how to do that? What are the minimum requirements for that - do I really have to list all of the modules and hooks in there? Thanks!

well the only thing is that we moved to TB in the first place because php 5.x isn't really supported anymore. So I don't know how much longer will 7.4 be supported. Don't want to have surprises. I also tried 8.0, 8.1 8.2 and all create the same problem and the site is breaking

Thanks for the quick reply! I indeed use an old PS default theme (slightly modified css). But the problem is that the BO becomes error 500 or the other error as well. I cannot do anything once I start the update process. When I run on 7.4 I don't see any notices - where did you mean I should look for them? After I follow step 2, save and go to update - I receive a whole list of red entries of "changed files", "missing files" and "extra files". If I now update them the site will get stuck on the other error I mentioned ("Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.0.0". ") and changing the php version on the server will not change this and the site is completely broken in the front and back office. This is exactly the vicious circle I referred to. Or what did you mean I should do differently?

I got it working stable on php 7.4 TB 1.6 (stable) If I update the php version to anything from 8 up, I receive an error 500 on all pages (back and front office). If I first change the "target php version" to the one I want to change to, save, and then update the php version - the same. If after setting the option to php8.xx, then check for updates under core updater I get "your installation is broken" with a list of files that need to be updated. If I update them, I receive an error that "Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.0.0". And the site becomes completely broken - I then need to delete all files by ftp and upload them again from a backup. This is very tedious and the main thing is, that I can't seem to find a way to get free of this vicious circle of updates - nothing works. So how should I update the php to 8.3 without destroying the installation?

OMG this was it! Thanks a lot! Why is it under "debug mode"??? 🙂

yup. nothing happens (and there should have even been an option for using php's mail() function, right? i.e. without smtp settings..)

It is impossible to select anything - the email transport field shows only "none". I reset, un- and re-installed phpmailer - nothing changes.

tb 1.6, php 7.4 I get an warning on the email setting page ("Your server is NOT sending emails. Please install some email transport module and select it for use."). But nothing change even after I install that module. Any idea? thanks in advance!

I also got stuck with all of the php version mess. My solution: since the PS version was 1.6.XX I thought it might be a good idea to try to use a TB migrator version that old as well. So I tried the 1.0.2 version (from here) and the migration went smoothly!