Configuring claims and forms based authentication for use with a SQL provider in SharePoint 2010

http://sharepointchick.com/archive/2010/05/07/configuring-claims-and-forms-based-authentication-for-use-with-a.aspx

SharePoint Branding Limitations

• Partner Spotlight : Tam Tam
• SharePoint’s Branding Limitations, Part 1
• SharePoint’s Branding Limitations, Part 2
• SharePoint’s Branding Limitations, Part 3
• SharePoint’s Branding Limitations, Part 4

Introduction

As a Front-end Developer with a background in designing I’ll show you how to make a graphical design that works for a default SharePoint-environment. If you want to take control over the front-end, don’t use any themes. Create your art by using style sheets!
Not all graphical designs for a portal will work in a SharePoint environment. There are a couple of limitations the Graphical Designer must know. A Graphical designer needs to know the scope of the graphical design. For example, if a Graphical Designer puts a border on an element like a table, that will take him about 3 minutes to design, but this simple border could take the Front-end Developer a few hours to implement.
It’s really important that the Graphical Designer and the Front-end Developer work together and have a clear communication about the graphical design. Making a graphical design specifically for a MOSS environment could save you days on the implementation! This article will give the Graphical Designers more insight into the effect of these design decisions.
This article assumes that the reader has SharePoint and basic HTML knowledge.

Web parts

This section is all about SharePoint’s web parts. First the display mode of the web parts will be the point of interest, then the Edit mode, and after that the Article page layouts will be discussed.
The <td> with class name .ms-bodyareacell is the overall container for the content. Inside this <td> is a table with class .ms-propertysheet, and a td.ms-bodyareaframe inside that there is another table. These are the containers for the content on a page and are being defined in the page layout. Inside the .ms-bodyareaframe are a few nested tables and one of these tables is the table of a web part.

Web part ID’s

If a web part is placed inside a web part zone, it will get an ID. Depending on the amount of already placed web parts on that page, and the order in which they are placed, the ID will get its tracking number. It does not change when you change the order of the web part zones. So therefore, the ID of the web part actually isn’t unique, it is just unique for that page.

The web part in this example is the third web part of the page and as you can see, it carries number 3 in the ID. The search interface in the header is always the first web part of the page. In this case there were two web parts placed on the page, which together with the search makes three: the ID number of the last placed web part. If you want to style the web part in its entirety, you can only list all the web part ID’s and add styling to them. This nasty solution is the only solution to styling every web part on itself. A better solution would be for example to style the elements inside the web parts, such as the .ms-WPBody.

..
#MSOZoneCell_WebPartWPQ27,
#MSOZoneCell_WebPartWPQ28,
#MSOZoneCell_WebPartWPQ29,
#MSOZoneCell_WebPartWPQ30{
     Border:1px #f2f2f2 solid;
}

Because every web part has a <td> and inside that a table as a container, it is possible to style the background of the web part with two background images, but it is very tricky an I advice you not to do so. Make sure every <td> with ID #MSOZoneCell_WebPartWPQ2 (a web part ID of your choice) has a background image. Then style every table inside the <td> with those ID’s with another background image. Secondly, hide every background image on every second or more nested table inside the <td> with the web part ID.
Here’s an example of how, just for web part ID 3:

#MSOZoneCell_WebPartWPQ3{
     Background:transparent url(images/webparttop.jpg) repeat-x left top;
}
#MSOZoneCell_WebPartWPQ3 table{
     Background:transparent url(images/webpartbottom.jpg) repeat-x left top;
}
#MSOZoneCell_WebPartWPQ3 table table{
     Background:transparent none;
}

Which means “only apply if table is the first element inside #MSOZoneCell_WebPartWPQ3“, because it is not supported in Internet Explorer 6 and older versions.
Unfortunately you cannot use

#MSOZoneCell_WebPartWPQ3 > table {
     ..
}

Make sure the images you use are repeatable on the x-axis. If they are not, you will need to make a new page layout where the web part zones have a static width (set in the style sheet of course). This way you can control the width of the web parts in a particular web part zone, and make your background images as wide as the web parts.

Web part headers

