phpfreak

LOL, so the export f'd up without error message or even a single sign of issue. I dropped all of the tables and ran the import and less than half of the tables were actually properly stored in the the export. Lost some data, but the site is up and running. Well, I'll be contacting their host and finding out if they have a backup we can revert to and also what we can do to prevent it from occurring again.

REPAIR TABLE did not have any effect and returned errors stating corruption, good call. I deleted the table `eua_settings`and replaced it with the copy I had on my testbed. The constant's are fixed now, which is an improvement. Other tables are having the same issue, so I will need to replace all of the tables likely. re-running the install will destroy all of the data, correct? I'm not to keen on updating the application quite yet, would like to give it a few days/weeks to have the more serious users test it. Nothing personal, just a practice I have for updates. I appreciate the help, thanks.

Thank your for the quick response. This may not be a problem with phpVMS at all then, it may be a problem with the host my clients website is being hosted off of. I'm not familiar with this application really at all yet, just a little with the API (I'm building a module for them). So I immediately went into the db though phpMyAdmin which is provided via cPanel by the host. When I click on the table `eua_settings`I get this error: I understand entirely if you do not desire to provide support for this issue, doesn't seem to be a phpVMS issue. I'm going to do some of my own research and if nothing turns up I'll talk to the guys at phpfreaks. com again, thanks for the speedy reply.

I'm working on one of these phpVMS sites and I'm not sure if my client updated the site or what he did (communication can be quite delayed) and we're getting this message: A few things going on here: 1. Note the double / after "public_html" in the template file url. 2. Note that Constant "CURRENT_SKIN" is not defined apparently and the constant's name is output. odd result if you ask me. I defined it in the core/codon.config.php and it fixed that problem which revealed to me another... 3. Constant "SITE_NAME" is not defined and is also being output simply as the constant's name. 4. I'll venture a guess that the problem with $pilots is due to the other variables being screwy. 5. Logging in does not work, also will guess it has something to do with the other problems. Any help appreciated.