Support/Comments for Provisioner 1.9-beta

Site import is only for evo to revo, whether that be 2.0.8 or 2.1, between revo installs no matter what the versions you can only import discrete entities.

Provisioner is only for Evo to Revo??

We need Revo to Revo import here...

Thank you, Tom

Quote from: TomMLS at Jun 14, 2011, 11:22 AM

Provisioner is only for Evo to Revo??

We need Revo to Revo import here...

Thank you, Tom

Tom, you can still pull resources, files, etc over from the remote site, it’s just not an "Import Everything at Once" kind of function. It’s been several weeks since I’ve done Revo to Revo, so I can’t remember distinctly but it’s either a drag ’n’ drop thing or a right-click thing.

:)

I don’t need provisioner any more on our MODx site -- how do I delete it COMPLETELY??

Thank you, Tom

Go into package management, select the provisioner package, on the pull down select ’force remove’.

I have problems getting provisioner 1.0 pl (which doesnt seem to have its own forum topic) to work.

Local system (mydomain.int) was a direct copy of the remote system mydomain.com. I reinstalled modx2.1.1 (as upgrade) on the local system, which now works the same as the remote. I installed provisioner on both system. On mydomain.int I enter all the info as per instructions but I keep getting "Login to the Remote Site failed - Access denied". My password is correct, everything else is.

Locally I have files inside assets/components/provisioner/tmp with contents like this:



I have no other idea how to troubleshoot this...

SO...question...

If I cant get provisioner to work, and I am just updating chunks and custom snippets and resources, would a database update from local to remote be sufficient?

Thanks in advance.

Remote Site failed - Access denied".

Are you sure your account/password and site id are correct? Revo sites need the site id as well as the account credentials, the upgrade probably generated a new site id key. The error above is returned straight form the remote revo site as is, i.e its not generated by Provisioner.

I’m sure of the username and password as I can log into the remote manager in another tab with the same info.

The upgrade I did was to the local installation, and I tried both the remote site id and the local one too. Cleared the cache on both sites as well.

I know I have the URL correct - mydomain.com/site/connectors/ If I change the url I get ’unknown error’.

There has to be something else preventing it. I even disabled my firewall and still nothing.

Would it make a difference if I had installed the pbkdf2convert package and converted the md5 passwords?

Hmm, all I can suggest is could you mail me your account/password for the remote site, [email protected], I’ll try and login from my known good test site, if it fails I can at least attach the debugger and try and suss whats going on.

It would appear that this change :-

https://github.com/modxcms/revolution/commit/322ac4428a3c9126c648d8a80bcd8d5b4394e51b

is stopping Provisioner in its tracks at the mo, it doesn’t look as though there’s an easy work around for this either at the moment except to downgrade to 2.1.0.