[Upgrading MySQL 5.1.73 to 5.5/5.6]

Thank you bsmither

I am wondering about how far to go with the upgrade

Is there anyone that can confirm whether a standard CubeCart installation works with MySQL 5.6?

[Upgrading MySQL 5.1.73 to 5.5/5.6]

I have CubeCart v6.1.14 installed and my server is currently running MySQL v5.1.73 (even though cubecart.com says 5.5 minimum)

I understand that you should not upgrade directly from 5.1 to 5.7, but should go 5.1 to 5.5, then 5.5 to 5.6, then 5.6 to 5.7.

However Plesk does not yet support 5.7, so I won’t be going that far.

1/ What do I need to do with my CubeCart database if my server is upgraded from MySQL 5.1 to MySQL v5.5?

and then...

2/ What do I need to do with my CubeCart database if my server is upgraded from MySQL 5.5 to MySQL v5.6?

[File Backups within Maintenance]

Manually upgrade what? The currently installed version is 6.1.14.

[File Backups within Maintenance]

I have already upgraded using the auto-setup tool
(as a known issue I’m puzzled why it wasn’t squished at the same time)

I assume this is source code issue rather than a setting or database value

Is there a specific directory that I can swap out?

e.g. perhaps "sources/maintenance/*" from the current version of source code?

Thank you in advance

[File Backups within Maintenance]

I have found an error affecting two different CubeCart installs with different hosts, so I think this may be a bug

When choosing the standard Files Backup button, with checkboxes off, the backup proceeds and is created but then it tries to find this file...

/admin_ZZZZZZZ/sources/maintenance/indexbackup.inc.php - not found.

Where ZZZZZ is a novel admin location - it doesn’t appear to have been used before and doesn’t match the current.

In one situation (it may have been a checkbox difference) I was warned about cross-site scripting on the dashboard page

It appears as is something is not going well for the Files Backup feature, and could do with looking at by the software development team

(I am not that bothered personally, there are other backup methods available)

[How to Fix Database Index?]

Thank you - I have now cleared all the warnings from the maintenance section.

It was time consuming, but I suppose it will now mean the server resources are used more wisely.

I will just keep my fingers crossed that this upgrade issue is a one off, and auto upgrades will start working again.

...now onto my next CC install for more of the same!

[How to Fix Database Index?]

I now have the database warnings down to the following:

CubeCart_category.cat_parent_id has no key set. Expecting KEY.
CubeCart_inventory.popularity has no key set. Expecting KEY.
CubeCart_inventory.status has no key set. Expecting KEY.
CubeCart_reviews.approved has no key set. Expecting KEY.
CubeCart_seo_urls.item_id has no key set. Expecting KEY.
CubeCart_seo_urls.type has no key set. Expecting KEY.
CubeCart_sessions.customer_id has no key set. Expecting KEY.
CubeCart_sessions.session_last has no key set. Expecting KEY.

and

CubeCart_currency.currency_id has a key type KEY but expecting PRIMARY.
CubeCart_modules.module_id has a key type KEY but expecting PRIMARY.

I have taken some screengrabs and wonder whether you can give me a few pointers on what to enter. On the first image I have clicked on the Go button you suggested. The other two look a bit trickier because they are about changing something rather than add/delete. Someone at CubeCart might also want to make a note about the warning for using the table field name of "default".

[How to Fix Database Index?]

Thank you. The explanation helps. But where do I click? Are there any options I will be asked about?

[How to Fix Database Index?]

Okay, and for the benefit of anyone else following this, here is a new screengrab.

I have used a red arrow to show you where to find this panel. The other two rows are now removed because I clicked on the word ‘Drop’ (just in case anyone is looking for a delete button). In my CubeCart admin panel this error is now cleared.

Here is the other type of error:

CubeCart_category.cat_parent_id has no key set. Expecting KEY.

And my screengrab... how do we fix this sort, there are no onscreen prompts?

 

[How to Fix Database Index?]

Just found something. Just above the Information infopanel at the bottom is the word Indexes, which when you click on opens up some details...

 

[How to Fix Database Index?]

I am using phpMyAdmin and looking at the table - CubeCart_admin_user

There are 23 database fields, starting with admin_id

At the bottom are two infopanels - Space Usage and Row Statistics - nothing about column indexes

What am I looking for? I can see the data, I can see the structure.

[How to Fix Database Index?]

Okay, so I have manually upgraded to v6.1.5 and I can see the database now has some issues - this was to be expected.

However, I wasn’t expecting the link to a "database checker tool" to be just a link to a discussion elsewhere and the comments by Al Brookbanks aren’t much help... “Please use a tool such as phpMyAdmin to make any required changes” ... erm, yes, so how exactly?

There appear to be two types of error message.

This is what I am looking at:

