Dirty Butter

Your store looks OK on FireFox for me. But my browsers already have the correct javascript, etc. These are repeat customers who are having issues? If so, there's a good chance the problem IS with their browsers already having cached copies of some of the files that have changed. Try the fix Bsandall suggested to force a Customer Refresh and see if it works. I'll test your store on some more browsers and screen sizes to see what I get there.

What is the url of your store? No way for me to know if this is the issue, but it might be worth reading:

I have a sitemap.xml entry for /index.php?_a=saleitems that is legitimate. I do remember there was a code change some time ago that changed the logic so Sale Items were in the sitemap only if SOME of the store products were on sale. If ALL items were on sale, it did not show in the sitemap. And if NONE of the items were on sale, it did not show in the sitemap. I think this started as a Bsmither change he helped me with, but I'm pretty sure it ended up being added to stock code.

PHEW!!! Just call me DB There were a LOT of database table changes in 6.1.5 upgrade. So there were calls to the database tables that couldn't find the right fields when you were still working from the old cached files.

I've depended on Bsmither on the forum as long as I can remember. I hope he's enjoying his well deserved time away from us. I was hoping @havenswift-hosting or some other knowledgeable help would be along. I don't even understand your host's reply, let alone how to fix your issue.

Have you deleted the setup folder from the store root? Have you cleared all cache except images within CC and in your browser? The error message about "expects parameter 1 to be array, boolean" is a known notice that doesn't cause problems and I think will be fixed in a future version of CC. Delete the contents of the error log, too. It must be huge if it crashed.

Have you created the error log? What messages do you get when you try to make a Store Setting change? Are you logging into Admin with the correct admin_xxx.php link or still using your old bookmarked login screen?

Oh My!!! And you've checked that global.inc.php entries match the naming for your admin_XXX folder and admin_XXX.php file? What is the permission for global.inc.php in the properties of that file?

It's to be expected that it did the re-naming - 6.1.6 to 6.1.7 shouldn't have all these naming issues. Just so everything matches with the active, new versions, and what's in global.inc.lphp and all other useless admin named stuff is deleted - you are fine. Congratulations!!! That which does not kill us makes us stronger!

@Al Brookbanks ?

I have never offered skin changes to customers, so I'd never seen this issue before. I just played with your store, and I see what you mean. This definitely needs fixing. Maybe something session cookie related, like the site cookie acceptance message? @keat Please make a GitHub request on this.

You Are CORRECT. When you are sure you have a good install you will want to delete the old useless plain admin folder. The admin.php file is in the store's root - If you look in the includes/global.inc.php file you will see what that file was re-named to - admin_XXX.php. If you have both, you need to delete the plain old admin.php file. The image source folder in the setup files is empty. Your current images are safe. ANY edits you have made to source code in your old version WILL be lost. So if you made cosmetic changes to Foundation, they will be over-written. (If you are using any other skin, it won't be over-written, but you may have to make some skin changes to keep it working properly) If you have previously made edits to admin code (for instance, maybe Bsmither had helped you with some issue????) THOSE edits will have to be added back in to the upgraded files.That's why you need a good backup of your current files, so you can add your wanted edits back in. The 6.1.5 setup script WILL make some changes to your database, but your actual store data will still be there. Some of the table structure might change. That's why you need a good backup of your database before you do this - just in case something goes wrong. I completely understand your trepidation. You are being justifiably cautious to be sure you understand what's happening before you do it. But it's really not as bad as writing it all down makes it sound. If you have good backups, you'll be OK. If worse comes to worse, you can go back to your old version and pay to have it done for you. I'm sorry you are having to use my poor skills as your help on this. I know how to do it, but I'm not so good at getting it all down so it makes sense.

Our shop is in a subdomain. This section of the htaccess file seems to handle this. Ours redirects to plushcatalog, not index.php: Options +FollowSymLinks RewriteEngine On # # REDIRECT /folder/index.php to /folder/ RewriteCond %{THE_REQUEST} ^[A-Z]{3,9}\ /([^/]+/)*index\.php\ HTTP/ RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$ RewriteCond %{REQUEST_URI} !^/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$ RewriteRule ^(([^/]+/)*)index\.php$ https://dirtybutter.com/plushcatalog/$1 [R=301,L] # RewriteCond %{HTTP_HOST} ^www\.(([a-z0-9_]+\.)?dirtybutter\.com)$ [NC] RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$ RewriteCond %{REQUEST_URI} !^/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$ RewriteRule .? https://%1%{REQUEST_URI} [R=301,L] RewriteBase /plushcatalog/

Take a look in your global.inc.php file in the includes folder. Whatever the admin folder and file are named there is where you want your upgraded re-named?? admin folder and file code to go. IF you DO have re-named AND regular named admin.php and admin folder - Don't do anything with the original named ones, like from 6.1. When you have the install working properly THEN delete the old original named admin file/folder.

It involved lots of changes - https://github.com/cubecart/v6/issues/1546 I don't have the skill to spot just one place in GitHub to look for all the invisible recaptcha edits, plus the new file(s). I download the commit almost daily and use a file difference program to find what code changes have been made. I then merge those changes with code onto a hidden test site. When I'm comfortable that my test edits are working properly, I install on dirtybutterestates. If it is still all working correctly, I then merge the edits with plushcatalog. I've learned a lot doing it that way, but I have the time and inclination. Yes, I'm crazy.

The Invisible Recaptcha is one of the new features coming out in 6.1.6. If you can't wait you could find the beta code in GitHub and implement it now. https://github.com/cubecart/v6/issues/1483 A word of caution, however. I have some plugins on our plush catalog that will need edits before they will work with the invisible one. I have it in operation on our estates site, if you want to see it working.

I have our store name as the title on my homepage document. The seo_url for that document is automatically re-directed to the store sub-domain. I tried looking through all my .htaccess file, but I don't understand it well enough to know what code there tells it to re-direct to the store sub-domain.

Backup your database as well as your files. I download all the files, except for images, to my hard drive. And I make a copy of the database in phpMyAdmin, as well as a zipped backup. That way, if the worst were to happen - you can get back to your old version. That way you don't need to be so nervous about doing something new to you. I've been upgrading manually for a very long time, thanks to all the edits I have made to stock code that I don't want to lose.

Glad you worked it out.

That isn't anything like the experience I've had with him. Sorry to hear you've had problems.

Good for you! Care to share your code?

He's irreplaceable. Thank goodness there are some regulars here with a good grasp. I wish I were one of them.

Bsmither is not going to be around for the next few weeks, and I sure can't be of help with this. Hopefully someone else can.

Version 6.1.6 will still have the upgrade problem. But it has the fix that is supposed to finally solve all this issue, so upgrading to 6.1.7 and onward will be fine. There's usually a flurry of GitHub fixes right before a new release is coming out - and there's not been any of that of late. But there have been some major changes that I think most people will like in 6.1.6. You can get a sense of what is upcoming by going to GitHub and looking at what issues have been closed lately. Havenswift has mentioned (in another thread about the upgrading problems of late) that there are some security issues that have been resolved since 6.1.1.

I made a copy of the Google_Base and renamed it. There's also a place in the config file of the plugin where you have to match the re-naming. My Google_Base is not stock, either, as I said previously. If you're not comfortable yet with all this, it sounds like Havenswift's plugin would serve you better.