Support/Comments for Provisioner 1.8-beta

Quote from: shamblett at Oct 20, 2010, 06:52 AM

I could look for the id’s as part of tag conversion and substitute them, I have the old->new map at the time so this is doable.

That would be great.

I have trouble logging in. Both websites have revolution version. I entered modx login infomation.

Where can I find the "Remote Site Identifier". No info is included in the guide about this field. Is this the web_context?

Thanks

From the User Guide Chapter 3 Administration :-

Additionally for Revolution sites you must supply a site identifier for the remote site. This is a unique key generated on installation of the remote Revolution site that ties the AJAX calls made in the front end to the back end connectors for that specific site, i.e. it is an API key. This can be found in the config.inc.php file under /core/config of the remote site. Look near the top of this file for a PHP variable named ’$site_id’ and copy it exactly, without quotes.

Thanks shamblett.

Just a note for those having trouble with any information Provisioner doesn’t retain from the original site. To correct this problem, I created a TV for each piece of information I was looking to keep—specifically the original resource id, the createdon timestamp, and the resource type (weblink or document)—then placed the aforementioned pieces of information in the modx_site_tmplvar_contentvalues table via the command line, associating each with the appropriate resource.

After provisioning the site into the Revo installation, I again dropped back to the command line and used the TV values to modify the modx_site_content table, setting the resource type, the createdon timestamp, and replacing any old references to specific resource ids with their new equivalent. It helps to generate your MySQL commands in a text editor, then copy and paste into the command line so you can fire them off all at once (this is especially true for updating the references to specific resource ids).

All of that said, I have to go through this a second time, as I didn’t realize having differing character sets in my production and testing databases would cause all sorts of havoc with regards to special characters. Sigh. No rest...

Hi Shamblett,

my question seems to be pretty basic but, I just can’t resolve it.

I’m currently trying to import resources from an Evolution site to a new Revolution version. When I installed Provisioner yesterday and tried to connect, it told me that it couldn’t connect to the site and the Revogateway was not installed. I had followed your instructions and upload the revgateway package.

Trying again with some fresh eyes this morning, I now simple have the inital "Actioning" message and nothing happens!

Would you have any advice about this please??

Thanks in advance

Simon

Provisioner Beta 1.8
MODx Revolution 2.0.4-pl2
MODx Evolution
Mac OS X 10.6.4

Ok, your remote evo site should have the following directory structure /assets/snippets/revogateway with this directory containing a connectors folder and an index.php file.

Also check that you have the following local directory and it is writeable by your webserver : /assets/components/provisioner/tmp.

If the above is correct login to your Revo site, go to Provisioner, enter your remote evo site account and URL, select ’remote site is evo’ and ’logout’. Submit this and see what the message is, it should be ’not logged in’.
If you get anything else just note it. Now select ’login’ and try again. If its still fails check your webserver access log and post the output back here.

Thanks for your speedy response.

I checked all your conditions:

1. structure correct on Evo /assets/snippets/revogateway and contains appropriate connectors folder and index.php file.
2. local directory did not have /tmp but, have added this and made sure it is writeable.
3. entered all account data, logout, submitted and is currently saying, please wait...Actioning.

I have attached the current webserver log..

Thanks

simon

Hi, looking at your log your calling provisioners connector OK and its returning a response thats 648 bytes long, without further investigation I don’t know off hand if this is correct or not but from experience if you return anything to the front end thats not correctly formatted in JSON it will hang, which is what you are seeing.

Maybe its perms issue of some kind, navigate your browser to /assets/components/provisioner/connector.php and see what you get back.

Get the following back when I run it:


Warning: require_once(/wsb5169259701/working/core/config/config.inc.php) [function.require-once]: failed to open stream: No such file or directory in /homepages/34/d268253803/htdocs/wsb5169259701/working/assets/components/provisioner/connector.php on line 20

Fatal error: require_once() [function.require]: Failed opening required ’/wsb5169259701/working/core/config/config.inc.php’ (include_path=’.:/usr/lib/php5’) in /homepages/34/d268253803/htdocs/wsb5169259701/working/assets/components/provisioner/connector.php on line 20

Line 20 from connector.php reads:

require_once MODX_CORE_PATH.’config/’.MODX_CONFIG_KEY.’.inc.php’;

??