Inside the <td> with the web part ID is always a table with two <tr>’s. The first one is for the header of the web part, the second one is for the content of the web part.

The first class you can use to style the header is the tr.ms-WPHeader. This <tr> has two <td>’s, one for the title of the header, and another one for the little arrow on the right pointing down. Only the first <td> has an ID, which has the same ID-number as the web part-ID. To style the background and the borders of the header, you can style every <td> inside the .ms-WPHeader.

.ms-WPHeader td {
     border-bottom:1px solid #4E7CB7;
}

To style the text of the header, style the .ms-WPTitle. Be aware that some web part titles contain a hyperlink. The little arrow is also a link, and to style that you can style the <a>-tag inside the <td>, and then overrule the styling for the header text. Like this:

/*This styles every link in the header*/
.ms-WPHeader td a{
 background-color:#000000;
}

/*This styles every textual link in the header*/
.ms-WPHeader .ms-WPTitle,
.ms-WPHeader .ms-WPTitle a:link,
.ms-WPHeader .ms-WPTitle a:visited{
 color:#4F3B2F;
}

It is possible to hide the header by changing the settings of the web part. Choose “appearance” and in the “chrome type” drop down and choose “none”. The <tr> with the header will not be rendered then.

Content Editor Web parts

The <td> of the second <tr> of the #MSOZoneCell_WebPartWPQ contains a <div> with a web part ID that has the ID number related to the amount of web parts on the page, like #WebPartWPQ3. It also has a class called .ms-WPBody. The core.css uses this class to set the font family and size.

When using a Content Editor Web part, text is placed directly in the .ms-WPBody. The color of the text is set by the styling in the core.css, on the .ms-propertysheet and the body tag. The same goes for the hyper links in the text.

Lists

In a list web part, there is a table.ms-summarycustombody class, in where all the links are positioned. Every <td> has a class.

Depending on what list with hyper links you use, the <td>’s will have one of the following class:

.ms-vh,
.ms-vh2,
.ms-vh-icon,
.ms-vh-icon-empty,
.ms-vhImage,
.ms-gb,
.ms-gb2,
.ms-gbload,
.ms-vb,
.ms-vb2,
.ms-vb-tall,
.ms-GRFont,
.ms-vb-user,
table.ms-disc td,
.ms-vh2-nofilter,
.ms-vh2-nograd,
.ms-vh3-nograd,
.ms-vh2-nograd-icon,
.ms-vh2-nofilter-icon,
.ms-pb,
.ms-pb-selected,
.ms-ph {
     font-family:tahoma,sans-serif;
     font-size:8pt;
}

The first two of this list are for example also used for list headers. Most graphical designs will have the same styling for all hyper links on the portal, so you can add your styling to the above classes and their <a>-tags. The “add new” (add new announcement, add new event, add new link, etc. ) hyper links can be styled with their own class, for example: a.ms-addnew. Here’s an example of how you could style the lists.

Data table

SharePoint uses tables and lists to display its data. The Document Center is one of those ‘data tables’. The Document Center uses another page layout, because the purpose of the page is to show a big list with data and no text like articles. Therefore the Document Center has one web part zone that uses the whole width of the page. When styling the web parts, make sure the lists of the Document Center (Documents, Announcements, Tasks) are styled correctly. Pay special attention to the list headers here and make sure the fly outs of the top navigation are positioned above the list headers. If they are, make sure you position the .ms-vh div and .ms-vh2 div statically.

Width

Sharepoint comes with a set of page layouts. These page layouts have middle and right zones, but they do not always have an ID or class name for those zones. If you want to control the width of the web parts in either the middle or the right column, you need to create new ones, based on the existing page layouts. Make sure every web part zone has an ID or class, so you can set the width of those in the style sheet.

Edit mode

In edit mode the styling is usually kept default. Most of the classes and ID’s of the content are different when in edit mode, so the styling of elements inside web parts is rather easy to separate, but the web parts themselves aren’t. When editing a page, some web part zones and web parts will get other class.

