Dan huwa post ieħor tiegħi serje għaddejjin dwar kif tuża jQuery ma SharePoint.
Jekk inti tixtieq titgħallem aktar dwar jQuery, I jirrakkomanda ħafna: jQuery fl-Azzjoni billi Bear Bibeault u Yehuda Katz.

Waħda mill-ewwel affarijiet I ħsibt, ladarba I bdew jilagħbu madwar mal jQuery, was whether we could use it to secure a SharePoint view. The answer is “no” (or at least, I’m not claiming it’s possible). Madankollu, it is certainly possible to make it difficult for people to see a particular view.

I started with my sandbox environment when working on this. I wrote about that environment here: Quick u Easy: Oħloq Your Own Sandbox jQuery għall SharePoint.

To “secure” a view, follow these steps:

1. Create a view you want to secure. I did that and called it “Secured View”.

   This is what it looks like when it’s not “secured”:

   

2. Add a content editor web part to the view’s page using the trick described in the sandbox article (I.E. add “PageView=Shared&ToolPaneView=2” to the URL).
3. Figure out your SharePoint _spUserId by following these crazy steps, believe or not:
   1. Log into your SharePoint environment.
   2. In the web browser’s address field, tip: “javascript:alert(_spUserId”).
   3. Record the result (it’s “13” in my case).

      

4. Add the following javascript to your CEWP in code view:
   
   

   <script type="text/javascript" src ="../../jQuery%20Library/jquery-1.3.2.min.js"> </iskrittura> <tip b'kitba ="text/javascript"> $(funzjoni() { alert(_spUserId); var theSecuredView = $('iframe[FilterLink*=Secured View]"); jekk ((theSecuredView.length > 0) && (_spUserId == 13)) $('iframe[FilterLink*=Secured View]").ġenitur().ġenitur().ġenitur().html("<tr bgcolor = aħmar><td>No view for you!</td></tr>"); }); </iskrittura>

I’ve included that alert(_spUserId) line in there to demonstrate how this is not really a “securing” a view, but simply making it more difficult to see. More on that in a moment.

Bażikament, jQuery is looking for an iFrame on the page who has an attribute that contains “Secured View” in its value. Once it finds it, we check to see if the current user is “13”. If it is, we walk up the DOM to a <TR> tag (which I figured out by viewing source and tracing it) and then replacing that TR tag with my message. I really don’t know how robust this is (I’m very suspicious, fil-fatt), but it worked in my sandbox. If I find a better way, I’ll blog about it. This is the result:

I click the OK button and the data is replaced with a big red message:

As you can tell, the way I’ve implement this “security” solution is to allow the web part to render itself. After it finishes, I overwrite its content with my “No view for you!” message.

Despite the fact that it’s not really a “secured’” view, it’s potentially useful and with some clever work, it may eventually be securable in a more formal sense. The fundamental issue is that the client is getting all the data and then, only after it gets the data, it wipes it out. If the client is getting the data, a clever user can prevent the jQuery from running at all and see what he/she wants to see.

There are other drawbacks. This “security” approach is based off a _spUserId. We’d want to really secure based on the full SharePoint security model, or at least by user name. That becomes progressively harder, but I see some good stuff written on this subject, so I’m hopeful there’s a good answer to that problem.

The list of views themselves should be trimmed, jekk possibbli. I haven’t tried to figure that out. I assume it’s possible, but doesn’t really solve the fundamental security issue because someone could still just type the URL of the view they want (if they knew it). Madankollu, trimming makes sense. It’s a good usability feature and it helps to obfuscate things. If an end user doesn’t know that the view event exists, they probably won’t try to use it. Kultant, that’s good enough.

With luck, I’ll have more to write on this subject over time.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Dan huwa post ieħor tiegħi serje għaddejjin dwar kif tuża jQuery ma SharePoint.
Jekk inti tixtieq titgħallem aktar dwar jQuery, I jirrakkomanda ħafna: jQuery fl-Azzjoni billi Bear Bibeault u Yehuda Katz.

