Argh! Moved MODx Revo rc-4 installation from sub-folder to root.

I have moved a MODX 2.1.0-rc4 installation inside a sub-folder to the root.
Now I can’t update or remove Extras with Package Management I get error messages that it can’t find the old sub-folder.
Also I made a MySQL database backup and found references to the old sub-folder.

What can I do to clean things up?

Thanks!

Follow these instructions the next time:
http://rtfm.modx.com/display/revolution20/Moving+Your+Site+to+a+New+Server
(Yes, also when moving from a sub-folder)

Most likely the workspaces table is still referencing the old path.

But you may also want to make sure other config files on the server have been updated.

Yeah I would check in core/config/config.inc.php as a start.

Thanks Mark and Bridgecourt,

I already have follow these instructions... except the work/namespaces will try it right now!

System settings and namespaces are not reflecting the old sub-folder.
Is there an other way to clean things up?

In the error log:

[2011-05-18 20:07:44] (ERROR @ /connectors/workspace/packages-rest.php) Could not transfer package wayfinder-2.3.1-pl.transport.zip to /domains/mywebsite.eu/DEFAULT/sub-folder/core/packages/.

At the bottom of mySQL dump I have this line:

INSERT INTO `modx_workspaces` (`id`, `name`, `path`, `created`, `active`, `attributes`) VALUES
(1, ’Default MODX workspace’, ’/domains/mywebsite.eu/DEFAULT/sub-folder/core/’, ’2011-04-14 07:59:01’, 1, NULL);

Can I just remove the sub-folder and import it back with phpMyAdmin

INSERT INTO `modx_workspaces` (`id`, `name`, `path`, `created`, `active`, `attributes`) VALUES
(1, ’Default MODX workspace’, ’/domains/mywebsite.eu/DEFAULT/core/’, ’2011-04-14 07:59:01’, 1, NULL);

Yeah - just update where-ever paths are wrong. In the DB, namespaces etc.

And clear the cache after that.

Thanks Mark, will do!

I have one error when importing to phpMyAdmin, should I fix this?

Fout

SQL-query:

--
-- Gegevens worden uitgevoerd voor tabel `modx_access_context`
--
INSERT INTO `modx_access_context` ( `id` , `target` , `principal_class` , `principal` , `authority` , `policy` )
VALUES ( 1, ’web’, ’modUserGroup’, 0, 9999, 3 ) , ( 2, ’mgr’, ’modUserGroup’, 1, 0, 2 ) , ( 3, ’web’, ’modUserGroup’, 1, 0, 2 ) , ( 13, ’en’, ’modUserGroup’, 1, 9999, 1 ) , ( 12, ’en’, ’modUserGroup’, 1, 9999, 2 ) , ( 11, ’de’, ’modUserGroup’, 1, 9999, 1 ) , ( 10, ’de’, ’modUserGroup’, 1, 9999, 2 ) , ( 19, ’mgr’, ’modUserGroup’, 1, 10, 8 ) , ( 16, ’web’, ’modUserGroup’, 1, 9999, 1 ) , ( 18, ’mgr’, ’modUserGroup’, 1, 9999, 1 ) , ( 20, ’web’, ’modUserGroup’, 1, 10, 8 ) , ( 21, ’de’, ’modUserGroup’, 1, 10, 8 ) , ( 22, ’en’, ’modUserGroup’, 1, 10, 8 ) ;

MySQL retourneerde: Documentatie
#1062 - Duplicate entry ’1’ for key 1