evolvewh Posted August 22, 2013 Report Share Posted August 22, 2013 I'm not sure if it was supposed to be this way or not but the blesta.php file inside the config folder for the full 3.0.1 version is named blesta-new.php Is that correct or a mistake? Quote Link to comment Share on other sites More sharing options...
0 Michael Posted August 22, 2013 Report Share Posted August 22, 2013 I'm not sure if it was supposed to be this way or not but the blesta.php file inside the config folder for the full 3.0.1 version is named blesta-new.php Is that correct or a mistake? Correct leave it be, you don't need it. Just keep your blesta.php. Quote Link to comment Share on other sites More sharing options...
0 evolvewh Posted August 22, 2013 Author Report Share Posted August 22, 2013 This was my first time upgrading (new user) so I wanted to point out a couple of things in case there are others who are just getting started and looking for this info: 1. The upgrade URL is www.yourdomian.com/index.php/admin/upgrade/ , for some reason I read it to be www.yourdomain.com/admin/upgrade/ (maybe I'm just too tired). If you have the install in a folder, you need to of course add that before the /index.php/admin/upgrade/ 2. I had to go to my installed modules and payment gateways and click upgrade for a couple of them after I ran the upgrade script. 3. Check all of your login info for modules and payment gateways. Mine was all erased after the upgrade. I don't have this all up and running yet because I'm waiting for the WHMCS import but I'm hoping that more things aren't going to be wiped out during an upgrade. Quote Link to comment Share on other sites More sharing options...
0 Paul Posted August 22, 2013 Report Share Posted August 22, 2013 3. Check all of your login info for modules and payment gateways. Mine was all erased after the upgrade. Which were erased? This patch doesn't touch the database, so no module data should be erased. Quote Link to comment Share on other sites More sharing options...
0 evolvewh Posted August 22, 2013 Author Report Share Posted August 22, 2013 Maybe my mistake but I ended up using the full version instead of the patch. Logicboxes, bluepay, paypal standard and all of cPanel except for my nameservers were wiped out. Quote Link to comment Share on other sites More sharing options...
0 Michael Posted August 22, 2013 Report Share Posted August 22, 2013 Maybe my mistake but I ended up using the full version instead of the patch. Logicboxes, bluepay, paypal standard and all of cPanel except for my nameservers were wiped out. Sorry to hear that, however Cody did state how to patch (Well gave a link) http://www.blesta.com/forums/index.php?/topic/831-release-301/#entry6854 However it's your first time, do you have any backups mate? Also what I do is upload the files to the server in a upload folder. I then remove the routes.php from the /config/ folder to keep my admin and client area saved. Then I go to /app/views/clients/ and rename default to default-3.0.1 that way it won't overwrite the custom theme. Then move the files over to the public_html Then run the /upgrade/ Hopefully this will help you in the future . Quote Link to comment Share on other sites More sharing options...
0 evolvewh Posted August 22, 2013 Author Report Share Posted August 22, 2013 Sorry to hear that, however Cody did state how to patch (Well gave a link) http://www.blesta.com/forums/index.php?/topic/831-release-301/#entry6854 However it's your first time, do you have any backups mate? Also what I do is upload the files to the server in a upload folder. I then remove the routes.php from the /config/ folder to keep my admin and client area saved. Then I go to /app/views/clients/ and rename default to default-3.0.1 that way it won't overwrite the custom theme. Then move the files over to the public_html Then run the /upgrade/ Hopefully this will help you in the future . I'll definitely use this as a reference. I'll survive because I don't have any data in there yet (other than login info which is not hard to replace) so it's just a good learning lesson right now! I did avoid overwriting my custom theme in /app/views/clients/ but made a mistake somewhere along the way with the admin. I usually make a backup but I didn't this time because it was all test and no actual client data setup in there. Quote Link to comment Share on other sites More sharing options...
0 Michael Posted August 22, 2013 Report Share Posted August 22, 2013 I'll definitely use this as a reference. I'll survive because I don't have any data in there yet (other than login info which is not hard to replace) so it's just a good learning lesson right now! I did avoid overwriting my custom theme in /app/views/clients/ but made a mistake somewhere along the way with the admin. I usually make a backup but I didn't this time because it was all test and no actual client data setup in there. Great job you didn't overwrite your theme, I did that once haha I was half asleep and upgraded and then I was like Oh F*** lol and thankfully I had a half done backup. Since then I always do it that way above. Quote Link to comment Share on other sites More sharing options...
0 evolvewh Posted August 22, 2013 Author Report Share Posted August 22, 2013 The theme would be the easy part to fix (for me anyway). I'll definitely follow your method for all future patches. Quote Link to comment Share on other sites More sharing options...
0 MemoryX2 Posted August 22, 2013 Report Share Posted August 22, 2013 1. The upgrade URL is www.yourdomian.com/index.php/admin/upgrade/ If this is the actual url you used, idk how it worked because I can't get it to. www.yourdomain.com/admin/upgrade/ This is the url you should be using. It works for me since b1 all the way to 3.0.1 and it hasn't wiped any of my data yet.. Michael 1 Quote Link to comment Share on other sites More sharing options...
0 Moby2000 Posted August 22, 2013 Report Share Posted August 22, 2013 Just did the upgrade and everything went smoothly no problems using "www.yourdomain.com/admin/upgrade/ ". But the only thing i see that hasn't changed is the version number in the bottom right corner. Still says "Installed Version 3.0.0" Steve Quote Link to comment Share on other sites More sharing options...
0 Michael Posted August 22, 2013 Report Share Posted August 22, 2013 If this is the actual url you used, idk how it worked because I can't get it to. This is the url you should be using. It works for me since b1 all the way to 3.0.1 and it hasn't wiped any of my data yet.. Mate his domain isn't yourdomain lol and the admin/upgrade is the way to upgrade. However he accidentally overwritten the blesta.php which is why he managed to re-install it Quote Link to comment Share on other sites More sharing options...
0 Michael Posted August 22, 2013 Report Share Posted August 22, 2013 Just did the upgrade and everything went smoothly no problems using "www.yourdomain.com/admin/upgrade/ ". But the only thing i see that hasn't changed is the version number in the bottom right corner. Still says "Installed Version 3.0.0" Steve Erm you sure you upgraded or half upgraded mate? I get: Blesta © 2007-2013, Phillips Data, Inc. Licensed to Licensecart Installed Version 3.0.1 Quote Link to comment Share on other sites More sharing options...
0 Moby2000 Posted August 22, 2013 Report Share Posted August 22, 2013 <--- kick me in the backside Forgot to clear my browser cache lol Steve Michael 1 Quote Link to comment Share on other sites More sharing options...
0 Michael Posted August 22, 2013 Report Share Posted August 22, 2013 <--- kick me in the backside Forgot to clear my browser cache lol Steve Woops I never need to clear my cache to see it chrome ftw Quote Link to comment Share on other sites More sharing options...
0 MemoryX2 Posted August 22, 2013 Report Share Posted August 22, 2013 Mate his domain isn't yourdomain lol and the admin/upgrade is the way to upgrade. However he accidentally overwritten the blesta.php which is why he managed to re-install it I was referring to the /index.php/ part I know that your domain isn't his domain. Index.php should not be in the upgrade url so I tested it to see if I could even get it to load with index.php in my url and I could not. At minimum that is the wrong url but it may also reflect the wrong file permissions by it even being loadable. The upgrade URL is pathtoblesta/admin/upgrade Michael 1 Quote Link to comment Share on other sites More sharing options...
0 Michael Posted August 22, 2013 Report Share Posted August 22, 2013 I was referring to the /index.php/ part I know that your domain isn't his domain. Index.php should not be in the upgrade url so I tested it to see if I could even get it to load with index.php in my url and I could not. At minimum that is the wrong url but it may also reflect the wrong file permissions by it even being loadable. The upgrade URL is pathtoblesta/admin/upgrade Haha I missed that woops #2 Quote Link to comment Share on other sites More sharing options...
0 Paul Posted August 22, 2013 Report Share Posted August 22, 2013 I was referring to the /index.php/ part I know that your domain isn't his domain. Index.php should not be in the upgrade url so I tested it to see if I could even get it to load with index.php in my url and I could not. At minimum that is the wrong url but it may also reflect the wrong file permissions by it even being loadable. The upgrade URL is pathtoblesta/admin/upgrade /index.php/admin/upgrade is correct, if mod_rewrite is not being used. If that's the case, all URLs will have /index.php/ followed by the typical path structure. Of course, we recommend using mod_rewrite with the included .htaccess file, but some servers don't support it or don't have it installed. MemoryX2 and Michael 2 Quote Link to comment Share on other sites More sharing options...
0 evolvewh Posted August 22, 2013 Author Report Share Posted August 22, 2013 /index.php/admin/upgrade is correct, if mod_rewrite is not being used. If that's the case, all URLs will have /index.php/ followed by the typical path structure. Of course, we recommend using mod_rewrite with the included .htaccess file, but some servers don't support it or don't have it installed. Mod Rewrite is installed so I'll have to look into the rest of it. I'm happy to hear that I can make the /index.php/ part go away. Michael 1 Quote Link to comment Share on other sites More sharing options...
0 evolvewh Posted August 22, 2013 Author Report Share Posted August 22, 2013 Mod Rewrite is installed so I'll have to look into the rest of it. I'm happy to hear that I can make the /index.php/ part go away. /index.php/ is gone! When the WHM** import is ready, will that be made as an announcement at the top of the forum, or elsewhere? Quote Link to comment Share on other sites More sharing options...
0 Paul Posted August 22, 2013 Report Share Posted August 22, 2013 /index.php/ is gone! When the WHM** import is ready, will that be made as an announcement at the top of the forum, or elsewhere? We will mention it someplace, yes. Probably a forum thread, with the files attached. Michael 1 Quote Link to comment Share on other sites More sharing options...
Question
evolvewh
I'm not sure if it was supposed to be this way or not but the blesta.php file inside the config folder for the full 3.0.1 version is named blesta-new.php Is that correct or a mistake?
Link to comment
Share on other sites
20 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.