Preċedentement, I wrote about how to use jQuery to locate and hide a text field on a form. I didn’t care for the specific approach (I was chaining parents – that’s simply isn’t done these days, at least in families of quality).

When I first started to think about it, I knew I needed to find a <TR> to which I could invoke the hide() metodu. My early effort to find the correct <TR> was something like this:

$('tr:has(input[title = Hide Me!])");

The problem with that is that it would find every <TR> tag that had any parent relationship to the Hide Me! qasam, even if Hide Me! is nested many levels deep in <TR>’s. It turns out that on my sandbox form, that expression finds 9 different TR’s who have Hide Me! as a child somewhere in its DOM tree. I realized that I could walk back up the tree from the input field itself, so that’s how I ended up abusing parents, but it didn’t sit well with me.

I gave some thought to this and one of the things I read finally made sense: I could use the not() method to trim out <TR>’s I don’t want in my wrapped set. Li wasslitni sabiex dan:

$('tr:has(input[title = Hide Me!])").not('tr:has(tr)").hide();

The first bit finds all the <TR> tags that have the Hide Me! field anywhere in their own hierarchy. It then strips out any <TR> that also have a child <TR>. This leaves us with a single <TR> that:

1) Has no <TR> child records

2) Does have the input field as child.

We can then apply the hide() method to the resulting set and we’re done.

I’m still a bit nervous about this, but not as nervous as chaining parents.

I don’t know if this is a best practice or not. There may be a more appropriate way of identifying just the <TR> that we care about in a SharePoint form. If you know, jekk jogħġbok post kumment.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Dan huwa post ieħor tiegħi serje għaddejjin dwar kif tuża jQuery ma SharePoint.
Jekk inti tixtieq titgħallem aktar dwar jQuery, I jirrakkomanda ħafna: jQuery fl-Azzjoni billi Bear Bibeault u Yehuda Katz.

UPDATE (diġà!): I ma think ta 'mod aħjar biex jillokalizza l- <TR> tag I tixtieq li jaħbu u kiteb dwar dan hawn. You may still find this article interesting anyway so I’m leavnig it up.

Irrid li jaħbu qasam tat-test, "Hide Me!"Kif muri:

"

Il jQuery ġej ma l-trick għalija:

<tip b'kitba ="text/javascript">

  $(funzjoni() {


    $("Input[title = Hide Me!]").ġenitur().ġenitur().ġenitur().hide();

  });

</iskrittura>

Il-kodiċi huwa qal, "Issib lili oqsma kollha ta 'input li title = Hide Me!. Imbagħad, tikseb parent tagħha u mbagħad ġenitur li jmiss u l-* jmiss * ġenitur (phew!) u jinvokaw l-ġilda() metodu fuq li ħaġa, x'ikun dan jiġri jkun.

I dehret li l-istruttura ġenitur billi tiqies l-HTML għall-forma li SharePoint maħluqa kif muri:

<TR>
    <TD nowrap="true" valign="top" wisa="190px" klassi="ms-formlabel">
        <H3 klassi="ms-standardheader">
            <nobr>Hide Me!</nobr>
        </H3>
    </TD>

    <TD valign="top" klassi="ms-formbody" wisa="400px">
        <!-- FieldName="Hide Me!"
                 FieldInternalName="Hide_x0020_Me_x0021_"
                 FieldType="SPFieldText"
        -->
        <medda inti="none">
            <input
                isem="ctl00$m$g_bdb23c2c_fde7_495f_8676_69714a308d8e$ctl00$ctl04$ctl02$ctl00$ctl00$ctl04$ctl00$ctl00$TextField"
                tip="text"
                maxlength="255"
                id="ctl00_m_g_bdb23c2c_fde7_495f_8676_69714a308d8e_ctl00_ctl04_ctl02_ctl00_ctl00_ctl04_ctl00_ctl00_TextField"
                titolu="Hide Me!"
                klassi="ms-long" />
                <br>
        </medda>


    </TD>
