I have a strange behavior for a module that I try to import in Servoy 5.
The module was in a Servoy 4 solution, I upgraded to Servoy 5 lately and did all the required changes to handle function parameters and JSEvent, everything is OK there, and it is working just fine on Servoy 5.
But when I export the solution, this particular module cannot be imported later in another Servoy 5 Developer, it asks for a password, even when the solution has been exported without password. All other modules for this solution import fine, but this one doesn’t.
I have tried importing from the server admin, then checking out the solution. Importing from the server works, but when I check out it asks for a password.
The module is a global utility module, named QF_UTILS, and contains nothing but a global.js file - nor forms, no relations.
I tried adding a dummy form but it doesn’t change the behavior.
The only way that I have found to work around this problem was to effectively add a password…
This is happening on WinXP and Server 2003, java 1.6_017
Has anyone of you ever experienced such a strange password on import problem?
I can open a case with the .servoy file of the module if needed.
I just noticed that a solution that was exported with a password will keep it forever!
My workaround to finally import the solution was to give a password to the whole solution and reexport.
Then I was able to import giving it the password I added.
But after that, when I export from the ‘imported with password’ solution, even if I don’t ask for a password again, it keep the one I gave at the import, meaning that I can’t export again without password. Don’t know if you are following, I have trouble myself
This is very weird.
But the ultimate question is: can a solution be exported without password from the Developer where it has been imported with a password?
Or is there a way to get rid of it once it has been set on export?
In the versions before version 4.0 there was a button in the Repository dialog that allowed you to remove the protection of a solution/module (after supplying it with the correct password).
I can’t find this function anymore in Servoy 4/5.
Perhaps one of the Servoyans can shed a light on this. Didn’t this function make it into 4/5 or is it hidden somewhere?
ROCLASI:
In the versions before version 4.0 there was a button in the Repository dialog that allowed you to remove the protection of a solution/module (after supplying it with the correct password).
I can’t find this function anymore in Servoy 4/5.
Perhaps one of the Servoyans can shed a light on this. Didn’t this function make it into 4/5 or is it hidden somewhere?
Hi Robert,
Yes, such a function would help a lot!
But I guess that for the module that has been protected (no idea when or by whom in our team), we will have to create a new one because no one seems to know the password :{
The problem is that the Servoy 4 version (which we still have in SVN) is not protected.
I detached the solutions, installed Servoy 5 and pointed it to the repository.
Everything went fine, but one of our developer wanted to install it on a laptop using a USB key for transfert, so he exported it, and that’s how we discovered that one of the module (and one only!) is now protected. And I haven’t found a way to unprotect it.
Even when I managed to import it on a Developer 5 app, if I re-export it (not checking the ‘protect solution’) the module is still protected.
I really think there is something wrong here, and I would like to discover one day out of the blue that some other modules are suddenly protected with an unknown password and that I can’t unlock it!
mboegem:
how did you convert the ‘4’ solution to ‘5’? did you export from 4 and import in 5?
Hi Marc,
I detached from SVN in Servoy 4.
Then in Servoy 5, I pointed to the old repository and he did the conversion.
Then I shared to a new repository location on SVN.
But I fail to see how these steps get me into this…
I don’t know if it will make any difference, but we actually exported our whole solution from Servoy 4.
Then in 5 we imported the whole solution again and linked it to a new SVN location.
We have quite a large solution running, but I was surprised how smooth & fast this worked (as a check out in 5 from our ‘4’ SVN location made Servoy 5 choke in it).
mboegem:
I don’t know if it will make any difference, but we actually exported our whole solution from Servoy 4.
Then in 5 we imported the whole solution again and linked it to a new SVN location.
We have quite a large solution running, but I was surprised how smooth & fast this worked (as a check out in 5 from our ‘4’ SVN location made Servoy 5 choke in it).
If it isn’t to much work I’d say: give it a try!
Hi Marc,
work or not, the problem is rather that I don’t know when and how the module got this protection during the process…
And whether or not it is possible to get rid of it.
The Remove protection option was added in context menu of an active solution/module (if protected). You will be prompted for old password. This will be included in Servoy 5.1 .
The Remove protection option was added in context menu of an active solution/module (if protected). You will be prompted for old password. This will be included in Servoy 5.1 .