System pages like the “site settings”-page and the “all site content”-page only contain the same header elements. The rest of the page has classes that are not used on the front-end. Therefore you can style those pages differently. I advise to only change the colors and fonts and leave the layout and the positioning the way it is by default. This way you won’t corrupt the usability of the system pages.

News articles

When creating a news article, it is possible to choose between several news article layouts; the page layouts. The first page layout for an article page is the “article page with body only”. Other page layouts are the “article page with image on left”, “article page with image on right” and the “article page with summary links”.

Article page with body only

This page contains a page content zone and a roll up image. When publishing the page, all the content will be inside the #MSO_ContentTable. Inside that is the div.pageContent.

Since the div.pageContent is an element of every news article page layout, you cannot set the width of the element. Styling this element will cause other page layouts also to be adjusted.

Article page with image on left

The second page layout is the “Article page with image on left”.

This page layout has the following elements:

• Page image
• Article date
• Byline
• Page content
• Image caption
• Roll up image

Page image
The .bodyareaframe contains two tables and some <div>’s. The first table has the property float:left. This makes the image positioned to the left of the text.

Article line and byline
The second table of the .bodyareaframe is the header. It contains two cells, one for the article date (.dateLine) and one for the “byline”.

Page content
The div.pageContent contains a div#ctl00_PlaceHolderMain_Content__ControlWrapper_RichHtmlField, which contains the text. The ID is not unique for this piece of page content, it is only unique on this page.
Other page layouts use the same ID, so by styling this element, the text looks the same, no matter what article page layout is chosen.

Article page with image on right

The “article page with image on right” has got the same fields and controls as the “Article page with image on left”. The only difference is the floating. Where in the “Article page with image on left” the table was floating left, here the table has no floating, but a <div> around it has a right floating. There’s an extra container div, the .articleLayout that was not in the “Article page with image on left”.

Article page with summary links

The “Article page with summary links” has, instead of the page image and image caption, a Summary Links control. These links are positioned inside a table that is floated to the right.

Next time in “SharePoint’s Branding Limitations”

Next time in part four of “the Art of SharePoint, how to make a graphical design work for SharePoint”, I will discuss some design decisions for search pages and the My Site. Other points of interest are the styling of the calendar and date picker and the use of SIFR.

Series Navigation

Share

Articles, Developer

SharePoint’s Branding Limitations, Part 2

SharePoint’s Branding Limitations, Part 4

Fatal error: Cannot use object of type PEAR_Error as array in /home/spm/public_html/wp-content/themes/headlines/threadposts.php on line 16

Configure Disaster Recovery Farm with SharePoint 2010

http://blogs.technet.com/b/mahesm/archive/2010/04/30/configure-disaster-recovery-farm-with-sharepoint-2010.aspx

Configure Disaster Recovery Farm with SharePoint 2010

mmohanty

30 Apr 2010 6:48 PM

• Comments 4

If you haven't read and still looking for the information on DR farm configuration with MOSS 2007 then you can refer the TechNet article. In this post i have explained how to configure the DR farm with SharePoint 2010 and what are the improvements we have in SharePoint 2010 as compared to MOSS 2007.
You can configure SharePoint 2010 DR farm using SQL Log shipping or SQL database mirroring for SharePoint databases. Before i start SharePoint 2010 DR farm configuration, I want to give an overview of SQL database mirroring, SQL log shipping and what can be used. In this post i am going explain followings.

1. Overview to SQL Database mirroring
2. Overview to SQL Log shipping
3. What can be used for SharePoint 2010 DR Farm configuration
4. SharePoint 2010 DR Farm configuration using SQL Database mirroring
5. SharePoint 2010 DR Farm configuration Using SQL Log Shipping
6. Comparison
7. Changes required when you failover

Overview to SQL Database Mirroring:
Database mirroring feature is available in SQL 205 and SQL 2008. Its a solution to provide database high availability and its configured per-database basis. You can only configure the database mirroring for the databases that use the full recovery model. You cannot configure the database mirroring for the System Databases (master, msdb, tempdb & model).
In database mirroring there will be 2 copies of a single database residing on 2 different SQL instance. One SQL server instance act as Primary server and holds the active databases. All the clients or applications connect to this database server. Other SQL Server instance act as Secondary server or mirror server which holds the hot or warm databases. Once the database mirroring has been configured and databases are synchronized state, failover can be performed without a loss of data. While you configure the SQL database mirroring you can also configure the Witness server. This is going to another SQL instance which would be monitoring the primary SQL server instance. If primary SQL Service fails then witness server will automatically failover the databases from primary SQL server instance to Secondary SQL server instance.
There are 2 operating modes for configuring Database mirroring:

