prab007 Posted June 4, 2015 Share Posted June 4, 2015 Hello, I upgraded from version 5.2.16 to 6.0.5. It was working fine when I checked last time which was about 3 days ago but the version seems to have a major issue. My site was really slow and the images were not loading not even a single and god knows how long it had been like that as I was away. I have rolled back to 5.2.16 and seems like its working fine but would like to ask if you could fix the issue as soon as possible. Regards, Quote Link to comment Share on other sites More sharing options...
Al Brookbanks Posted June 4, 2015 Share Posted June 4, 2015 Hi @prab007 We haven't come across any other cases like this and I would say that 6.0.5 is more stable than any v5 release. Unless there are any error logs to say otherwise that the upgrade version is coincidental. Maybe the server hit a heavy load? Please let us know if you find anything interesting in the php or apache error logs. Quote Link to comment Share on other sites More sharing options...
havenswift-hosting Posted June 4, 2015 Share Posted June 4, 2015 HiI would agree - we have a large number of clients running both V5 and V6 including 6.0.5 and not seen any other cases like that - I think you need to investigate other causes firstIan Quote Link to comment Share on other sites More sharing options...
prab007 Posted June 4, 2015 Author Share Posted June 4, 2015 Hi,I just upgraded to v6 again. But the problem is still there. I am using Vector Skin and fusion plugin does it has to do any thing with V6?Prabesh Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted June 4, 2015 Share Posted June 4, 2015 Have you tried your store with a stock Foundation skin? I used to use Blueprint, which is another Fusion skin from the same developer. It is possible to get a comparable look and function with Foundation. It does take a willingness to either pay for cosmetic changes and/or the time to make the edits yourself. I did a little of both. Quote Link to comment Share on other sites More sharing options...
bsmither Posted June 4, 2015 Share Posted June 4, 2015 I will recommend you download the latest version of Fusion from here. Unless you already have. The latest version no longer phones home for a license check. Quote Link to comment Share on other sites More sharing options...
prab007 Posted June 9, 2015 Author Share Posted June 9, 2015 @bsmither @Al Brookbanks Thanks but even the fusion update did not help. I just figured out the problem seems with SSL certificate path but not sure where. Even in v5 if SSL is enabled on all pages the problem occurs but if I disable it works fine. It seems that SSL is the issue with v6 aswell. I would be grateful if you could help me on this.Many thanks. Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted June 9, 2015 Share Posted June 9, 2015 Back up your database first, as you may have to revert to the backup. No promise this will work at all, or fix your issue. It may make a mess!!But maybe it's worth a try. Go to the SSL tab of Store Settings and delete the Standard Store url and Save. Quote Link to comment Share on other sites More sharing options...
prab007 Posted June 9, 2015 Author Share Posted June 9, 2015 Thanks. But it did not work. I cant figure out why SSL blocking the page elements. Kindly help!!!! My domain and SSL is hosted by Godaddy Quote Link to comment Share on other sites More sharing options...
bsmither Posted June 9, 2015 Share Posted June 9, 2015 What is the web address of your store? Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted June 9, 2015 Share Posted June 9, 2015 Another stab in the dark - backup your .htaccess and then delete it. CC will create one when you load your store and see if that gets you anywhere. Quote Link to comment Share on other sites More sharing options...
prab007 Posted June 10, 2015 Author Share Posted June 10, 2015 @bsmither @Dirty Butter Bingo!!! Deleting .htaccess have worked at the moment. Thanks a lot for your help. Any issues ill get back to you. Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted June 10, 2015 Share Posted June 10, 2015 Great!!! I'll mark this as Resolved, but comment again if it starts up, and I can always take the Resolved off. If you would, could you attach a copy of your original .htaccess file? It might help solve this issue. I, too, had to delete my .htaccess to get 6.0.5 to work properly. Quote Link to comment Share on other sites More sharing options...
prab007 Posted June 10, 2015 Author Share Posted June 10, 2015 @Dirty Butter Please find attached .htaccess file. Thanks htaccess (3) Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted June 10, 2015 Share Posted June 10, 2015 You ARE on https????? Your old .htaccess has a redirect section near the bottom where all seem to be http:// url's Quote Link to comment Share on other sites More sharing options...
prab007 Posted June 10, 2015 Author Share Posted June 10, 2015 Yes I am on https. I am new to coding so I don't understand the terms very much. Anything wrong with that? Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted June 10, 2015 Share Posted June 10, 2015 I don't know enough to know if that's why the upgrade was an issue or not. But it looks odd to me. Just to clarify - were you on SSL BEFORE your upgrade?I had some Redirects in mine that seem to have caused my issues, and you had some Redirects as well. I'll attach my old one, so maybe someone can spot how to keep this from causing problems with the new SSL coding. .htaccess Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted June 11, 2015 Share Posted June 11, 2015 @prab007 There's a brand new GitHub change that MAY be the correction for the problem you and I were having with the original .htaccess file causing issues on 6.0.5.If you would, please backup seo.class.php and then do this:1. Comment out this section, as shown: /* COMMENTED OUT PER GITHUB } elseif (!strstr($current_contents,'RewriteBase '.CC_ROOT_REL) || !strstr($current_contents, CC_ROOT_REL.'index.php')) { $find = array( '/^.*?RewriteBase.*\n?/m', '/^.*?ErrorDocument.*\n?/m' ); $replace = array( "\tRewriteBase ".CC_ROOT_REL."\r\n", "ErrorDocument 404 ".CC_ROOT_REL."index.php\r\n" ); if(!file_put_contents($htaccess_path, preg_replace($find, $replace, $current_contents))) { die('Failed to update existing .htaccess file for Search Engine Friendly URL\'s. Please edit this file in the stores root directory to have the content.<textarea style="width: 400px; height: 300px;" readonly>'.$current_contents.'</textarea>'); } $GLOBALS['cache']->write('1',$cache_id); httpredir(); */ 2. Then rename the working .htaccess file and replace it with your copy of your ORIGINAL .htaccess file.See how things work and please report back. Quote Link to comment Share on other sites More sharing options...
prab007 Posted June 15, 2015 Author Share Posted June 15, 2015 (edited) @Dirty Butter Im new to coding. Did you mean to add the above codes or is there any section that I need to amend? Edited June 15, 2015 by prab007 Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted June 15, 2015 Share Posted June 15, 2015 The code I showed above is in the seo.class.php file. Putting the /* at the beginning and */ at the end has the effect of keeping that code from doing anything in the file. It comments it out.So Search for RewriteBase in the code. Be sure you have the correct section and put the /* */ around it, as I did above, being sure to leave a space next to the *'s. Quote Link to comment Share on other sites More sharing options...
prab007 Posted June 15, 2015 Author Share Posted June 15, 2015 @Dirty Butter I dont see Rewritebase in the code. I have attached a copy of my seo.class.php. seo.class.php Quote Link to comment Share on other sites More sharing options...
Dirty Butter Posted June 15, 2015 Share Posted June 15, 2015 I apologize. I try out GitHub code for the next version from time to time - in this case what will eventually be 6.0.6. At one point since 6.0.5, this code was ADDED and then DELETED as apparently having unintended consequences.I'm sorry for your confusion, as it is all my fault. Quote Link to comment Share on other sites More sharing options...
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.