Issue moving C5 8.1 localhost site to testing site.
Permalink
I have a local instance of C5 8.1 running MAMP Pro on my localhost. I'm now moving the site to my test site so the client can review before launch.
My test environment is my personal website hosting withhttp://www.inmotionhosting.com. I have followed the instructions in the developers guide on moving a site. (https://documentation.concrete5.org/developers/installation/moving-a-site) However I'm still getting the following error.http://www.waynesstewart.com/bmc/...
I have updated my database.php file with the new db credentials, made sure I assigned a username to the database and cleared the cache folder in application/files/cache and still the error persists.
Any help will be greatly appreciated.
My test environment is my personal website hosting withhttp://www.inmotionhosting.com. I have followed the instructions in the developers guide on moving a site. (https://documentation.concrete5.org/developers/installation/moving-a-site) However I'm still getting the following error.http://www.waynesstewart.com/bmc/...
I have updated my database.php file with the new db credentials, made sure I assigned a username to the database and cleared the cache folder in application/files/cache and still the error persists.
Any help will be greatly appreciated.
Is waynes14_bmc the database on your test site's server? And if so, does the table Packages exist (case sensitive)?
Yes, exported the DB from my local machine and imported it into the new bmc db. See attachment.
The problem is that all of your table names are lowercase. This happens on windows a lot, if you search the forums there are several solutions.
Ok. Cool. Thanks. I'll do some research.
I used the migration tool plugin in and that did not work. Then I manually tired and renaming all the tables with a SQL query but still did not work all that well. I talked to the web hosting for the live site and they said if I have any issue they will help me make sure that case sensitivity is correct. So I will go with that solution for now and keep building out the site locally.