• Asynchronous: This doesn't need the Witness Instance, that means there is no automatic failover. Once the Database server is not available administrator to stop the database mirroring session manually.
• Synchronous: You can configure this with witness server (optional). If you configure with witness server then you get the advantage of automatic failover feature. However, automatic failover requires both the databases to synchronized.

Lets look at the advantages and disadvantages of database mirroring.

• Database Mirroring Advantages:
  • Easy setup and maintenance
  • Real-time synchronization of transaction log
  • Automated failover (in High Availability Mode, Witness Server Instance required)
  • Fast & easy Failover
  • Using connection strings you can make your application mirroring aware or using SQL alias.
• Database Mirroring limitations:
  • Database mirroring is configured per database not per SQL server Instance.
  • Mirror database always in recovery mode and this database can’t be used for any purpose or database queries.
  • Database mirroring can only configured for one database to another database. There can’t be more secondary server.
  • Database mirroring can’t be configured for once database once than once.

Note:- Database mirroring can be configured for the databases having Full Recovery Model. Database mirroring can not be configured for the databases which is using Simple Recovery Model.

Overview to SQL log Shipping:
SQL log shipping allows to backup the transaction logs from primary SQL Server instance in regular interval to one or multiple secondary SQL Server instance. Transaction log backup are restored to all the Secondary SQL Server instances individually. SQL Log Shipping consist of 3 operations:

• Backup transaction log from the primary server
• Copy the transaction log backup to the secondary server or secondary servers
• Restore the transaction log backup to the secondary server instance

Above 3 operation will create 3 jobs on SQL Servers. Backup Job will be only available on Primary SQL Server instance. However, Secondary SQL Server instance contains the Copy job and Restore job. All these job executes in regular interval and you can define the time. SQL agent service has to be on running for log shipping.

• Log Shipping Advantages:
  • Flexibility to backup, copy and restore the transaction logs.
  • Due to scheduled jobs database corruption can be avoided.
  • Multiple secondary databases can be configured
  • Secondary databases are in read-only and standby mode and can queried if required.
  • Log shipping allows multiple standby databases
  • Log Shipping disadvantages:
• Log Shipping Disadvantages:
  • No option for automatic failover
  • Minimum time to synchronize is a min. which can be configured. 
  • For failover need to execute SQL Query. not simple as database mirroring.

Note:- Transaction Log Shipping can be configured for the databases having Full Recovery Model. It can not be configured for the databases which is using Simple Recovery Model.

What can be used for SharePoint 2010 DR Farm Configuration:
For SharePoint 2010 Disaster Recovery Farm configuration you can use both. However, if you use Database mirroring then databases on Secondary SQL Server or Databases on Secondary Datacenter will be on restoration mode which you cant attach to the web application. I would always recommend to use SQL log shipping for SharePoint 2010 DR Farm configuration. Again, SQL database mirroring is mostly used for HA and SQL log shipping is used for DR. On this post i will be explaining DR farm configuration with both and compare at the end so you can choose what's best for you.
SharePoint 2010 DR Farm Configuration using database mirroring:
To configure the DR Farm using Database mirroring, you need to start a fresh installation of SharePoint 2010 on Secondary Datacenter. You should have below:

• Install and Configure SharePoint 2010 Farm in Secondary datacenter in same AD Forest using Primary SharePoint farm Service accounts
• Install the customizations which are present on primary farm
• Create all the web applications which are present on primary farm
• Create all the Service applications
• Detach the content databases from the web applications and delete the content databases
• Configure the mirroring only for content databases from Primary SQL server to Secondary SQL server. By Default all the content databases uses Full Recovery Model. If you have changed the Recovery Model for to simple for any content databases, it will not allow you to configure database mirroring unless you change the recovery model back to full recovery model.
• Create database mirroring without the Witness server for all the SharePoint Content Databases only. No witness server required as database mirroring would be used for High Availability and auto-failover is not required

