i am working in Cruisecontrol and i am using below code to get input from user
<parameters>
<textParameter>
<name>Password</name>
<display>Enter Password</display>
<description>Enter Password</description>
<default>password#123</default>
<required>false</required>
</textParameter>
</parameters>
but problem is that when i am going to type password in textbox, it's readable.there is any way we can set mode password in textbox.
Looking at the CruiseControl.NET documentation on parameters it appears there is no option "out of the box" to encrypt the password prompt.
I believe you could write some custom javascript/DOM stuff in the index.html page to handle this on your own (if you want to get creative).
Related
Following this disabled social account from logon sample. Here's what I see when the Local Account user exists and is disabled:
NB - I've changed the ContentDefinition so that it's using 2.1.7 instead of 1.1.0.
I'm assuming the "hide me" text box is to be hidden using css? Which would mean that I would have to implement my own Template?
Also, there's a Cancel and a Continue button. Because the dummy textbox doesn't actually do anything, clicking the Continue button does not work. So I assume I want to hide the Continue button, but only when the dummy text box is present? Does that mean I should be looking at Javascript?
Finally, the UserMessageIfClaimsTransformationBooleanValueIsNotEqual error message (defined in the AAD-DisabledUserPage Technical Profile) does not appear anywhere in the source of the page. It seems integral to the strategy in the sample. Am I missing something?
I've looked at Customise the UI, Customise the UI with HTML template and Enable JavaScript and page layouts. There doesn't seem to be anything on customising the generated content. Have I missed something in the documentation?
Very strange so I had a look at the sample.
This is an old sample. It still uses "socialIdpUserId".
<! - The claim socialIdpUserId has been renamed to issuerUserId →
I renamed this in the base file to "issuerUserId".
Essentially, they needed a "dead-end" page.
But the dead-end page needs an output claim so they made a dummy one but wanted in removed!
I would have used a paragraph element. Maybe it wasn't available then?
I wrote that up a while back.
My version is in this gist.
If disabled, the user sees:
You can hide Cancel and Continue by modifying the technical profile. See the Metadata section here.
I am working on CruiseControl.Net. I am using textbox like below code
<parameters>
<textParameter>
<name>Password</name>
<display>No</display>
<description>Enter Password?</description>
<default>pass#12345</default>
<required>false</required>
</textParameter>
but problem is that when I am going to type anything, it's visible whatever I have entered in textbox. So I want my textbox should be password mode.
this is issue 220 :
http://www.cruisecontrolnet.org/issues/220
so not available yet
I have successfully created a feature in sharepoint that modifies the existing edit dialog and adds a custom button to it like this.
and I am aware that I can pass back data when the user clicks the custom button like this.
<CommandUIHandlers>
<CommandUIHandler Command="ActivateUser" CommandAction="/_layouts/MyFeature/MakeUserActive.aspx?ListID={ListId}&ItemID={ItemId}&ItemUrl={ItemUrl}&ListUrlDir={ListUrlDir}" />
</CommandUIHandlers>
As detailed here
I can now handle the list item and perform my required actions on it BUT given that this button has been added in the modify context (IE: Inside the sharepoint edit item dialog) what if you want to save changes to the data itself?
To me it seems like using your custom button would always mean losing any changes the user has made to the data. Is there a way around this?
Good question!
You actually already linked to the solution: Right now you are simply redirecting the user by using a URL as your CommandAction: CommandAction="/_layouts/MyFeature/MakeUserActive.aspx?ListID={ListId}&ItemID={ItemId}&ItemUrl={ItemUrl}&ListUrlDir={ListUrlDir}"
This if course redirects the user to another page without saving the current entry. What you want to do is use Javascript as linked in the MSDN article:
CommandAction="javascript:alert('here be dragons');"
You can either work the the SharePoint Javascript object model here and use something like SP.ListOperation.Selection.getSelectedItems(); or you could use complete custom code.
From your aspx page name I can see you want to "make a use active" (btw: wouldn't "ActivateUser.aspx" be nicer?). If this simply means setting a property in another list you could do that with the SharePoint OM, if it is some custom stuff you would need a webservice which you can call from JavaScript and "activate the user" like that. You can of course always access the current form and pass on the values the user entered. Or you could create a custom save button which does some stuff (activate user) before saving.
Lastly: You can also have postbacks in your custom button where you could do anything you'd like.
I have a requirement to display the currently logged in user on a newItem list form the user is filling out- I have a people picker control which I know I can convert to the Rich Text format to display the current user.
However, I am having trouble getting the current user. I took a look at how SP did it, but found that they also had "Welcome " embedded into their code, so I cannot just re-use it.
Then I found this resource that showed me how to get the logged on user from the server variable. But I have no idea to display it on the form, so I don't even know if it got what I was actually looking for!
While I was poking around the code for the page, I found that I'd already had the following parameter
<ParameterBinding Name="UserID" Location="CAMLVariable" DefaultValue="CurrentUserName"/>
<xsl:param name="UserID" />
which looked like it might do the trick, but again.... I can't figure out how to display the value of it on the webpart form- so I don't even know.
How can I display the value of a parameter on webpart page so that I can verify that it is what I am looking for?
Thanks!
You can use <xsl:value-of select="$UserID" /> to display current user name.
I am trying to implement a simple trick which would hide span/label inside textbox when user starts entering text in respective textbox, and show it, on blur if textbox is empty.
(It is implemented on user sign in form)
This thing is working okay so far and here is the demo
But it fails in following scenario:
1) If user enters username, previously entered username list (the form data stored by browser when auto-complete is turned off) appears. And if user selects username with mouse-click from the list, password field gets auto-populated. Now though password field has value in it, it won't hide the span.
(keydown/focus/click/change event over textbox not helping in this case)
2) When the username/password is wrong, page reloads, username textbox has last entered value. But still the span over it is being displayed.
(I tried to check if username textbox is empty on pageload. It didn't work)
Can anyone help me fix these things?
Thanks in advance... :)
What you need i s a placholder. Placeholder have been standardized by html5
and can be easily implemented via various jquery plugin (here is one).
i suggest you use those solutions, as they are standards. the ideal solution is to use html5 and than fallback to javascript for older browsers.
Look ath this form where i implemented placholders: http://www.consiglio.regione.lombardia.it/web/crl/BancheDati/atti_si
When you insert a letter in an input field, the text disappears. It's done with the help of that plugin.
It seems that you are attempting to reinvent the wheel here. Check this already answered question on what appears to be the same subject:
how do I make an html text box show a hint when empty
Usability-wise, I don't think it would be terrible to hide the watermarks of both inputs regardless of which on was clicked/keydowned etc. Now this next option is controversial, so you have been warned...
<input name="first_name" type="text" autocomplete="off">
Just wanted to make sure you were aware of that - most often used to prevent credit card fields from autocompleting. Hope something in here this helps.