Dirty Butter
-
Posts
6,634 -
Joined
-
Last visited
-
Days Won
139
Posts posted by Dirty Butter
-
-
3 minutes ago, bathroomboy said:
Sorry do not know how to check the " ALTER TABLE `CubeCart_system_error_log` ADD INDEX (`time`); #EOQ "
I don't know how to explain to you how to check that one. But at least we know the database is at least on 6.1.6 - more than likely on 6.1.7.
BUT I'm not so sure about how you stand as far as admin folders and admin files are concerned.
Take a look in includes/global.inc.php and see what the name are for admin_XXX folder and file there. THOSE are the admin folder and admin file that should have the 6.1.7 files in them. The directory that has that includes folder in it is your store root.
Look in your correctly named admin_XXX folder for \skins\default\csrf.inc.php. Is that file there? THAT is the GOOD admin folder. DELETE any other admin named folder at your store root.
Your GOOD admin_XXX.php file will have a copyright date of 2017 on line 6. DELETE any other admin.php files in your store root.
Refresh our memory - is your store on SSL? Was SSL working properly on 6.1.1??
-
@garywhitling What CC version are you on? Is this a new install or an upgrade? If upgrade, from what?
-
42 minutes ago, havenswift-hosting said:
Reverting to 6.1.6 would not solve your problems and in fact would cause a lot more !
I agree - don't try to go to 6.1.6 - and if you can hold off on reverting to your old version for a bit hopefully we can spot the problem.
-
Before you try to revert -
1. Be sure you have cleared all CC cache except image AND your browser cache - control/F5 usually.
2. What is showing in the error log now that the sanitize file is the 6.1.8 code?
3. Take a look at the store root level - that's the one with the includes folder in it.
Do you see more than one file/folder with admin in it?
Also, check your database to see if your CubeCart_option_assign table has a column named option_default. That would be one of the last obvious changes to the database.
The last two database changes in 6.1.7 were below, if you know how to check to see if they are there.
ALTER TABLE `CubeCart_system_error_log` ADD INDEX (`time`); #EOQ
ALTER TABLE `CubeCart_system_error_log` ADD INDEX (`read`); #EOQ -
I use the AddThis plugin, and it's still working properly. Is your skin stock Foundation?
-
I've wondered before about this, but never bothered me enough to ask. I have no idea what it is for, as we have been able to login as a specific customer for some time now.
-
Here's the link to the whole 6.1.8 sanitize.class.php file.
https://forums.cubecart.com/topic/52519-resolved-paypal-pending-error/?do=findComment&comment=226602
-
Be sure you have ALL your files backed up and your database, too.
After you have the 6.1.7 zip uploaded and extracted to the store root:
Then in your browser run your store url/setup. Be sure to choose upgrade. Make sure there is no warning about a server setting that would be an issue. That's not likely since you are on 6.1.5.
When you finish, the last screen will caution you to use the admin_XXX file and folder naming. And to login with https if you use SSL.
-
Strange!!! I just tested on a stock test store with yesterday's commit. The subscribe/unsubscribe works from all locations, including the footer.
-
I use https://www.cubecart.com/extensions/plugins/mailchimp
I use the plugin on plushcatalog. SemperFi modified it for a price to also automatically trigger an Automated email campaign.
I use the MailChimp embedded code based on what MC provides on the estates collectible shop. As far as I can tell both stores correctly subscribe correctly.
-
I tried it again on stock store on yesterday's commit. The quantity of a product was not added back to stock when I manually deleted it from a Processing order.
-
It should be possible to use the descriptions as a place to designate as retail or wholesale, as well as the different product codes. That would add to the differences in the two products. You should be able to tell if Google fusses by checking the Webmaster Tools>your store>Search Appearance on the left column>HTML Improvements.
-
1
-
-
Have you made a post about your issue with 6.1.7 Mailing List @SergeiG? I don't remember seeing it. I use a MailChimp plugin, so I can't easily test it for you.
-
Has this ever worked properly for you? Have you made any CC changes or host changes lately? Is it properly showing as Processing? Is it tangible or digital product? Can we have your store url?
-
What version of the PayPal plugin are you using? It has been so long since v4 was supported, I can't help but wonder if the newest PP plugin version would be compatible. I do NOT know anything about v4. When you say alternate, do you mean it's in the gateway or plugin folder?
-
Al closed this as NOT being reproducible. I'll test again. Please do so as well.
-
May we have the url for your store? It's a little confusing, but the second box on the ssl tab should have the http:// version of your store url.
If you have that part right, then it may be something on your page is not secure. It might be an image or some link that is to http://.
-
Welcome to the forums @Darren Rogers!
There is a public folder in 6.1.7 files that should do what you want.
-
GREAT! I removed your screenshot, because the url revealed your admin_XXX naming.
-
Here's a link to the minimum requirements to run CC:
https://www.cubecart.com/hosting-requirements
It looks like your current MySQL is not going to work with v6. That may be why you currently only have a v5 install available.
-
What was your previous version that also had this issue?
Do you have the error_log? If so, what do you get when you attempt this?
Also, please check the permissions on templates, images, and admin folders.
-
Have you posted on the 3rd party forum? http://www.cubecartforums.org
-
OK, if you don't want extensive changes:
You're going to have to play around with that section copied over to cubecart.default.css along with the footer section.
footer { background-color: #000; color: #fff; } footer h3 { color: #fff; }I'm not the one to tell you how to do it, though. Sorry.
-
I searched in the language definitions.xml file and found this in <group name="common">:
<string name="description_short" introduced="6.0.5"><![CDATA[Short Description]]></string>
Is that what you needed?
Also, if you add {debug} temporarily to the bottom of the file you are trying to modify and then refresh that page on the front end - you will get a popup of all values available to that file. Keep the popup, but take the debug off as quickly as possible - otherwise your customers will see the popup.
Upgrade assistance
in Install & Upgrade Support
Posted
DON'T do that!!
If you still think it didn't install correctly somehow - use the Maintenance>Upgrade>Restore Current Version
If you don't mind spending the month's worth of support - that's sure the easiest way to get this fixed. Sorry I couldn't help.