To configure Database mirroring using SQL management Studio you can follow the MSDN Article.

Note:- Do not configure database mirroring with Witness Server. Database status on Primary SQL server would be “(Principal, Synchronized)”. It might take a while to reach that status. Database status on Secondary SQL server would be “(Mirror, Synchronized / Restoring..)” As soon as the database mirroring has been configured transfer the SQL logins from Primary SQL Server to Secondary SQL Server following Support Article. If you feel following support article is difficult then you need to create the logins manually, assign them appropriate roles. If you don’t transfer the SQL logins then after fail over you will not be able to connect to SQL databases and you will be receiving errors on SharePoint servers. On Secondary SQL Server, you cant change the database status from SQL management Studio. To change the status of the database you need to execute the below SQL query: ALTER DATABASE ContentDatabaseName SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS

 SharePoint 2010 DR Farm Configuration using database log shipping:
To configure the DR Farm using database log shipping, you need to start a fresh installation of SharePoint 2010 on Secondary Datacenter. You should have below:

• Install and Configure SharePoint 2010 Farm in Secondary datacenter in same AD Forest using Primary SharePoint farm Service accounts
• Install the customizations which are present on primary farm
• Create all the web applications which are present on primary farm
• Create all the Service applications
• Detach the content databases from the web applications and delete the content databases
• Create the log shipping for the content databases only. By Default all the content databases uses Full Recovery Model.If you have changed the Recovery Model for to simple for any content databases, it will not allow you to configure database mirroring unless you change the recovery model back to full recovery model.

To configure Database log shipping using SQL management Studio you can follow the MSDN Article.

Note:- Database status on the Secondary Server would be “Stand by / Read-only”. As soon as the database log shipping has been configured transfer the SQL logins from Primary SQL Server to Secondary SQL Server following Support Article. If you feel following support article is difficult then you need to create the logins manually, assign them appropriate roles. On Secondary SQL Server, you cant change the database status from SQL management Studio. To change the status of the database you need to execute the below SQL query:       RESTORE DATABASE contentdbname WITH RECOVERY

Comparison of using SQL database mirroring or Log Shipping for SharePoint DR farm.
Database Mirroring:

• In database mirroring Real time transaction log shipping to secondary SQL Server. Incase of primary SQL server failure latest information will be available on Secondary SQL Server.
• As Database on Secondary SQL Server would be “Mirror, Synchronized / Restoring” We will not be able to attach the databases to web application on DR farm. Incase of Failover we will need to make the databases active and attach the databases to web applications.
• After failover when we attach the content database to the web application, it will automatically refresh the site map on Configuration database.
• As we cant attach the databases to the web applications, Search Service Application wont be able to crawl the content. After Fail-over you need to crawl the content.
• When failover happens we need to run SQL script to make the all content databases writeable.

Database Log Shipping

• In Log shipping transaction log backup, copy and restore happens on scheduled time (Minimum time 1Min). Incase of fail-over from primary SQL Server to Secondary SQL Server we might loose some data if that's not restored on SQL Secondary SQL Server or manually restore the transaction log backup to Secondary SQL Server database.
• As Database on Secondary SQL Server would be “Stand by/ Read-only” It will allow you to attach the databases to web application on DR farm and we can crawl the content using Search Service Application.
• As the databases are attached to the web application we can run a script to refresh the Site Map on Configuration database.
• As we cant attach the databases to the web applications, Search Service Application wont be able to crawl the content. After Fail-over you need to crawl the content.
• When failover happens we need to run SQL script to make the all content databases writeable.

Changes required when you failover from Primary SharePoint 2010 to SharePoint 2010 DR Farm.
If you are using SQL database mirroring:

• On the DNS Server make the changes so that all the request can be reached to DR Farm SharePoint 2010 WFEs.
• Run the SQL Query to make the database active. (ALTER DATABASE ContentDatabaseName SET PARTNER FORCE_SERVICE_ALLOW_DATA_LOSS)
• Attach content databases to the web applications.
• Start a full Crawl process on Search Server.

