strange issue when updating packages

Hi,

i’m running into a strange little issue. i’ve just changed a revo (2.04pl) website hoster, of course, cleared the cache, changed all the pathes in the core/config file, everything work fine except that, when trying to update the installed packages or installing a new one, i get an error saying that it’s impossible to install or update them with the old core/packages path in the console message instead of the new one.

Well, i cleared the cache twice more, unlogged and relogged, nothing changed. Has somebody an idea where that old path could be stored for me to change it with the new one ?

another "symptom" that may help finding the solution is that in the tinyMCE link pop up, the tabs are filled with the smarty tags instead of their lexicon values (only for the links pop up, the img one works fine)
strange isn’t it ?

thanks for any idea, i’m a bit stuck

Did you do an upgrade install after changing the paths?

Hi Bob,

actually, i did an upgrade install (2.0.4 pl2) locally and on the former distant server to have a try at it and everything worked fine except for that little lexicon problem with tinyMCE links pop up.
About the path, don’t worry, i always save the config files and htaccess in a directory not to loose the changes when upgrading or transfering and i restore them or the needed changes after every upgrade.
i then transfered the whole "solution", db and files on the new distant server without making any changes (except, of course, for the config file)

but, funny enough, i was back here to say i’d found the trick ! it comes from the pref_workspaces table that stores Default MODx workspace, something more to change when swapping hosters and that i couldn’t find anywhere in the system tab items, neither in namespaces not in params (the first place i went when running into that wrong path error).
How i found it out ? i simply made a dump of my whole db and searched for the guilty string in the sql file. I should have thought about that before as i knew it was a storing issue...
I thought that everything was stored as showed in the manager {core_path} but it’s not the case for this peculiar string in the db.

Now, i can upgrade my packages without any problem, great isn’t it ?

I still just had to solve that tinyMCE issue. Strange as it may seem, the package manager said that i had the 4.1.2 installed (the first package upgrade that failed many times before i went here and ask the question) which is said to solve that modxlink issue.
Well, i tried an upgrade locally and it worked, except for some lang files, and the link pop up was clean again.
I then went and see on the distant server why it could not find the transport package to uninstall it... quite normal, it wasn’t there !
I really wonder how it could say that the release was installed without having even uploaded the package (a little bug, isn’t it ? ). Of course, is it necessary to say, each time I try something that fails, or even just sounds curious, i clear the cache and try again before going any further.
Well, let’s use a brutal solution, i’ve uploaded the package from my local server, uninstalled tiny thanks to that new package, reinstalled it but i’ve still got that modxlink lexcion issue.
Nevermind, as it works locally, i’ll find where the problem is.

Thanks for taking time to answer and let’s hope this little misadventure may help others, at least with this workspace string in the DB...

Quote from: virtualgadjo at Nov 01, 2010, 03:04 AM

Thanks for taking time to answer and let’s hope this little misadventure may help others, at least with this workspace string in the DB...

I must admit, I wouldn’t have expected this either - however there is a specific page in the manual explaining how to successfully move a modx site onto a different server (I came across it accidentally a little while ago while doing some background reading.)

http://rtfm.modx.com/display/revolution20/Moving+Your+Site+to+a+New+Server

Hi Andy,

you’re right and i’m that more unforgivable that i have made a pdf of this page to be able to refer to it any moment... the fact is, it had never been a problem before that package upgrade and i was surprised to find the path hardcoded. Nevermind, everything is ok now, i just have to solve that modxlink pop up problem, mustn’t be that hard

Have swing

Thanks for all the posts. They were very helpful. I took me a half a dozen times before I figure things out.

Sincerely,
monitium