</TR>

Din l-istampa turi l-istess, iżda markat-ġenituri:

L-ewwel ġenitur (1) is a span tag. Span’s parent (2) hija tag TD u mbagħad finalment irridu jiksbu l-ġenitur reali I tixtieq li jaħbu (3) li huwa l-tikketta TR innifsu.

This is a pretty terrible approach I think because it’s extremely dependent on the very specific structure of this form. When SharePoint 2010 toħroġ, this whole structure could change and break this approach. What I really want to do is craft a jQuery selector that is along the lines of “find me all the TR’s (u biss tags TR) li jkollhom x'imkien tfal elementi tagħhom f'qasam input li title = Hide Me!". I starting from the bottom and moving up. Assuming I figure this out, I ser post aġġornata malajr u faċli post "".

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin

Dan huwa post ieħor tiegħi serje għaddejjin dwar kif tuża jQuery ma SharePoint.
Jekk inti tixtieq titgħallem aktar dwar jQuery, I jirrakkomanda ħafna: jQuery fl-Azzjoni billi Bear Bibeault u Yehuda Katz.

Getting beda bil jQuery fl SharePoint hija sorprendentement faċli (lili). (I do have serious questions about a “best practices” approach to deploying these things to production, but that’s for another day). I’ve just started playing with this technology and to that end, I created a sandbox environment to use. If you’re looking to get started with jQuery, you may find this approach useful.

1. Create a Blank Site

Create a blank site somewhere in your site and call it something clever like “jQuery Sandbox”.

2. Download jQuery

You can download the jQuery javascript library from here: http://docs.jquery.com/Downloading_jQuery

Save that to to your desktop.

I have been using the “minified” version.

3. Create a SharePoint Document Library

In your sandbox site, create a document library.

4. Upload the jQuery Library to SharePoint

Access the doc library you just created and upload the jQuery library.

5. Create a Custom SharePoint List

I’ve started with a custom list because I want to muck about with standard SharePoint forms. You could also create a page in a pages library or web part pages and probably a lot of other places.

Add some columns to the custom list so that you have something to run jQuery against. My initial objectives were to:

1. Hide a field.
2. Assign a value to a field.

With that objective in mind, I added two text fields. Maż-żmien, I’ll be playing with links, images, lookups, eċċ.

6. Modify the NewForm.aspx Web Part Page and Add a Content Editor Web Part

This is a little black magic-ish , in that it’s a new concept to me. I first learned about this from Paul Grenier, SharePoint jQuery Superstar, at his CodePlex project site: http://spff.codeplex.com/.

Follow these steps to add a CEWP to the same page that shows NewForm.aspx for any custom list:

1. Access the custom list and click New.
2. Append the following to the URL: PageView=Shared&ToolPaneView=2

That will transform your boring vanilla data entry form from something like this:

To this:

Add the content editor web part to the page.

7. Write Your First jQuery Code

Open up that CEWP in the code view and add the following:

Here’s the actual code if you want to copy/paste:

<script
    type="text/javascript"
    src ="../../jQuery%20Library/jquery-1.3.2.min.js">
</iskrittura>

<tip b'kitba ="text/javascript">
  $(funzjoni() {

    $('#resultsID').html('There are ' + $('a').size() + ' a tags tags on this page.');

  });
</iskrittura>

Riżultat:
<div id='resultsID'></div>
/result

Note that the first <iskrittura> tag is referencing the actual jQuery library. Presumably, these things change over time, so you’ll want to make sure you a) use the right name and b) point it to the correct SharePoint document library.

Bask in the Glory

If you did it correctly, you’ll see a result similar to the following:

Wrapping Up

This isn’t the only way to get started, but it’s quick, easy and isolated from your existing SharePoint environment.

</aħħar>

Abbona għall-blog tiegħi.

Follow lili Twitter fi http://www.twitter.com/pagalvin