If you are using SQL database log shipping:

• On the DNS Server make the changes so that all the request can be reached to DR Farm SharePoint 2010 WFEs.
• Restore all the pending transaction logs backup to database.
• Run the SQL Query to make the database active. (RESTORE DATABASE contentdbname WITH RECOVERY)
• Start an Incremental Crawl process on Search Server. After knowing both the options, now you can choose between database mirroring and Database log shipping for DR farm configuration.

XSLT Get current and last row position in itemstyle.xsl

http://pholpar.wordpress.com/2010/01/21/displaying-results-in-multiple-columns-using-the-content-query-web-part/

Top Sharepoint Site

http://www.woodside.com.au/
http://about.sensis.com.au/products/

CSS Round Corner

http://www.search-this.com/2007/02/12/css-liquid-round-corners/

حلقة خدمات الشيربوينت

SharePoint 2010 For Students – Baby Steps (3), Arabic Version

By Rand

حلقة خدمات الشيربوينت

اذا أثارت موضوعاتنا السابقة اهتمامك فيما يخص الشيربوينت، من الممكن أن تكون قد قمت ببحث عن ماهية هذا المنتج، وباعتقادي أيضاً أن هذه الصورة قد مرت على ناظرك في مكان ما، وتساءلت عن ما تعنيه أو أهميتها، هذا ما سنتحدث عنه في هذه التدوينة.

هذه الصورة تمثل الخدمات المقدمة من منتج الشيربوينت، أو، بعبارة أخرى، ما يمكن أن تقدمه لك كمستخدم.

لنبدأ بـ المواقع : من المعروف أن الشيربوينت يقدم لك خدمة بناء المواقع، قد تقول: "أين الجديد!"، الأمر لا يتوقف عند هذا الحد، ليس عليك أن تكون مبرمجاً محترفاً لتقوم بانشاء موقع باستخدام الشيربوينت، كل ما عليك فعله هو اختيار النموذج المناسب لك، والقيام بعدة نقرات بسيطة بواسطة الفأرة، لتجد أن الموقع أصبح جاهزاً.

مواقع الشيربوينت تختلف عن المواقع الأخرى بأنها تسمح للمستخدم بالتفاعل بدلاً من القراءة وحدها، أي انه يمكن لأي مستخدم  تغيير محتواها، اضافة الصور، وأشياء كثيرة أخرى يمكننا التحدث عنها لاحقاً.

أما بالنسبة لـ المجتمعات، تعطيك الشيربوينت أدوات تمكنك من بناء بيئة تفاعلية تتواصل من خلالها مع الآخرين، وبناء مواقع مخصصة لهذه الأهداف، كمواقع لفرق العمل والشركات، كما يمكن تحرير نفس المستند من عدة مستخدمين كما ذكر سابقاً

هذا المنتج الضخم يوفر لك الإمكانية لحفظ المحتويات بدلاً من حفظها على جهازك، الصور والمستندات وكل ما يخصك، يمكنك بناء مكتبات خاصة بك وحفظها تحت الفئات التي تناسبك، ثم تخصيص مستوى الخصوصية الخاص بك ومشاركتها مع من تختار من المستخدمين الآخرين.

عندما تكثر المحتويات، هذا يعني أنك بحاجة لمحرك بحث لأيجاد ما يعنيك بأسرع وقت ممكن، لم يغفل مطورو الشيربوينت هذه الخاصية أيضاً، حيث قامو بتطوير محرك بحث عملاق له من الخصائص ما يمكنك من تحديد نوع البحث وتخصيصه الى أبعد الحدود، والتوسع الى البحث داخل المستندات أو بخصائصها (كتاريخ الإنشاء أو اسم المؤلف) وحتى البحث عن أشخاص أيضاً.

