Posts Tagged SharePoint

SharePoint Rich Text Editor List Field strips out Target Attribute

In a custom SharePoint list definition that contains a field type which is a RTE (Rich Text Editor), I found that items added to the list would allow for anchor tags, but the “Target” attribute was stripped off when the HTML markup was saved. In the MSDN definition for the Field Element (List) I found an answer to this problem

The first step is to add the IsolateStyles property and set to false. The second step is to set the RichTextMode to “FullHtml.” After these to settings and updating the list, I was able to add the “target” attribute to an Anchor tag in the HTML markup for a list item.

In the end, this is what the field definition looks like in the list schema.xml file:

<Field ID=”{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX}” Type=”HTML” DisplayName=”Description” NumLines=”4″ RichText=”TRUE” RichTextMode=”FullHtml” IsolateStyles=”FALSE” Name=”AlertDescription” RestrictedMode=”FALSE”/>

Leave a comment

How to find the version level of SharePoint you are running?

An excellent blog article with details on SharePoint versions

To find out the SharePoint 2007 version within Central Admin, navigate to “Central Administration > Operations > Servers in Farm”

For SharePoint 2010,  go to Central Administration, under Upgrade and Migration, click Check product and patch installation status to view version numbers


Leave a comment

Backup and Restore SharePoint from Windows Internal Database

I was presented with an instance of SharePoint (WSS 3.0) that was installed on a single server that utilized SQL Server 2005 Embedded Edition or as it is now called “Windows Internal Database.”  This instance of WSS was being used internally be a select group of savvy users to “test” out the functionality of SharePoint before the roll out to the rest of the company.

We had reached a point in the process where we wanted to sunset the test instance and move the content that had been generated over several months to the production server.  The next step was to backup the web application containing that content.  The backup through Central Admin went fine, but the restore on the production server did not work.  The problem was that the service account that was restoring the database in production did not have rights to the instance that was backed up on the single server.  My first thought was, fine, I’ll just add the production service account to the security login for that content database on the single server in SQL Management Studio…  I’ll just connect to it from there.  It was then that I realized this was a “Windows Internal Database.”  How do I connect to the database?  After a little research, I found that the best way was to install SQL Server Express on the single server and connect to it using a somewhat odd connection string: “\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query”   I installed SQL Service Express, added the production service account and gave it dbcreator and securityadmin server roles in SQL Server.  The import was successful after that change. 

Sources: 1 2


Leave a comment