Update 1.0.2

Hello
Did a clean install of 1.0.2 - the first thing when opening the page is getting an alert telling me that AjaxSearch is obsolete - is this the expected behavior?

I’ve seen that on an upgrade when the files are not replaced in the assets/snippets/ajaxSearch/ directory. Some FTP clients don’t seem to get that right when upgrading sites. Cannot reproduce this on a clean install.

Hello Ryan,
It was a clean install on a new directory and new database - no leftovers from a previous install?!

Quote from: mmjaeger at Nov 05, 2009, 10:47 AM

Hello
Did a clean install of 1.0.2 - the first thing when opening the page is getting an alert telling me that AjaxSearch is obsolete - is this the expected behavior?

I can’t reproduce this behavior. Did you install the sample site and this alert occurs on the home page? It’s not clear from your description all the steps that were taken to cause this...

yes, indeed I included the sample site - upon first opening the site, I got that alert - now it seems to be o.k. - refreshed the page several times - opened it in Safari and Firefox??

I think just forget it by now.

By the way, Ryan, I’d like to draw your attention to this post: http://modxcms.com/forums/index.php/topic,38196.msg230779.html#msg230779

I know, layout is not a top priority - however, I think it is important when trying to convince potential clients of MODx - thanks again for all your hard work.

Quote from: mmjaeger at Nov 05, 2009, 11:12 AM

yes, indeed I included the sample site - upon first opening the site, I got that alert - now it seems to be o.k. - refreshed the page several times - opened it in Safari and Firefox??

I think just forget it by now.

I bet the previous version was cached by the browser, and force-refresh of the cache knocked out the cobwebs.

By the way, Ryan, I’d like to draw your attention to this post: http://modxcms.com/forums/index.php/topic,38196.msg230779.html#msg230779

I know, layout is not a top priority - however, I think it is important when trying to convince potential clients of MODx - thanks again for all your hard work.

Very important indeed, but that’s a perfect example of not having issues logged in JIRA slipping through the cracks. Can you please file a ticket so it doesn’t happen again? Thanks!

just to remind you to update the headline in the front page. 1.0.1 stands still.
(lol... like to bypass to forum’s bookmark, anyone? :p)

What’s the best way to install this without too much headache? I’m still in the process of developing our site, but I’d like to upgrade. Do I need to overwrite all of the files and then install it fresh or can I just replace certain files?

Questions on updating 1.0.0 -> 1.0.2
Scenario:
- i have a current installation in directory c:\xampp\htdocs\modx\good-1.0.0-installation
- i unzipped the modx 1.0.2 files into directory c:\xampp\htdocs\modx\modx-1.0.2
- now i want to update my good-1.0.0-installation
- if i open the install on my NEW 1.0.2 installtion (c:\xampp\htdocs\modx\modx-1.0.2) i don’t get an Update option (it is grayed out). I understand that this is because it IS a blank installation and there is nothing to update.

Questions:
- do i just copy over all of the directories over from the new modx-1.0.2 to my good-1.0.0-installation?
- if not, then what do i do?

Thanks,
Steve

Questions:
- do i just copy over all of the directories over from the new modx-1.0.2 to my good-1.0.0-installation?
- if not, then what do i do?

There are several ways documented in the Wiki on how to do upgrades. But, in this instance, you could:

• Copy over your custom assets files from your 1.0 install to your 1.0.2 install
• Copy your config.inc.php from your 1.0 install to your 1.0.2 install (config.inc.php is stored in manager/includes)
• Then, run the 1.0.2 installer in upgrade mode
• Once installed, review the settings in the Configuration Settings screen once you log back into MODx to check any path changes - mainly for the Resource Browser

That should give you an updated install in your 1.0.2 folder. Remember to back up your files/database before doing this in case you need to revert back to using your 1.0 install.