Upgrading to Beta 3

[met00]

Poor ridex...

There seem to be just two things that set him off... people changing fallback files rather than just creating a new template directory and changing the files there, and then using the balance from fallback unchanged.

and

multiple images with people who don't understand how to make mopics work.

So, suntech, your next question MUST be... "Why doesn't the admin have a multiple image upload capability when you are adding a product?"

[ridexbuilder]

What a stirrer!

[suntech]

Ok I uploaded the new files and now I am trying to run the upgrade SQL and I get this error:
#1060 - Duplicate column name 'information_url'
Any Ideas?

MET00, just saw your post. Pretty funny however I figured out mopics a while back.

[michael_s]

Manually update using the sql file from the line after the error. So open the upgrade sql file and copy from the line after the error to the last line of the file. Paste it into the sql query window of phpmyadmin (should be provided by your host) and execute the remaining queries on your db.

There are a couple of lines in the update script that do not take into account that some of the updates are auto-generated by osCmax if you change a few settings.

[ozstar]

I would like to transfer categories and products from an older oscOMMERCE to the new Beta3 as a test.

What is the easiest way to do this please.

Be gentle!!

(This is not the same issue I posted earlier as that was from an older oscmax)

Thanks

[met00]

download old osc with ezpopulate

put 1 product in 2.5 beta3

download with ezpopulate

match up the columns between the two spreadsheets copying data from the old to the new.

upload the new ezpop spreadsheet with the updates to the 2.5 beta

If there are columns that do not have information in them from the old store, then you MAY have to populate them.

{upload the images to the correct directory on the new store as well}

That's about the fastest and easiest way I know how.

Now be ready for a problem. All the product ID will have changed. This could be VERY damaging to you in google. The UGLY option to over come this is to use your mysql tool to dump the data, and then go through that file and make wholesale changes to the inserts where you need to because of a field change, etc. This will maintain the product IDs, but is a much more time consuming process.

[ozstar]

MMmmm.. Got to get my head around this one...