release files

Quote from: shamblett at Feb 28, 2010, 03:34 PM

You should be OK going from old(revolution branch) to new(2.0 branch) although admittedly I’ve not tried this lately. As revo matures into a GA release Provisioner will be updated to match this at which point we will have a stable baseline, until then you may get a few funnies depending on how far apart the installs are in time.

I’m a little confused

"Revolutin brach" is the version that I can download from modxcms.com site (Revolution 2.0.0-RC-1 (expected Spring 2010)

"2.0 branch" is new version with all fix/updates from last version


The 2.0 is final and "on working" version with all updates

Is it OK?

The 2.0 is final and "on working" version with all updates

Yes, the ’bleeding edge’ if you like and as such is undergoing continual testing as new features are added/bugs fixed, some of these features may alter the JSON data returned by the processors to the Provisioner component, which at the mo wouldn’t know this and so might not behave as expected.

Ok! now I download

http://svn.modxcms.com/svn/tattoo/tattoo/branches/2.0/

that is the "on working version", with daily/weekly updates and with new features/bugs/fixes etc....

(OK??)

and I’ve and installed version of Revo (downloaded from modxcms.com) with documents/chunks/snippets created


now.... what I have to do for use update version of Revo with my documents?


Thanks thanks thanks thanks for help me!

Just copy the new files over the old files and run setup/, choosing Upgrade.

Quote from: OpenGeek at Mar 01, 2010, 04:35 PM

Just copy the new files over the old files and run setup/, choosing Upgrade.

oky!!!

I’ve seen that in my svn version I’ve a "_build" folder.... Do I’ve to build the project before overwrite my old (revo) version?? or I’ve only simply to overwrite my version old-revo version (without consider _build folder)?

Thanks

I’ve made other tests

I’ve seen the "_build" folder....my question is this: if I’ve an existing version of (old) Revo and I want to install/activate new version (downloaded from SVN), Do I have only to overwrite my old-revo version with new Revo files without consider _build folder?

Thanks

Build the SVN export (php transport.core.php), then copy all the folders over your old revo installation and run setup (upgrade).

(you can remove _build folder, it’s not needed)

Quote from: oori at Mar 02, 2010, 08:29 AM

Build the SVN export (php transport.core.php), then copy all the folders over your old revo installation and run setup (upgrade).

(you can remove _build folder, it’s not needed)

This action will also update my existing "old Revo" DB ... adding new features/fix/updated??

only a final question:

in transport.core.php and transport.data.php I show something like this

if (!defined(’XPDO_DSN’))
define(’XPDO_DSN’, ’mysql:host=localhost;dbname=modx;charset=utf8’);


if my DB has another name Do I have to modify these information???

There are other things to check/modify in these 2 files?? (only in these 2 files??)

One thing.... only because I don’t want to lose all my records in old_revo

modx is the folder of my old_revo

I download new version of revo
I generate the core package zip

now, I want to use the records that I’ve in my old_revo with new revo files and new revo DB

what I have to do??


copy all new revo files in my modx folder (old revo) and run setup????


or


run new revo setup from new folder and point to the same DB of old revo??


Thanks

please can you reply to this my final problem??


One thing.... only because I don’t want to lose all my records in old_revo

modx is the folder of my old_revo

I download new version of revo
I generate the core package zip

now, I want to use the records that I’ve in my old_revo with new revo files and new revo DB

what I have to do??


copy all new revo files in my modx folder (old revo) and run setup?Huh


or


run new revo setup from new folder and point to the same DB of old revo??


Thanks