Upgrade.SQL

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
12 лет назад
Trying to execute upgrade.sql to upgrade from 1.9 to 2.0. When I select "execute" I get this error:

Invalid object name 'Customer'.

Don't see Customer as a table or field. I see NOP_Customer.

The script reads "DELETE FROM [Customer]
WHERE IsSystemAccount=0

Don't see "IsSystemAccount either.

Shouldn't this be an easy execute?
12 лет назад
You need to install nopCommerce 2.00 (without sample data) to the 1.90 database before running upgrade.sql (this is step two in the Readme.txt file in the nopCommerce 2.00 - Upgrade Script archive).

Customer is the table name for customers in 2.00+ and Nop_Customer is the table name for customers in 1.90 and earlier. The upgrade script copies data from the 1.90 tables to the 2.00 tables and then drops the 1.90 tables from the database.

The following topic has a link to a video for upgrading nopCommerce 1.90 to 2.00:
https://www.nopcommerce.com/boards/t/11924/upgrade-from-19-to-20-video.aspx

.
12 лет назад
so I ftp the 2.0 files to my server without removing  the 1.9 files?

BTW, is that video supposed to have sound?
12 лет назад
This is the error I get when I attempt to install 2.0
12 лет назад
This is the error:

We're sorry, an internal error occurred that prevents the request to complete.
12 лет назад
Seems it is almost impossible to install nopCommerce on a GoDaddy shared server. Is there a similar package that you are aware of that will work on a Linux server with MySQL?
12 лет назад
rdub wrote:
so I ftp the 2.0 files to my server without removing  the 1.9 files?

BTW, is that video supposed to have sound?

You can backup and remove the 1.90 files since they will no longer be needed; although, you will need to copy the images back -see step 6 in Readme.txt.

I believe the video has text comments only.

rdub wrote:
This is the error:

We're sorry, an internal error occurred that prevents the request to complete.

To see the error details, you need to turn off custom errors.
Edit web.config and update the mode in the following line:
<customErrors defaultRedirect="errorpage.htm" mode="RemoteOnly">
from RemoteOnly to Off:
<customErrors defaultRedirect="errorpage.htm" mode="Off">


.
12 лет назад
This seems impossible. I now get the page not found error.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.