Great Ideas. Always Flowing.

We are not happy until you are happy. Client satisfaction guaranteed. Whatever your needs and requirements, we have the skills and resources for the job!

Quick login...


Or... now make it easy with Facebook Integration
Connect via Facebook



Top Sellers

Frustrated over the lack of customization for your user's registration fields? Dynamically setup your DNN Portal with custom registration fields, layout, questions, and other core integration options......

Ultra Video Gallery is a brother product of Ultra Media Gallery, UVG allows you to upload videos in various format and automatically encode them to flv or H264 format, you also can add videos from internet or record live videos from your webcam.

Build high performance, completely customizable data-entry forms and views driven by your DNN and external databases. New built-in tools make it a snap to quickly create data entry forms, data views, and even database tables. Plus, add your own HTML, CSS, Javascript, SQL commands, stored procedures,

The most advanced DotNetNuke shopping cart on the planet. Easy to use e-Commerce, Secure Shopping Cart Software and SEO friendly. B2C / B2B Ecommerce Sites.

One stop solution for events calendar and events registration! FREE DOWNLOAD is available now!

Submit button force visible
Last Post 07-27-2009 03:47 PM by Gordon. 18 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
mike jonesUser is Offline
skipping stones
skipping stones
Posts:6
Avatar

--
01-16-2008 07:29 PM

    Under the Submit button/link customization section there's an option: Initially hide form submission button.

    The help text says: Hide form submission button until forced visible by client event.

    I want to hide the submit button so I clicked this, and then I want to force it visible once someone completes a field. But I can't figure out what particular type of client event I need to set in order to force it visible.


    Chad NashUser is Offline
    Posts:5260
    Avatar

    --
    01-18-2008 04:35 PM

    Hi,

    Check out this demonstration that outlines executing a client side events and hiding form submit button until the user types in the word yes. You could easily change this client side event to have the user check a box or other types of enhancements.

     

    Dynamic Forms - Hiding Submit Button Feature Demonstration

     

     

    -Chad

     

    mike jonesUser is Offline
    skipping stones
    skipping stones
    Posts:6
    Avatar

    --
    01-18-2008 07:22 PM

    Thanks for pointing me to that tutorial. I'm still a little unclear on how to make it work for my situation.

    So I have a checkbox short name: Agree
    When someone checks that checkbox I want the submit button to show. I put this in the client side even:

    if ( $(Agree))
            {
                  showhtml('SaveForm') 
            }
    else
            {
                   hidehtml('SaveForm')
            }

     

    But it didn't work, I tried making a text/html field with this in it:

    <Div ID="SaveForm">
    But that didn't work. Could you please tell me how to make this work,
    I'm having trouble understanding the tutorial and how to edit it to work with a checkbox.
    Thanks
     

     

     

    Chad NashUser is Offline
    Posts:5260
    Avatar

    --
    01-23-2008 09:46 AM
    Hi,

    Well your client side event looks correct so this might be something you will want to open a support ticket and have us review. There already is a DIV called SaveForm though (this is actually built in and is where the submit button exists) so you shouldn't have to create a new one. Actually if you did create one then it would probably cause a problem since one already exists?

    -Chad
    Daniele BernottiUser is Offline
    new to the springs
    new to the springs
    Posts:4
    Avatar

    --
    04-01-2008 07:38 AM

    Hi Chad

    I've the requirement to hide the submit button until users complete the form.

    I saw the demo and it's exactly what I need, but I cannot find the "initially hide" setting.

    I'm running version 02.30.50. I've a bad configuration or I need to upgrade the module code?

    Kind regards

    Chad NashUser is Offline
    Posts:5260
    Avatar

    --
    04-01-2008 11:43 AM

    Hi. This feature wasn't added until 2.5 so you will need to upgrade to the 2.5 release. You should receive approx 70% off for the upgrade though if you login with the same userID/Password as you purchased 2.3 with.

    -Chad

    GordonUser is Offline
    wading in the water
    wading in the water
    Posts:16
    Avatar

    --
    07-08-2009 11:59 PM
    Hi,
    I too am heading down the 'hide submit-button' route but am not having success with the methods described on page 118 of the V3.0 manual and in DF Demo #7 and also outlined above.

    My problem is that the 'submit' button is visible on form opening; it is not hidden. (The "Initially Hide Form Submission Button" is definitely ticked. I have even tried unticking it, clearing the cache, refreshing, tipping my computer upside down and shaking it - still no good.)

    What puzzles me is that the Submit button can be toggled hidden/visible by ticking/unticking the "chk(ShowHide)" check box. The client-side event would therefore appear to be working.

    The puzzle continues in Demo #7 itself; at least on my computer and with both Explorer and Firefox. That green "Continue" button is visible on form opening and it, too, can be toggled hidden/visible by typing YES/incorrect-entry. I have downloaded the demo and tried it locally, and the result is the same as on the web: it is visible on form opening. No good.

    My form is a long one and I certainly do not want my users seeing that submit button until the end. Any ideas on how to get this up and running would be very much appreciated.

    Regards,
    Gordon

    PS Should simply ticking the "Initially Hide Form Submission Button" hide the button, as happens with "Hide Until Forced Visible by Question Event' everywhere else? I first thought that it may not hide unless it was tied to "something" that was capable of opening it. The chk(ShowHide) proves to do that and the Submit still does not want to hide. Hmm?
    CandaceUser is Offline
    river guide
    river guide
    Posts:2431
    Avatar

    --
    07-09-2009 07:16 AM
    Hi Gordon,

    Can you please copy/paste your client side event into the Initial JavaScript box under Module Configuration, Custom JavaScript File and see if it works? Thanks!

    Candace
    GordonUser is Offline
    wading in the water
    wading in the water
    Posts:16
    Avatar

    --
    07-09-2009 02:17 PM

    Hi Candace,

    Many thanks  - cracked it. I have a solution.  However, I am sure that all is not quite right.

    The event needs to be in both the chk(ShowHide)'s Client Side Event and the Module's Initial Javascript.

     

    • Take it out of  chk(ShowHide)'s and no response from the checkbox. 
    • Take it out of the Module's Initial Javascript and it's back to the symptoms in my previous post (Submit is visible on form opening but can be toggled hidden/visible).  And this is what is happening in Demo #7.
    • Have it in both and it's hidden on opening as  it should be and it still can be toggled - correct.

    In the course of all this I found another 'trap for young players'.  I created the checkbox with the name of "chkShowHide" but after a few misfires trying to get this whole thing going I discovered that the Short Name had defaulted to "chkShowHid".  Of course the script doesn't like it with the 'e' missing. 

    On field creation, Short Names are being truncated to a field length of 10. But you can subsequently edit them to what appears to be any length.  One to watch out for.

    Regards,

    Gordon

    CandaceUser is Offline
    river guide
    river guide
    Posts:2431
    Avatar

    --
    07-09-2009 04:22 PM

    Hi Gordon,

    Thanks for sharing your observations.  Yes, most times, you need to have it in both so the Jscript applies at page load.

    True on the short names also.  Some people just let it alone and have LastNa as the short name for Last Name, for example.  I always check and modify, though, to make sure it makes sense to me.   Plus, it helps prevent errors like you experienced.

    Candace 

    GordonUser is Offline
    wading in the water
    wading in the water
    Posts:16
    Avatar

    --
    07-17-2009 02:44 PM
    With Candace’s terrific advice I thought I was across the line on this one. Unfortunately, although I can hide either chk(ShowHide) or the Submit Button, I can’t hide both.
     
    Using some simple examples here is what I am trying to achieve. I open with one question: “Do you want to go down aisle A or B”.   However, concurrently, users also are presented with either “Do you want to go to the check-out?” (chk(ShowHide)), or “Pay up now.” (Submit). Logically, they shouldn’t see these choices until they have filled their cart. That is, until they have passed through a series of Question Events, leading to the chk(ShowHide) becoming visible for the first time.
     
    By the way, the chk(ShowHide) and Submit work perfectly when they are both visible.
     
    In trying to hide them both I tried the following combinations using “Hide until forced visible by question event” for CHK(ShowHide) and “Initially hide form submission button” for Submit.
     
    CHK(ShowHide)
    Hidden at setup?
    Submit
    Hidden at setup?
    What is visible on form opening…
    What is visible after Question Event triggered…
    True
    True
    SUBMIT only
    CHK box only
    True
    False
    SUBMIT only
    CHK box only
    False
    True
    CHK box only
    CHK box only
    False
    False
    CHK box only
    CHK box only
     
    I would really like to think I am missing something here and that there is a little checkbox hidden away that I need to click to make this work. But, am I barking up the wrong tree, is this something that DF is not capable of achieving, or do you think this could be bug-related? 

    Any advice would be gratefully accepted. Gordon

    David ToUser is Offline
    river guide
    river guide
    Posts:2719
    Avatar

    --
    07-20-2009 07:14 AM
    HI Gordon, can you export your form to www.betasprings.com(username: host,password:dnnhost) and send us the URL / tabid so we can take a look at it? -- David
    GordonUser is Offline
    wading in the water
    wading in the water
    Posts:16
    Avatar

    --
    07-20-2009 03:17 PM
    Thanks David,

    My form is now here:
    http://www.betasprings.com/GordonSh...fault.aspx

    By the way, an issue on this form was the subject of my post on 10 July (http://www.datasprings.com/Products...ult.aspx).
    That was the one where CAPTCHA and Required Field were conflicting. You said you were able to reproduce the problem, but here is my version if it is of any help.

    Kind regards, Gordon
    David ToUser is Offline
    river guide
    river guide
    Posts:2719
    Avatar

    --
    07-21-2009 07:13 AM
    HI Gordon, I just looked at your form on betasprings and I can see the "Submit" button is showing until the user clicks the checkbox. Based on this, that means option 3 above in your table (checkbox isn't hidden at setup, submit is hidden at setup). The form is looking good to me. I'm kind of puzzled as to what you want to improve? Is your final objective to have the checkbox not show up on page load either? -- David
    GordonUser is Offline
    wading in the water
    wading in the water
    Posts:16
    Avatar

    --
    07-21-2009 03:38 PM

    Hi David, Yes, my user-requirement is to have neither of them visible on page load.  My reasoning is explained with my 'aisle' and 'checkout' analogy two posts back.   Further:

    • It looks a bit sloppy to be asked to go to the 'checkout' before you have even started to look for something to buy.  (As an aside, this is what is happening on DF Demo #3.  There you can submit the form before answering the first question: chosing either 'Employer' or 'Prospective Employee'.)
    • If users are able to see Submit, and a question event happens to load slowly, there is a chance that the user will instinctively hit Submit.
    • If Submit is visible users can consciously clk it before all the questions are answered.  What is particularly bad about this is that if Required Fields are not opened/presented to the user then they are not validated. (at least in my forms.) So, for instance, if a user Submits without entering an email address, we will have no way of getting back to them to point out that their booking can't be accepted.  'Email' will not have been considered as Required so an empty field will be accepted.
    My end-state, and I thought DF was capable of this, is:
    • To have the "Finalise and Submit" section only open after all preceding questions have been completed. [Status: the heading does]
    • That section would have
      • a "Do you agree to the terms and conditions"/YES textbox (like in DF Demo #7. And, by the way, that demo doesn’t seem to be working: on page load both the YES Textbox and the 'Continue' button are visible.)  [Status: Before heading down the 'terms and conditions'/Textbox route I had aimed to  get this Combobox approach working]
      • a CAPTCHA [Status:  I have taken that out of play because it has a bug - the subject of an earlier post.]
      • a Submit button [Status: struggling to hide it and the chk(ShowHide)]

    Obviously I am a newcomer to this game, but I would have thought that if the “Hide until forced visible by question event” for CHK(ShowHide) would work (ie actually hide it as it's telling me it will) then my prayers would be answered.

    Using the same column headings as in my table above that would give the desired: True/True/Neither Visible/CHK box only. 

    Regards, Gordon

    PS my form on BetaSprings is set up using Option #4 (both False), not #3, although the result is the same.

    David ToUser is Offline
    river guide
    river guide
    Posts:2719
    Avatar

    --
    07-22-2009 01:58 PM
    HI, please check out your form that I patched up:
    http://www.betasprings.com/tabid/68...fault.aspx

    1) under Module Configuration / Javascript on load, I placed "Hidehtml('SaveForm')
    2) I also hide "chkCheckBox" field
    3) created 6 question event to unhide "chkCheckBox" field based on the last drop down question the user asnwers (ie. drop down fields QuestionComments and Title_Contact).

    This closely resembles what you want to achieve. A better option to go would be to not use the chkCheckBox altogether. What you would do is to use strictly client side javascript on the last field to "Showhtml('SaveForm')" . This way, whenever they are on the last question field (whether it's a textbox or dropdown) it will unhide the "Submit" button. -- David
    GordonUser is Offline
    wading in the water
    wading in the water
    Posts:16
    Avatar

    --
    07-23-2009 10:21 PM

    <!--[if gte mso 9]> Normal 0 oNotOptimizeForBrowser />

    Many, many thanks David,

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    I have done as you suggested and it’s working perfectly.  However, I have stuck to the CheckBox (rather than your javascript approach) because I now want to convert it to an “Agree … terms and conditions?” question.

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    And may I add, if there is anyone reading this who is not convinced of the quality of the product or high level of customer service that the team at Datasprings provides I want to give a huge endorsement for both.  David, in particular, has spent a lot of time helping me and I am very grateful.  Great effort.

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    The following is a contribution that puts what I have learned back into the pool……… 

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    If planning to hide the Submit button you have to decide when you want the question that will lead to its opening (eg  clk(ShowHide) ) to become visible.  Demonstration 7 gives an example where that controlling question (the ‘Do you agree to the Terms and Conditions”) is visible right from the form opening.

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    On the other hand, you may not want that question to appear until a series of preliminary questions has been answered. That was my case, and the subject of Candace’s and David’s terrific assistance above. My logic for wanting to do this is up in my post of 21 July

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    How to set up the first case is explained briefly on page 118 of the Feb 2009 (V3) User Guide. Here that explanation is expanded and the lessons from this post are added:

    • Add a Simple CheckBox
      • Give it any Question name (eg  “Do you agree to …..?”
      • Ensure you give it a Short Name of exactly  chkShowHide. (Be careful: if you give the Question itself that name (in ‘da big box) and have it automatically copy to the Short Name it will truncate to a field length of 10. The following code won’t like it.)<!--[if !supportLists]-->
      • In its Client side events (in Advanced Field Options) add<!--[endif]-->

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    if($(chkShowHide))

    showhtml('SaveForm')

    else

    hidehtml('SaveForm')

    <!--[if !supportEmptyParas]-->

    • <!--[if !supportLists]-->Also add the code above to the Initial JavaScript box  (Module Configuration, Custom JavaScript File

     

    • Tick: “Initially hide form submission button” (Module Configuration/ Submit/Link Button).   (You will see radio buttons in there. It doesn’t matter which one is used in this context. Style as necessary.  eg change the button’s title from ‘Submit’ to, for example ‘Send Request’, ‘Apply’ etc)<!--[endif]-->

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    Finished. On form opening you will see the “Do you agree…?” but not the Submit.  Tick the former and Submit will appear.  (Again, this is the Demo #7 approach.)

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    Now for the more complicated case two: neither the checkbox /(“Do you agree to …..?”) nor Submit are visible on open.  We want to see them much later. (And, of course, here Iam only dealing with the submit-related questions; no mention at all of any others that will end up on the form.)

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    • Repeat the above process with two exceptions:
      • DO NOT add the code above to the Initial JavaScript box  (Module Configuration, Custom JavaScript File).  Instead, add to that box only: hidehtml('SaveForm').  (Yes, confirmed, put it all in the  Initial JavaScript box )
      • DO tick the “Hide until forced visible by completion event” for the “Do you agree … “ question.  (In the previous case the form opened with that question visible, in this one we are starting it off  hidden.)

    <!--[if !supportEmptyParas]--> <!--[endif]-->

    • <!--[if !supportLists]-->Note, you could also add other ‘questions’ that you want to make visible at the same time as the  “do you agree…?; perhaps making a section on the bottom of the form for them. eg you could add a CAPTCHA, and things like  “Do you want to join our mailing list?” etc.  Don’t forget to hide them. I would suggest, however, you keep it simple on the first pass. Get it to work and then come back and add the extras.<!--[endif]-->

          

    <!--[endif]-->
    • Work out where you want the checkbox /(“Do you agree to …..?”) to initially hide. That is, inside which Question Event will it sit. Let’s assume you don’t want it to appear until the user ticks “Do you want to proceed to the checkout?”

    •   Create that Question.  It could be a Simple Checkbox as in the case above, or it could be another dynamic entity such as radios, a combo etc. Let’s make it a CheckBox and call it “Do you want to proceed to the checkout?” <!--[endif]-->

     

    • Create a Question Event based on that Question.<!--[endif]-->

    <!--[if !supportEmptyParas]-->

    <!--[if !supportLists]-->o       Open Question Events<!--[endif]-->

    <!--[if !supportLists]-->o       Select New Question Event<!--[endif]-->

    <!--[if !supportLists]-->o       Give it a name eg GoToCheckout<!--[endif]-->

    <!--[if !supportLists]-->o       Tick “Display hidden question based on another questions response’<!--[endif]-->

    <!--[if !supportLists]-->o       In Initial/Postback question select the Question you created above (Do you want to proceed to the checkout?” It’s the one you want a yes answer for.)<!--[endif]-->

    <!--[if !supportLists]-->o       Depending on the type of Dynamic Question (radio, combo etc), you will be presented with a choice of the responses that will trigger the event.<!--[endif]-->

    <!--[if !supportLists]-->o       If you are using a Simple Checkbox then put a tick in the Initial Response box.  (ie if user ticks the box the event will take place)<!--[endif]-->

    <!--[if !supportLists]-->o       Choose the Affected Question (it’s “Do you agree …. ?” It’s the one(s) that will come visible with the yes answer.) [ps If you have added other questions, as noted above, then tick them here also.]<!--[endif]-->

    <!--[if !supportEmptyParas]-->

    All going well you will now have a cascade of questions:

    • <!--[if !supportLists]-->On form open – only the “Do you want to go to the checkup?”  [Of course, you could also put that inside another Question Event.]
    • Tick that and “Do you agree …? , and others you have added, are revealed.<!--[endif]-->
    • Tick that and “Submit” appears.<!--[endif]-->

    <!--[if !supportEmptyParas]-->

    Troubleshooting

    • Watch the syntax – you have to get things like chk(ShowHide) spot on
    • Check all your hides / make visibles
    • Check you have the correct Dynamic Question and the Affected Question selected – don’t get them the wrong way around.
    • And there are many “others”. I think I have found most!

    <!--[if !supportEmptyParas]-->

     

    I hope that helps someone.

    Regards,

    Gordon

    <!--[if !supportEmptyParas]-->

     

    PS I wasn’t going to ask a question , but there is one that may be of benefit to others heading down this path (sorry, ‘stream’!).  The only (slight) hitch on my form is that if Submit is clicked without correct validation in all fields then, as expected, the error messages come up, BUT the submit button gets hidden.  Users could be left stranded not knowing what to do next.  My workaround is to put a note: “If fields not filled in … error message … add/correct …..” then invite them to un-click and then re-click the “Do you agree ….? box.”  Not very elegant, but it works.     Is there any way to not have the submit button hide on presentation of incorrect validation?  Or perhaps have my note appear at the same time as the validation-error messages appear. That is, not have it there even when there isn’t a validation problem.  Just a thought.

    <!--[if !supportEmptyParas]-->

    Again, my sincere thanks. Gordon

    Chad NashUser is Offline
    Posts:5260
    Avatar

    --
    07-27-2009 02:11 PM
    Gordon,

    Thanks for the feedback and information. I am sure this thread will be very helpful to others implementing similar client side events and so forth. We are also working to test this feature for the 03.00.20 upcoming patch because it should be hiding the submit button initially but I guess this came about recently within the 3.0 initial release and some other conflicting features.

    If you run the same JavaScript under 'Initial JavaScript' does this fix the issue with having to force the user to check/uncheck anything? The Initial JavaScript should be able to run and if that box is checked it should still be able to hide/unhide just as if the user checked it. We have had to implement similar code for other client side events that would lose their value such as totals and so forth (as in demo 20 at http://www.datasprings.com/formdemos)

    Thanks again,

    Chad
    GordonUser is Offline
    wading in the water
    wading in the water
    Posts:16
    Avatar

    --
    07-27-2009 03:47 PM
    Hi Chad,
    In response to your JavaScript question: I tried many combinations and the only approaches that I could get to work are as described above. In summary:
    • Case 1/Demo #7 equivalent. Both hidehtml and savehtml have to be in each of Initial JavaScript and Client side events
    • Case 2:   Both hidehtml and savehtml have to be in Client side events but only hidehtml is to be in Initial JavaScript

    It has proved to be a bit of a workaround but it is achieving the result. With the Checkbox configured as a “Do you agree to the terms and conditions?” it all flows nicely.  

    (Hopefully) to assist you in putting together your 03.00.20  patch my form representing the latest state of play is at:

    However ….. there is still the issue of what happens on incorrect validation on submit that I mentioned in the  PS of my previous post. Ideally, our friend, the  Submit button would remain visible on incorrect validation, but I think the simplest approach would be to put the “If you have not completed the required fields etc” as a header/footer/explanation to the error-message itself (as opposed to having it permanently visible as it is now).

    Interestingly, the words “here we are” and “ False” are returning as a header to that error message.  Any idea where they are coming from?? Could the “If you have not completed the required fields …etc” go there??

    Last one …I can only get the validation error-summary to appear if it is set to ‘top’; ‘’bottom’ returns nothing.

    Regards,

    Gordon

    You are not authorized to post a reply.


     
     

    Join our mailing list...

    Get current news and events the easy way
     
     
       
    Subscribe Me

    Recent Blogs...

     
    Copyright 2005 - 2011 by Data Springs, Inc.
     
  • film izle
  • 720 izle
  • film
  • sinema izle
  • film makinesi
  • T�rk�e dublaj film
  • film izle
  • film izle
  • baglan film izle
  • sinema izle
  • 1080 film izle
  • film mercegi