Norwegian_Rat

Ah! Great to hear @Traumflug . Still got the issue with the modules, though. How do I solve this?

@lesley : The passwd cloumn is set to varchar 60, so I guess this one is OK then? @Traumflug : Maybe a stupid question, but how do I run the upgrade again when the updater settings says I'm running the latest version, and nothing happens when I select "Stable" from the dropdown option? (I know that we can do rollback and do it over again, but I'm not quite sure if this is what you ment?) I'm not even sure if the module issue is related to the upgrade? Every module I have tried installing throws this error.

Ah! Thank you for the information @Traumflug ! Appreciate it. Will have a go at it and tell you how it went. All the best

Hi TB Forum I did an upgrade from 1.0.3 to 1.0.7 two months ago, and I got an error (see further down) I never got an answer to this error, but the shop did however work fine, and I couln't find any issues, so I did not think too much about it. But today when I was going to install the cookiebot and cookie consent modules, I got this error: [PrestaShop] Fatal error in module file :/customers/3/f/a/norwegianrat.no/httpd.www/vendor/pear/archive_tar/Archive/Tar.php: Cannot use result of built-in function in write context Is this somehow related to the error I got two months ago? Thanx in advance, ......................... 02.10.18 The updater did download and extract files as I mentioned in an earlier post. Trying to avoid the error, I cleaned up all the files in the “download” and “latest” folder to be sure I was starting with clean slates. I then did as follows: Disabled and uninstalled the updater. Uploaded the updater @Traumflug provided the link to (even though it was the same version number) Downgraded PHP from 7.1.19 to 7.0.30 One of these steps got it to work. At least partially. It gave me an error after a while, but so far the BO is working and says 1.0.7, and the front office sees to be working. What worries me a little is the error I got: All files upgraded. Now upgrading database… [Ajax / Server Error for action upgradeDb] textStatus: “error " errorThrown:” " jqXHR: " " Do we now have a broken database somewhere?

Thanx a lot, @30knees ! That made it work. Disabled and installed the "statsmodule" and "statsdata" modules, and downloaded them from github and reinstalled. Thumbs up!

Mkai..here's a little update: (We always do several backups manually @Chandra, so we always turn this one off, since these settings always caused issues when running PS) The updater did download and extract files as I mentioned in an earlier post. Trying to avoid the error, I cleaned up all the files in the "download" and "latest" folder to be sure I was starting with clean slates. I then did as follows: Disabled and uninstalled the updater. Uploaded the updater @Traumflug provided the link to (even though it was the same version number) Downgraded PHP from 7.1.19 to 7.0.30 One of these steps got it to work. At least partially. It gave me an error after a while, but so far the BO is working and says 1.0.7, and the front office sees to be working. What worries me a little is the error I got: All files upgraded. Now upgrading database... [Ajax / Server Error for action upgradeDb] textStatus: "error " errorThrown:" " jqXHR: " " Do we now have a broken database somewhere? Will do some more check ups to see if I can find any issues. Update: When we enable the statsmodule, we get a "This page is not working" -page. Not sure if this has anything to do with the error we got during the upgrade... All the best

Ah! Thanx a lot for the research, @Traumflug ! I was playing around with extracting the zip file manually in the folder using an unzipper.php file (with the hope it would result in the good news you mentioned) I believe I extracted it in the wrong folder though, in the "download" and not the "latest" folder, so I will have to give it another go That said: I was rocking and rolling about in those folders, and I actually saw that the 1 0.7 files got extracted to the "latest" folder (using te upgrader), but yet it gave me the error. I can double check this though, just to be on the safe side if the info might be useful(?)

Thanx for your reply, @datakick . Will look into that. That said we have never had any problems with PS-updates and migration to TB. Guess this involves pretty much the same procedure? Only difference I can think of, is that we now use PHP 7.1. Could this casue it? Can we go directly from 1.0.3 to 1.0.7 if we get it to work? And if we have to do it manually, do we have to go through 1.0.4 first? All the best

