datakick Posted September 28, 2018 Share Posted September 28, 2018 @purity said in Release 1.0.7 is there!: Seems to work fine with everything toggled green. Do you remember the old Pentium division flaw joke: Sure it gives the wrong answer, but look how FAST it is! This is probably what's happening to your site right now. And it's been that way ever since you've enabled full page cache. This feature never worked correctly, not even in previous versions. I'll describe what's wrong in another thread later. Link to comment Share on other sites More sharing options...
datakick Posted September 29, 2018 Share Posted September 29, 2018 You can read more info regarding Full Page Cache here. tl;dr - unfortunately it's not safe to use this feature in any version of thirtybees I'm not sure if it's possible to fix the underlying problem properly. If not, maybe this feature will have to be dropped completely. Link to comment Share on other sites More sharing options...
Traumflug Posted September 29, 2018 Author Share Posted September 29, 2018 I’m not sure if it’s possible to fix the underlying problem properly. It's certainly possible to fix it. But it's well possible all the exceptions handling code is then just as expensive as the code without full page cache. Time to create a set of performance measuring tests. Link to comment Share on other sites More sharing options...
the.rampage.rado Posted September 29, 2018 Share Posted September 29, 2018 For me right now tb is fast enough with just the working caching mechanisms. If you add php7.2 with some fixes for the current themes w/o need to fix themes it will be enough. Full page caching is a good thing but if I have to check daily if 10 things are broken or not it's not going to be turned on. Great work guys! Link to comment Share on other sites More sharing options...
Norwegian_Rat Posted September 30, 2018 Share Posted September 30, 2018 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, Link to comment Share on other sites More sharing options...
datakick Posted October 1, 2018 Share Posted October 1, 2018 @Norwegian_Rat your server probably failed to download the zip files from those urls. Please check with your hosting provider that your server don't have any restrictions regarding remote file access. Link to comment Share on other sites More sharing options...
Norwegian_Rat Posted October 1, 2018 Share Posted October 1, 2018 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 Link to comment Share on other sites More sharing options...
datakick Posted October 1, 2018 Share Posted October 1, 2018 Hard to tell what went wrong. There's probably some hint in your server's error log, or in thirtybees/log directory (if you have debug mode enabled). Regarding manual update - it's totally possible to go directly to 1.0.7. Just remember that you'll need to delete all stats modules, as described here. Simply follow the steps described in that article, the only difference is that you need to extract 1.0.7 version instead of 1.0.4 Link to comment Share on other sites More sharing options...
Traumflug Posted October 1, 2018 Author Share Posted October 1, 2018 Downloaded ZIPs go into admin/autoupgrade/download/. Extraction of these ZIPs goes into admin/autoupgrade/latest/Perhaps you can look these locations up, core ZIP should be 41686545 bytes (~40 MiB), extra ZIP should be 2817 bytes. Link to comment Share on other sites More sharing options...
Traumflug Posted October 1, 2018 Author Share Posted October 1, 2018 @norwegian_rat said in Release 1.0.7 is there!: [Ajax / Server Error for action unzip] textStatus: “error " errorThrown:” " jqXHR: " " I had a look at the situation and the good news is, one can download these files manually. Placed in the correct directory, they'll get recognized instead of downloaded again. Here's a module version which should give more helpful hints, please give it a try: 01538431535240tbupdater-master.zip Link to comment Share on other sites More sharing options...
Norwegian_Rat Posted October 1, 2018 Share Posted October 1, 2018 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(?) Link to comment Share on other sites More sharing options...
Traumflug Posted October 1, 2018 Author Share Posted October 1, 2018 Unzipping these files manually wouldn't work. Just already existing ZIP files get recognized if they have the correct MD5. To calculate MD5 on the command line, one can use md5sum <file>. If it still doesn't work it's a different issue. I just can't see a code path which wouldn't return a message, so I assumed it's a plain PHP script timeout. If you want to play with the code, processing happens in classes/AjaxProcessor.php. First round is ajaxProcessUpgradeNow(), then ajaxProcessTestDirs(), then ajaxProcessDownload() ... and so on. Link to comment Share on other sites More sharing options...
Chandra Posted October 2, 2018 Share Posted October 2, 2018 Please try with backups disabled. Link to comment Share on other sites More sharing options...
Norwegian_Rat Posted October 2, 2018 Share Posted October 2, 2018 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 Link to comment Share on other sites More sharing options...
30knees Posted October 2, 2018 Share Posted October 2, 2018 This might be relevant for the stats issue: https://forum.thirtybees.com/topic/1990/auto-update-to-newest-version-is-working-again/30 Link to comment Share on other sites More sharing options...
Norwegian_Rat Posted October 3, 2018 Share Posted October 3, 2018 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! Link to comment Share on other sites More sharing options...
Angstony_2 Posted October 4, 2018 Share Posted October 4, 2018 My local test version of TB (via vagrant + virtualbox) is still at 1.03 – which is surprising as I only installed it recently. Do I need to install any earlier versions before installing this one? Link to comment Share on other sites More sharing options...
Traumflug Posted October 4, 2018 Author Share Posted October 4, 2018 Do I need to install any earlier versions before installing this one? The updater module should work for any version between 1.0.1 and 1.0.6. Link to comment Share on other sites More sharing options...
Angstony_2 Posted October 4, 2018 Share Posted October 4, 2018 Thanks Traumflug. I'll try it as soon as the backup has completed. How on Earth Windows can take longer to copy a file set than it took to download them is beyond me… By the way, this forum seems to be broken in the latest version of my preferred browser (Firefox 62.0.3). It's constantly displaying a message that the forum has been disconnected, it wouldn't automatically load newer comments as I scrolled down, and I couldn't post comments – I'm having to use Chrome for that. Link to comment Share on other sites More sharing options...
Angstony_2 Posted October 4, 2018 Share Posted October 4, 2018 I'm getting the same 505 error as Norwegian_Rat, but I suspect it may be because Windows is in the middle of a major update, so everything is running at a snail's pace. I'll try again once that update is done and dusted. Link to comment Share on other sites More sharing options...
Traumflug Posted October 4, 2018 Author Share Posted October 4, 2018 Please don't evaluate thirty bees on a web server running on Windows. This is known to be troublesome. Link to comment Share on other sites More sharing options...
Angstony_2 Posted October 4, 2018 Share Posted October 4, 2018 @traumflug said in Release 1.0.7 is there!: Please don't evaluate thirty bees on a web server running on Windows. This is known to be troublesome. Hmm… I thought the vagrant+virtualbox method was supposed to be pretty robust – at least that's the impression this article gave me – is that not the case? Only I'm new to this and I read somewhere that best practice is to develop locally, upload to a test site and only when that's proven okay copy it into production. I do also like being able to edit files directly in Windows Explorer without needing ftp, but I'm happy to do whatever you advise is best. Link to comment Share on other sites More sharing options...
Traumflug Posted October 4, 2018 Author Share Posted October 4, 2018 I thought the vagrant+virtualbox method was supposed to be pretty robust Then it's no longer a server running on Windows, but a Linux running on (for the virtual machine and during these updates) crippled hardware. One solution is to make this PC dual booting with Ubuntu. This gives the most from the hardware and also gets rid of these slow update processes. The other one is to go to dinner during these updates, as you had the plan to do. Link to comment Share on other sites More sharing options...
Angstony_2 Posted October 4, 2018 Share Posted October 4, 2018 @traumflug said in Release 1.0.7 is there!: The other one is to go to dinner during these updates Well I could live with slow updates but at the moment it's still raising a "502 Bad Gateway" error during the zip extraction process. I've got to leave it for now, but I'll get back onto it tomorrow and maybe just go set up a test site on a subdomain, if that's going to be less problematic. Link to comment Share on other sites More sharing options...
spidawebs Posted October 5, 2018 Share Posted October 5, 2018 HELP! I have just upgraded from 1.0.3 to 1.0.7 using the upgrade module. The upgrade completed successfully but as soon as I refreshed the page, I have lost access to both the backend and the frontend. It just comes up with a 500 server error and this message: This page isn’t working www.ageasbowlshop.co.uk is currently unable to handle this request. Any idea what could be wrong and how to fix it? I will have a look at the server logs and post again if I find anything in there which may help. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now