Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
1
Web Server - Ask For Help / Re: Wizard Validation Issue
« on: August 31, 2015, 09:22:50 PM »
Thank you. Enjoy DevCon!
Regards,
Trent
Regards,
Trent
2
Web Server - Ask For Help / Re: Wizard Validation Issue
« on: August 28, 2015, 02:18:32 AM »
I thought I was trying to keep it simple by having the whole login process on one form. Two forms it is then.
BTW how is the next version of NT coming along with the update to jQuery Mobile?
Regards,
Trent
BTW how is the next version of NT coming along with the update to jQuery Mobile?
Regards,
Trent
3
Web Server - Ask For Help / Wizard Validation Issue
« on: August 25, 2015, 09:58:27 PM »
Hi Bruce,
Still working on the login form here on the 'Sites' example I created a few weeks ago and have found a problem with the validation.
The problem exists when the database is in 'Single Site Mode' and not in 'Multi-Site Mode', meaning there are no real links to any sites for each user, there is only 1 site that all users log into.
If a user does not have access to login, then the validation takes the user who is logging in to the second tab to select the 'Site', instead of staying on the first tab to allow for trying again. The user can press the 'Back' button but this then disables the 'Save/Login' button and the user cannot try logging in again.
Attached is an example app. The 'Demo' user does not have access to login. The 'Test' user does have access.
What can we do here?
Regards,
Trent
[attachment deleted by admin]
Still working on the login form here on the 'Sites' example I created a few weeks ago and have found a problem with the validation.
The problem exists when the database is in 'Single Site Mode' and not in 'Multi-Site Mode', meaning there are no real links to any sites for each user, there is only 1 site that all users log into.
If a user does not have access to login, then the validation takes the user who is logging in to the second tab to select the 'Site', instead of staying on the first tab to allow for trying again. The user can press the 'Back' button but this then disables the 'Save/Login' button and the user cannot try logging in again.
Attached is an example app. The 'Demo' user does not have access to login. The 'Test' user does have access.
What can we do here?
Regards,
Trent
[attachment deleted by admin]
4
Web Server - Ask For Help / Re: Force Save/Login Button Click on Wizard 'Next'
« on: August 18, 2015, 04:09:08 AM »
Oops! Thank you.
5
Web Server - Ask For Help / Re: Force Save/Login Button Click on Wizard 'Next'
« on: August 17, 2015, 03:06:19 PM »
Hi Bruce,
Thank you. One thing I have noticed:
1) Changing the properties of the 'Next' button does not work:
p_web.site.NextButton.TextValue = 'Log On'
p_web.site.NextButton.ToolTip = 'Click here to Log On'
p_web.site.NextButton.MobileText = 'Log On'
Haven't tested the 'previous' button.
Regards.
Trent
Thank you. One thing I have noticed:
1) Changing the properties of the 'Next' button does not work:
p_web.site.NextButton.TextValue = 'Log On'
p_web.site.NextButton.ToolTip = 'Click here to Log On'
p_web.site.NextButton.MobileText = 'Log On'
Haven't tested the 'previous' button.
Regards.
Trent
6
Web Server - Ask For Help / Re: Force Save/Login Button Click on Wizard 'Next'
« on: August 17, 2015, 01:57:25 AM »
Hi Bruce,
Good stuff! Is there also a method to disable the 'next' button or methods for hiding the 'next' and 'previous' buttons altogether?
Where can I find info on these methods and what else is there?
Regards,
Trent
Good stuff! Is there also a method to disable the 'next' button or methods for hiding the 'next' and 'previous' buttons altogether?
Where can I find info on these methods and what else is there?
Regards,
Trent
7
Web Server - Ask For Help / Force Save/Login Button Click on Wizard 'Next'
« on: August 13, 2015, 01:26:26 PM »
Hi Bruce,
I'm trying to force the 'Save/Login' button to be clicked if the user only has access to one site but the button is not behaving as expected.
Attached is the test app. Login with username and password 'test' and click the 'Next' button. In debugview you should see 'clicking save button to force login'. In the firebug console you should see 'save clicked' which means the click event should have happened, but the form validation does not happen and the user is directed to the next tab with the 'Site' drop.
Regards,
Trent
[attachment deleted by admin]
I'm trying to force the 'Save/Login' button to be clicked if the user only has access to one site but the button is not behaving as expected.
Attached is the test app. Login with username and password 'test' and click the 'Next' button. In debugview you should see 'clicking save button to force login'. In the firebug console you should see 'save clicked' which means the click event should have happened, but the form validation does not happen and the user is directed to the next tab with the 'Site' drop.
Regards,
Trent
[attachment deleted by admin]
8
Web Server - Ask For Help / Re: Mobile Mode Issue Part III
« on: August 04, 2015, 05:59:31 PM »
Hi Bruce,
I'm trying to force the 'Save/Login' button to be clicked if the user only has access to one site but the button is not behaving as expected.
Attached is the test app. Login with username and password 'test' and click the 'Next' button. In debugview you should see 'clicking save button to force login'. In the firebug console you should see 'save clicked' which means the click event should have happened, but the form validation does not happen and the user is directed to the next tab with the 'Site' drop.
EDIT 14/08 - Re-posting this on it's own as it's not a mobile mode issue.
Regards,
Trent
[attachment deleted by admin]
I'm trying to force the 'Save/Login' button to be clicked if the user only has access to one site but the button is not behaving as expected.
Attached is the test app. Login with username and password 'test' and click the 'Next' button. In debugview you should see 'clicking save button to force login'. In the firebug console you should see 'save clicked' which means the click event should have happened, but the form validation does not happen and the user is directed to the next tab with the 'Site' drop.
EDIT 14/08 - Re-posting this on it's own as it's not a mobile mode issue.
Regards,
Trent
[attachment deleted by admin]
9
Web Server - Ask For Help / Mobile Mode Issue Part III
« on: August 04, 2015, 01:54:08 AM »
Hi Bruce,
Here's another issue: loc:alert does not show in mobile mode on the login form. Previous webtest app uploaded in thread 'Part II' demonstrates this when you try to either click 'Next' or 'Save/Login' buttons on the login form after typing in incorrect details.
Regards,
Trent
Here's another issue: loc:alert does not show in mobile mode on the login form. Previous webtest app uploaded in thread 'Part II' demonstrates this when you try to either click 'Next' or 'Save/Login' buttons on the login form after typing in incorrect details.
Regards,
Trent
10
Web Server - Ask For Help / Re: Mobile Mode Issues Part II
« on: August 03, 2015, 11:53:35 PM »
Hi Bruce,
One problem: The 'Save' button is still enabled all the time in mobile mode when the 'Form Settings > Layout > Wizard Options > Save enabled all the time' option is disabled.
I've attached the test app which displays the wizard functionality for the login form.
My live app is working now but the 'Site' tab is showing on the first tab as well as the second tab in mobile mode only. Working through this now.
Regards,
Trent
[attachment deleted by admin]
One problem: The 'Save' button is still enabled all the time in mobile mode when the 'Form Settings > Layout > Wizard Options > Save enabled all the time' option is disabled.
I've attached the test app which displays the wizard functionality for the login form.
My live app is working now but the 'Site' tab is showing on the first tab as well as the second tab in mobile mode only. Working through this now.
Regards,
Trent
[attachment deleted by admin]
11
Web Server - Ask For Help / Re: Mobile Mode Issues Part II
« on: August 03, 2015, 11:35:42 PM »
Hi Bruce,
Demo app is working, just need to get my live app to work too. Demo app also has 'next' and 'previous' buttons in different places to my live app so will have to figure out what's going on there as well.
Regards,
Trent
Demo app is working, just need to get my live app to work too. Demo app also has 'next' and 'previous' buttons in different places to my live app so will have to figure out what's going on there as well.
Regards,
Trent
12
Web Server - Ask For Help / Re: Mobile Mode Issues Part II
« on: August 03, 2015, 06:18:28 PM »
Hi Bruce,
Updated to NT 8.59.
Tried using a wizard form with 2 tabs: Tab 1 for 'username' and 'password'; Tab 2 for 'site'. The wizard worked ok BUT the 'Save' button no longer works and the 'ValidateUpdate' routine is not called.
Also the UI in mobile mode is pretty bad for a wizard form. The 'Save/Login' button is on the top left corner, the 'Next' button is on the top right corner and the 'Previous' button is under the form in the centre.
Regards,
Trent
Updated to NT 8.59.
Tried using a wizard form with 2 tabs: Tab 1 for 'username' and 'password'; Tab 2 for 'site'. The wizard worked ok BUT the 'Save' button no longer works and the 'ValidateUpdate' routine is not called.
Also the UI in mobile mode is pretty bad for a wizard form. The 'Save/Login' button is on the top left corner, the 'Next' button is on the top right corner and the 'Previous' button is under the form in the centre.
Regards,
Trent
13
Web Server - Ask For Help / Re: Mobile Mode Issues Part II
« on: August 03, 2015, 12:01:14 AM »
Thank you. I'll keep thinking of a solution too. Maybe a popup form with the drop on it might work for dekstop mode, and just navigate to the form with the drop on it for mobile mode. The way that our desktop app was worked for the last 15 years is that this drop is selected at login for every login, so I don't want to stray too far from that or our customers will get confused.
Looking forward to the new jq mobile build. Which version are you going to upgrade to?
Regards,
Trent
Looking forward to the new jq mobile build. Which version are you going to upgrade to?
Regards,
Trent
14
Web Server - Ask For Help / Re: Mobile Mode Issues Part II
« on: July 31, 2015, 01:27:40 PM »
Hi Bruce,
Doing it on the 'Password' field is not ideal either. How is the user prompted to click out or tab out of the 'Password' field when there is nothing else to click except the 'Login' button?
There's only 5 seconds in the time stamp i provided. You can see that you click a selection and it does not populate with what you selected, so you click and select again - all in those 5 seconds.
Regards,
Trent
Doing it on the 'Password' field is not ideal either. How is the user prompted to click out or tab out of the 'Password' field when there is nothing else to click except the 'Login' button?
There's only 5 seconds in the time stamp i provided. You can see that you click a selection and it does not populate with what you selected, so you click and select again - all in those 5 seconds.
Regards,
Trent
15
Web Server - Ask For Help / Re: Mobile Mode Issues Part II
« on: July 31, 2015, 02:37:48 AM »
Hi Bruce,
Watched the webinar, thank you. What you have demonstrated is pretty much how I would normally hide, unhide fields on a form, via the validation of a prior field.
The login form is different though.
What you have in effect done is give everybody access to figure out any usernames that are stored in the database and also which 'Sites' they are assigned to. This is a security breach and is the reason I do not have this form coded this way. This is the reason that the form has to go through 'two' logins. Mainly so the random people (hackers) cannot figure out usernames that are stored in the database.
In our live app we actually have loc:alert set to "Please select a Site" when the user presses the first login so that they are prompted to select the Site and hit login again.
Any other suggestions?
FYI: You actually saw the 'drop not selecting' problem happen during the webinar. Checkout between times 9:30 to 9:35. Also during these times you say that the user could change the username and login as a different user, but validation on the form actually stops this from happening.
Regards,
Trent
Watched the webinar, thank you. What you have demonstrated is pretty much how I would normally hide, unhide fields on a form, via the validation of a prior field.
The login form is different though.
What you have in effect done is give everybody access to figure out any usernames that are stored in the database and also which 'Sites' they are assigned to. This is a security breach and is the reason I do not have this form coded this way. This is the reason that the form has to go through 'two' logins. Mainly so the random people (hackers) cannot figure out usernames that are stored in the database.
In our live app we actually have loc:alert set to "Please select a Site" when the user presses the first login so that they are prompted to select the Site and hit login again.
Any other suggestions?
FYI: You actually saw the 'drop not selecting' problem happen during the webinar. Checkout between times 9:30 to 9:35. Also during these times you say that the user could change the username and login as a different user, but validation on the form actually stops this from happening.
Regards,
Trent