To be able to debug vr_getContext() calls, you need to have run a smart client at least once during your Developer session.
You can stop it after that, what it does is activate the debugger in Servoy, then you can put a breakpoint at the start of the vr_getContext() method and you will be able to debug it.
Now, I think that what happens to you is that I've made the sample solution to use authentication during various tests for authentication methods (see the Wiki
https://www.servoyforge.net/projects/ve ... /WebClient for the various options), but I didn't save the config.json with authentication, sorry I'll update the .servoy with the fix.
So what you need to do is set the 'Must authenticate' flag of the VelocityWebClient solution to false, then you will see what's going on in the vr_getContext() method when it's called.
If you want to use authentication though, you will need:
1/ to create a new user in the VelocityWebClient solution ("User and group security") if you didn't import with the users.
2/ modify the config.json file (found in reports/www/) to:
- Code: Select all
VelocityWebClient: {
authentication: "basic",
type: "session",
resources: ["css", "images", "js", "files"]
},
Or
- Code: Select all
VelocityWebClient: {
authentication: "form",
userParam: "user",
passParam: "pass",
loginPage: "login.html",
type: "session",
resources: ["css", "images", "js", "files"]
},
Or
- Code: Select all
VelocityWebClient: {
defaultUser: "ptalbot",
type: "session",
resources: ["css", "images", "js", "files"]
},
And make sure that you've set the defaultUser password in the users.properties file you can find in /reports/www (the password are hashed when first accessed by Velocity)
Hope this helps.