Page 1 of 1
Cant add UDT after installation move
Posted: Sun May 17, 2015 2:20 pm
by wmdvanzyl
I moved my brand new 1.12 install from a cmsms subdirectory i initially installed it into, to the root public_html folder on the server and since then i have been unable to add UDT's.
It gives an error stating that it could not find the path
Code: Select all
domain.ext/admin/adduserplugin.php was not found
But the file is there at that location. Is there somewhere else where the admin directory path is located that i need to update for it to correctly find the file?
Re: Cant add UDT after installation move
Posted: Sun May 17, 2015 6:01 pm
by Dr.CSS
We need way more info to really help you...
Did you do a checksum to see if everything actually made it to the server..?
Re: Cant add UDT after installation move
Posted: Mon May 18, 2015 2:46 pm
by staartmees
A quick cure for the problem is to install your cms again.
BUT VERY IMPORTANT:
First make a backup of your current database
Upload a fresh cms and start the installation
at step 5 uncheck 'Create tables' and 'Install sample content and templates'.
Re: Cant add UDT after installation move
Posted: Mon May 18, 2015 7:49 pm
by wmdvanzyl
Dr.CSS wrote:We need way more info to really help you...
Did you do a checksum to see if everything actually made it to the server..?
Hi Dr - that's very true, i was just wondering whether there are general issues with moving an installation. For example, perhaps you are supposed to update some setting somewhere or some file somewhere. I updated the .htaccess file and checked the config.php file. Just not sure of any other places where it is suppose to be updated. I also cleared cache. And yes, all the files were there at the start.
staartmees wrote:A quick cure for the problem is to install your cms again.
Actually, since this is a brand new installation, the judo solution is just dump everything and reinstall - even the database. I don't want to waste time debugging something that can be fixed by reinstalling, but i also want to learn how to successfully move an isntalltion for future reference.
EDIT: Turns out the issue was with the UDT and not CMSMS! Weird... never knew an error in a UDT could give a result like this...