Hi folks! First of all; Thank you for all the hard work you putting into this project! Well done! We have been running 1.0.3 for a while now and are super happy with everyhting. But we thought it might be time to run an update. Just got a few questions regarding this. We did try the updater, but this ended up in a error: [Ajax / Server Error for action unzip] textStatus: "error " errorThrown:" " jqXHR: " " Archives will come from https://github.com/thirtybees/thirtybees/releases/download/1.0.7/thirtybees-v1.0.7.zip and https://api.thirtybees.com/updates/packs/thirtybees-extra-v1.0.7.zip md5 hashes for core and extra should be resp. 472994fe989dfdd8da6a01ac0e4964e8 and 5c7168745f4a6535565660a1d1a3420f Is this becasue we're on 1.0.3 ? I see that Lesley is mentioning somthing about query scripts regarding the 1.0.4, and if I remember correct there was something about doing 1.0.4 before 1.0.5+ ? Thanx in advance,

True, true. That said I would say switching to TB was a better alternative (at least for us) than to stay with PS. The 1.6 branch will die later this year anyway, and if they don't get their 1.7 straight with migration tools and all , PS would never be an option anyways. I might be wrong, but at the time we switched it didn't exactly look promesing.

Personally I think this project will gain a lot more momentum when 1.6 comes to an end over at PS later this year. Now I like to play around with things like this, so we migrated over a year ago, but I think the majority chose to just let their store be, til the time comes where they MUST do something

Our experience with tb and migration is nothing but great. Migrating from PS to tb was by far a much easier task than a PS-patch upgrade. And knowing we came from PS 1.4, I would say such a flawless migration is proof of pretty darn solid work! But of course, we had to disable and uninstall bought modules that caused issues. But we cant expect them to take every module that's out there into account when developing a migration tool

We used to load videos and tunes from YouTube and SoundCloud, and that worked fine in the start. However, as we added the iframes the page got slower and slower. It became so slow it wasnt usable. Now this was on one page, so maybe you wont face the issue we had. To solve this we created our own page with a js player, and loaded the files from our domain, and now the page is supersnappy!

Hi everyone. Hope you all had a nice Yule celebration! =) I was just dropping in because I ran into some od behaviour regarding the JSON module. It won't let me save the instagram address. Or in fact it give me the "Successful" message, but the field is still blank. Anyone else experienced this? Regards

You can of course use uptimerobot or google docs (or any other). Using the GD myself, and it works like a charm. This was more a question if it could be implemented in an easy way. Like in no more hazzle than a checkbox with "notify me my site goes down" etc

That's what I thought as well, but since I'm no tech-head I had to ask. =) Would have been quite a cool feature though, as I believe lots of merchants would like to know when their server goes down. Especially when you're on shared hosting, and knows for a fact the provider doesnt always put their downtime in the log

Would it possible making the "Turn Google docs into monitoring the up/down time for your website" feature into a module or something? Now my wild guess is that you can't run this operation from the domain you want to monitor, but what do I know. Thoughts, anyone? Here's the link to script I'm talking about if anyone is interested https://lifehacker.com/5896830/use-google-docs-to-monitor-your-websites-uptime

Got it!

I wasn't sure if it was a bug or not. That's why I posted it here, @mdekker =)

The default landing page when you log in. The status do however show on the "order" page

Anyone else noticed that the status of the orders disappeared on the dashboard when upgrading to 1.0.2?

Mmmno. Haven't tested that module. Is it supposed to work with IM?

It wasn't exactly a huge sacrifice going from 7.1 to 7.0, @dprophitjr ;)

I'm with the others in this thread. We just migrated ourselves from PS 1.6.1.11 on friday, and it went flawlessly. The only thing worth mentioning is that you should downgrade to PHP 7 if you're on 7.1, and it might be wise to uninstall complicated modules and reinstall them after the migration. Not sure if this is a must, but some modules caused a little trouble for us in our test-environment. However; This might be because of different domains and us not updating the settings after we moved our live store to a test folder etc. Anyhow it's not much work uninstalling and reinstalling a module just to be on the safe side. :)

Ah! Nice! Your work on the migration module itself seems like pretty panzer work as always. In the end we can't expect you to take care of the errors made by others elsewhere! (at least not every errors!;) Super work! Really looking forward to to live with tb now. Just need to tweak the default theme a little =)