CubeCart_admin_users.admin_id has a key type KEY but expecting PRIMARY.
CubeCart_category_index.id has a key type KEY but expecting PRIMARY.
CubeCart_category_language.translation_id has a key type KEY but expecting PRIMARY.
CubeCart_category.cat_parent_id has no key set. Expecting KEY.
CubeCart_currency.currency_id has a key type KEY but expecting PRIMARY.
CubeCart_image_index.id has a key type KEY but expecting PRIMARY.
CubeCart_inventory_language.translation_id has a key type KEY but expecting PRIMARY.
CubeCart_inventory.popularity has no key set. Expecting KEY.
CubeCart_inventory.status has no key set. Expecting KEY.
CubeCart_modules.module_id has a key type KEY but expecting PRIMARY.
CubeCart_order_summary.cart_order_id has a key type KEY but expecting UNIQUE KEY.
CubeCart_reviews.approved has no key set. Expecting KEY.
CubeCart_seo_urls.item_id has no key set. Expecting KEY.
CubeCart_seo_urls.type has no key set. Expecting KEY.
CubeCart_sessions.customer_id has no key set. Expecting KEY.
CubeCart_sessions.session_last has no key set. Expecting KEY.
CubeCart_transactions.id has a key type KEY but expecting PRIMARY.

 

[No prompt to upgrade in Admin section]

Does the ‘Force Upgrade’ button request the latest version?

(it’s catch 22 - it asks me if I am sure to continue but how do I know what it will do??)

[No prompt to upgrade in Admin section]

My last upgrade took me to version 6.1.1 on 14th-Nov-2016

My admin folder is on a custom URL - I have php 7.0.16 - ZipArchive check has passed.

Dashboard prompts me to upgrade but the upgrade/maintenance section says I have the current version. I can see other posts talking about stalled upgrades, upgrades failing, database crashes and things like that and wonder whether it may be best to wait a while for these issues to be worked out. Or should I put myself through the time and effort of a manual upgrade. All previous admin section upgrades have gone well so I am a but surprised to see I am now 4 updates behind, and yet there is no prompt to upgrade. A bit of a puzzle.

[PayPal-1.0.5.zip]

The Zip download for PayPal-1.0.5.zip is empty and the Flash token doesn’t work.

There is just an index.php file containing copyright information

https://www.cubecart.com/extensions/payment-gateways/paypal-standard

[PHP v7]

Has anyone tested Cubecart with PHP v7 ?

[404 in Basket Iframe when adding from category view]

bsmither, just wondering if you have any thoughts on how to fix this?

[404 in Basket Iframe when adding from category view]

kurouto/templates/content.category.php - line 40

{if isset($PRODUCTS)}
  {foreach from=$PRODUCTS item=product}
<form action="{$VAL_SELF}" method="post" enctype="application/x-www-form-urlencoded" class="addForm">

 

classes/gui.class.php - line 203

       //Assign common GUI parts
        $GLOBALS['smarty']->assign('VAL_SELF',        currentPage());

 

Maybe gui.class.php is out of date? - line 13 says...

 * CubeCart is NOT Open Source.

[404 in Basket Iframe when adding from category view]

Add category to product URL path? = no

Add subcategories to category URL path? = yes

custom url is formed as domain/directory/product (.html)

category url is formed as domain/category-name (.html)

directory is not the same words as category-name

[404 in Basket Iframe when adding from category view]

Also discovered that the final breadcrumb link is also missing the full path of the custom URL

The left hand navigation link is correct

[404 in Basket Iframe when adding from category view]

Already tried it but did it once more to be sure... no effect.

[404 in Basket Iframe when adding from category view]

"custom-name" doesn’t contain any special words that are likely to affect processing.

I have just tested with a different category that ends with /phrase.html and that is affected in the same way, so it affects numbers and letters for the page name

I think this is a URL nesting issue, the custom URL has a path that is longer than just a page name, and the form script is not pulling in the full custom URL

For clarification I use the URL structure of /category/product.html so that Google sees them as a distinct directory, and it helps with SEO (which is the whole point of having a custom URL).

This only appears to be an issue in category list view.

[404 in Basket Iframe when adding from category view]

Category list has a custom URL of this format:

xxdomainxx/custom-name/40-45.html

When adding to basket the whole side column fills with a formatted store page and a 404 error

When inspecting the page source the form submission is to the wrong URL like this:

xxdomainxx/40-45.html

Store version is currently v6.0.8

Does anyone know how to fix this?

[Hacked content detected]

I was hacked by the same people - https://forums.cubecart.com/topic/50393-upgrade-v5-to-v6-and-clean-install/

I did not need to submit a reconsideration request - Google spotted the cleanup and removed their may be hacked notice

Removing the snippet is essential - I didn’t do this first time around and they got back in.

[Upgrade v5 to v6 and Clean Install]

Fortunately I did a backup after completing my purge/upgrade, so I have something decent to fall back onto.

After completing the rollback I will delete the snippet, switch to a new skin and dispose of the old, and then carry out a visual review of what is stored in the database.

Thank you bsmither