I’ve been playing with revo SVN (2.0 branch), and was playing with Provisioner a bit, but I might have been pushing it too much on the bleeding edge. Did something change in latest SVN that broke Provisioner, or am I doing something wrong?
When I install Provisioner, it does not show up in the menu, but if I call it directly through the action ID, I am able to get the login page. I point it to http://mydomain/connectors and write remote user/passwd, but nothing happens. If I then select logout, it says I am not logged in.
Hi Jacob, yes your correct, provisioner works with revo 2 beta3. (and maybe the latest revolution branch also)
The 2.0 branch has moved ahead of this, for one thing how the 3PC’s hook into the menu structure has changed, this needs to be updated, there’s probably more to do here. I need to fix the actions thing then install it into the latest revo 2.0 branch and see what else is needed. I have to do this for the beta4 release so I’ll have a look at it.
Use MODx, or the cat gets it!
I’ve submitted version 1.1 beta to extra’s, it should appear shortly.
This allows provisioner to work with Revo 2 beta 4. It also packages the user guide in the transport package (so it will appear in /assets/components/provisioner/docs) and local/remote package comparison is now done on installed packages only, not just if the packages are present.
Use MODx, or the cat gets it!
Interesting, sounds as though it may be some kind of DNS prob, its trying to resolve the hostname but can’t, hence the hang. I wouldn’t have thought it would be a corrupt MODX install but its worth checking. What happens if you type the URL you are using into a browser on the local machine?
Use MODx, or the cat gets it!
Hello Shamblett,
Typing fyp.nl on the local machine works ok.
Ok, Can you login to the site through the manager locally? This will prove that the login itself works. Provisioner uses CURL to access the remote site, this will use your host file but it doesn’t know about any other URL redirections that you may have set up in Apache, you could try it without these as a test and see what happens.
Use MODx, or the cat gets it!
I copied the fyp.nl site to the localhost directory - and the site works there too and I can log in to the manager there too (as I could on the original location), but I still can not get the provisioner to log onto the system there.
I try to connect using "http://localhost/connectors" and get the following error in the log:
[2010-02-19 14:56:45] (ERROR @ /assets/components/provisioner/connector.php) Path specified for package provisioner is not a valid or accessible directory: model/