مع الشيربوينت، لن تتعامل مع المعلومات بالطريقة التقليدية بعد اليوم، فهي تمكنك من ترتيب المعلومات بطريقة متقدمة ومحترفة وغير يدوية، كالرسوم البيانية باستخدام برنامج الفيزيو أو جداول البيانات أو نظم الأعمال الذكية، يمكنك بعدها من القيام بأتخاذ القرارات بناء على نتائج هذه المعلومات. لذلك من الممكن اعتبار هذا المنتج منتجاً تجارياً لأصحاب الأعمال بامتياز.

هذا باختصارٍ شديد ما يمكن أن تقدمه لك الشيربوينت مع العلم أن كل مجالِ من هذه المجالات يحتاج أشهراً للدراسة والتعمق، وله المختصين والمحترفين به، لذلك يمكنك اختيار المجال الأنسب لك واحترافه.

يمكن لهذا الرابط توضيح الموضوع بشكل أكبر : حلقة خدمات الشيربوينت 

أتمنى أن تكون هذه التدوينة قد ساهمت في معرفة ماهية هذا المنتج بشكل أفضل للقارئ، كما أتمنى أن تعم الاستفادة في التدوينات القادمة أيضاً

يمكنك أيضاً قراءة هذه التدوينة باللغة الانجليزية : تعلم الشيربوينت للمبتدئين الحلقة الثالثة

كما يمكنك قراءة

 تعلم الشيربوينت للمبتدئين – الحلقة الثانية

تعلم الشيربوينت للمبتدئين – الحلقة الأولى

Jquery World Map highlight

Jquery World Map highlight :
http://davidlynch.org/js/maphilight/docs/

Example Customize RSS Viewer XSL

My Example on Customize RSS Viewer XSL:

Like Button for sharepoint 2010

To get started, just use the configurator on this site:

http://developers.facebook.com/docs/reference/plugins/like/

Filter Content Query Web Part based on page field value and query string

I wanted to blog about this excellent feature in SharePoint 2010 CQWP for quite a long time and here it is.
Can I filter my CQWP based on a field’s value in the current page?

Create a Forms Login Web Part for SharePoint 2010

On your way to branding a public-facing SharePoint 2010 site, you may at some point find yourself eye-to-eye with its bare, unfeeling, and unskinnable default login page. Giving life to this page is a dicey affair—it is located under the _login directory in the hive, way outside the jurisdiction of your site’s master pages. It uses the simple.master master page, which, from a design standpoint, might as well be an empty text file.

Microsoft.SharePoint.IdentityModel library. This avails to us the SPClaimsUtility class, which houses a method that nicely black-boxes the messy logging-in part of our exercise. Look sharp, though—this evasive batch of IL doesn’t appear on the Add Reference dialog’s regular assemblies menu. Instead, you will have to browse from the dialog to the find the DLL under C:\Windows\assembly\GAC_MSIL\Microsoft.SharePoint.IdentityModel\14.0.0.0__71e9bce111e9429c.CreateChildControls method so thoughtfully provided by our IDE, we want to add a standard ASP.NET Login control, tweak a couple of key properties, and add handler methods for its Authenticate and LoggedIn events.SPUtility class to redirect the user to the given ReturnUrl:We can now place this web part anywhere in the site—preferably in an anonymously accessible area. I suppose if you were really touched in the head, you could secure it, too.

XSLT Dynamic News Slider for MOSS

XSLT - Dynamic News Slider for MOSS

http://www.baltimoresug.org/Resources/tutorials/Tutorials/Dynamic%20News%20Slider%20for%20MOSS%202007.aspx

XSLT Capability - Scrolling News Aggregator in SharePoint

Example on XSLT Capability - Scrolling News Aggregator in SharePoint:

http://www.endusersharepoint.com/2009/11/13/scrolling-news-aggregator-in-sharepoint/

Cufon the easiest way to use any font you wish

Cufon the easiest way to use any font you wish
http://cufon.shoqolate.com/generate/

How to use:
http://net.tutsplus.com/articles/news/the-easiest-way-to-use-any-font-you-wish/

JQuery Ressources

JQuery Ressources

http://codecanyon.net/

http://www.htmldrive.net/

• Menu & Navigation (183)    

• Slideshow & Scroller (176) 

•  Image Effects (96)

• Tabs (38)

• Accordion (23)