Support/Comments for Provisioner 1.7-beta

This is an auto-generated topic for Provisioner 1.7-beta by shamblett.

Brief Description:

This package allows provisioning of a Revolution site from either a remote Revolution or Evolution site. Resources, elements, files, packages and user information can be viewed/imported. Please read the user guide in /assets/components/provisioner/docs for exact usage details. Also remember to install the revogateway connectors pack into any Evolution site you wish to use. See the changelog for details of fixes in this version. The source for this package is now in GitHub at http://github.com/shamblett/provisoner

Just a heads up for future updates, looking at issue 5 in github and other comments I’ve received I’m going to put another tab on Provisioner to do bulk site imports.

This will only be for Evolution remote sites(initially anyway) and will allow a whole site to be imported, resources, chunks, templates, TV’s, users, the lot and keep the relationships between them, i.e a resource will be linked to its template,TV’s, et al. Users will be able to select things like which context to import into, parent imported categories to Provisioner or not, keep published or not, keep users active/blocked or not and also you will be able to select the elements you want, i.e resources, chunks, snippets, along with tag conversion or not etc.

I’d rather do this than overload the context menus with lots of entries like ’import, convert tags and get its associated template’ and the like as this will just become confusing.

This will be an all or nothing process when started. I’m not going to attempt any kind of rollback here should things go wrong.

It’s intended for people who have an empty Revo site and want to a starting point from existing Evo sites.

It’s a bit of work to do this of course so if this sounds reasonable I’l do it, if anybody has better suggestions I’ll listen gladly. When done this will pretty much bring Provisioner to its GA state and maintenance thereafter.

Sorry but I think it’s better that you first upgrade to Evolution (1.0.4 = latest) before trying. In fact, Provisioner seems to work since 0.9.6.3 but I think updated is better.

Under /assets/components/provisioner there should be a /tmp directory, just check that this is writeable by your webserver, if not make it 777 and try again.

Is this extension can export/import settings keys ?

For example, on each new website with Revo, I’m changing few keys :
- publish_default
- friendly_urls
- automatic_alias
- use_alias_path
- default_template
- friendly_alias_translit

How can I easyly export/import these settings ?

It doesn’t do system settings unfortunately, its aimed more at content, if you’ve only got a few of these you can just do them by hand. You could of course dump the system settings table and import it into your target site also.

OK thanks for your answer.
Is there an official whishlist for MODx developpement somewhere ?

There’s a Wishlist forum here http://modxcms.com/forums/index.php/board,3.0.html, or if you want to specifically ask for this facility in Provisioner you can raise an issue in github here http://github.com/shamblett/provisoner. Provisoner isn’t finished, there’s still some work to do so I’ll consider this.

I’m trying to provision a 2.0.2 site from another 2.0.2 site - I created a provisioner user with admin role.

1. When I try to pull down from my live server, it appears to login, but then doesn’t list resources - and throws an error on logout -

"Logout of the Remote Site failed - Unknown error"

In the error logs I’m getting a number of variations of this, but this is the start of the chain:

provisioner.class.php : 754) PHP warning: curl_setopt(): supplied argument is not a valid cURL handle resource

Which is beyond my current knowledge. Can anybody help please?

Not true shows titles in Russian (site encoding UTF-8). see screenshot