Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

MySQL5 messed up the index site


Route 66

Recommended Posts

Hi there, this is my first post:

I just had a server upgrade to MySQL5 and that messed up the index site and the menu.

I read that oscommerce have problem with MySQL5, is there anyone that know where I can find all the statement that need to be exchanged?

Link to comment
Share on other sites

We need to know what version of osCommerce you are using. There is no version 1.28. Go log into your Admin -> Tools -> Server Info and find the version number.

 

Regards

Jim

See my profile for a list of my addons and ways to get support.

Link to comment
Share on other sites

No. Please follow instructions.

1. Log into your store's Admin.

2. Click on Tools.

3. Click on Server Info.

4. Read the version of osCommerce listed on that page.

 

Regards

Jim

See my profile for a list of my addons and ways to get support.

Link to comment
Share on other sites

2.2 MS2 was released in 2003. Upgrading that would be very difficult, even if you could find all of the intermediate versions. The only practical solution is to install a copy of 2.3.3 and import your customer and product database tables.

 

Regards

Jim

See my profile for a list of my addons and ways to get support.

Link to comment
Share on other sites

Thaks kymation - I understand you, but right now I’m into fixing the bugs that MySQL5 created on the index page, that must be possible (like the left join, issue)

so I’m thinking what else of the statement is overruled?

Link to comment
Share on other sites

There is an upgrade package from 2.2 MS2 to 2.2RC2a in the Addons section. From there you use the upgrade instructions in the 2.3.1 package, then 2.3.2, then 2.3.3. This will be a tremendous amount of work. It will leave you with a site that has all of the security and bug fixes, and all of the compatibility fixes for PHP 5.3 and MySQL 5+ that are in the latest version of osCommerce. It will not have all of the improvements that let you use the newer 2.3.x Addons. It will also not have the fixes to any old Addons that you have applied, so those may still break on your new server.

 

This is still not a practical solution.

 

Regards

Jim

See my profile for a list of my addons and ways to get support.

Link to comment
Share on other sites

There are many SQL statements that will have to be modified. There is no list. You'll have to find and fix each one. Then there are all of the security holes that will need to be found and fixed. Then there are all of the code bugs that will need to be fixed. Then you need to find all of the deprecated PHP functions and replace all of those.

 

By the time you have done all of this, you will have invested much more time and effort than would be required to start over with a current version. Don't let me stop you from doing this the hard way though.

 

Regards

Jim

See my profile for a list of my addons and ways to get support.

Link to comment
Share on other sites

The only info you gave so far about your problem is, that index page and menu are "messed up"

 

Based on this, I would not be able to identify any sql statement

 

Maybe you need to give more info? Do you get any errors or something?

Link to comment
Share on other sites

While there are incompatibilites with MySQL 5 in older versions of osC, are you sure your problems aren't related to PHP 5? There are lots and lots of code changes for that (one or two add-ons to help with the core code, but most of it is On Your Own, particularly for all add-ons). PHP 5.3 introduces a whole bunch more (deprecated functions) to fix. The only problems I recall moving to MySQL 5 were the JOIN versus comma operator precedence problems. Basically, you have to go through all SQL statements in the code, looking for JOIN or join, and make sure that any code containing a , between FROM and the

JOIN is within parentheses (). I seem to recall that only a handful really mattered. Or, you can just run the store and wait to see "1054" errors which will pinpoint the queries that need to be fixed.

Link to comment
Share on other sites

Thanks MrPhil. I know that they don’t run PHP5.

I’ve solved the left join issues, and this is why I’m asking for other statement that need to be changed after the MySQL5 upgrade.

 

Anyone know what other old osC statement that are outdated?

Link to comment
Share on other sites

Off the top of my head, the only problems I recall are the JOIN vs. comma operators. If you've fixed all those, AFAIK you should be OK with MySQL 5, at least if your starting point is no older than osC 2.2 MS2. I suppose it's possible that there are MySQL incompatibilities if you go back further than that, but I've never played with code that old.

Link to comment
Share on other sites

Your images appear to be generating 403 errors. By any chance did someone install "hotlink protection" on your site and forget to whitelist your domain? Are you able to directly bring up the images in a browser? Do the image links show the correct location?

Link to comment
Share on other sites

Hi MrPhil, this happened with the MySQL5 server upgrade, the links on the image is pointing to the correct location if this is what you mean, but the image/link that shows are now not the one that it should be?

 

Some code have now been overruled and that’s why I’m asking for other outdated statement like the “left join”.

 

Another thing that’s messed up is where using the subcategory, at the showing link it should only display 4 pictures, not all of the below things.

http://pedaler.eu/webshop/catalog/index.php?cPath=59

 

It seems that the overall problem is that MySQL5 bugging this osC structure, and why I’m curious about outdated code?

Link to comment
Share on other sites

Hi,

Do not know but when MR Phil said hotlink protection I noticed you have a script disabling right click

<!-- cer fjerner

 

<script type="text/javascript">

/////// START DISABLING RIGHT CLICK \\\\\\\\\\\\

 

would maybe remove when debugging just in case !

 

 

regards

John

To improve is to change; to be perfect is to change often.

 

Link to comment
Share on other sites

Your html contains instances of this piece of code

 

<img src="images/"

 

which is incomplete. It should be more like

 

<img src="images/mypic.jpg"

 

The image filenames are not being retrieved, but your site is so heavily modified that I cannot guess where they should be. Start by looking at the products table, and specifically at the products_image column, to see that all is well.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...