Support/Comments for Provisioner 1.9-beta

Note to all Provisioner users: Just to be clear, when using Evo Import function, when it says "Your site will be overwritten" it MEANS it! Importing into a different Context does NOT mean other contexts are preserved - your ENTIRE site will be overwritten!!

Luckily not much damage was done when I tried it, but if there was damage it’d be my own fault - there is a warning after all, and now here’s another one for you

Quote from: shamblett at Apr 19, 2011, 01:32 AM

OK, lets start ruling stuff out, I have a test site here bitez.dyndns-web.com/modx, this has the revogateway installed and works. I’ve PM’d you with the login details, login to this, see if you get any errors, if not see if you can see the content, if not the prob is your revo install, if you can the prob is your remote evo install.

Can you PM me the login for this so I can test it as well? Or email it to [email protected].

Thanks

Thanks for the info but I’m still getting the same result with an actioning screen the nothing.

OK, check most things taht have been mentioned above, especially the access to the tmp file directory etc.

I just upgraded my dev site to Revo 2.1 and got this error message:
The site import failed - Failed to remove elements - modKeyword

Is it going with deprecated code in Provisioner?

http://rtfm.modx.com/display/revolution20/Summary+of+Legacy+Code+Removed+in+2.1
modKeyword classes and related code gone from framework, to be implemented more efficiently as developer sees fit
modMetatag classes and related code gone from framework, to be implemented more efficiently as developer sees fit

Quote from: vhollo at Jun 01, 2011, 02:45 PM

modKeyword classes and related code gone from framework, to be implemented more efficiently as developer sees fit
modMetatag classes and related code gone from framework, to be implemented more efficiently as developer sees fit

Just commented out the depricated code from the provisioner.class.php (attached) file.
So no keyword and no meta tag import there.

I’ll raise a ticket for this, its not deprecated, it needs a version test like clearing the cache cache, people importing into 2.0.8 may still need this where it will still work, it will only fail on 2.1 but thanks for reporting.

The documentation ODT file is unavailable as of this moment...
Could it please be converted to text or pdf or Word or some format that is used by more than 10 people??
Making people download another software to read the docs is a serious hindrance to popular adoption and usage.
:) Thank you, Tom

Issue for this already raised on 8th Jan, https://github.com/shamblett/provisoner/issues/41, now fixed, awaiting release of 1.10-beta which should be this week.

Can Provisioner import a 2.0.8 site into a new clean 2.1.1 site??