Managed Metadata Navigation not showing to users

14. February 2016 20:13 by Mahmoud Farhat in SharePoint 2013  //  Tags:   //   Comments (0)

Once you are created a Managed Metadata service and created group, term-set and terms and setted up navigation to use Managed Navigation (Managed Metadata Service).

you will find this case when you are logged-in as a farm admin then you will be able to view the navigation and when when you browse site as anonymous site. the public users are not seeing navigation.

 

Solution

You have to make sure that simple link or header is selected for the terms 

SharePoint Error: There are currently no approval tasks assigned to you

Sometimes you get this error "There are currently no approval tasks assigned to you" with SharePoint sites based on "Publishing site with workflow" template and usually your user have the all rights (Full Control) 

Solutions:

1- Make sure that you are using new user with any roles that you want Ex:Full control but it should be different than Farm Administrator (System Account) as we usually do this mistake in our development machine

2- The important part to allow your user to approve your content, it should be to add your User inside the SharePoint Approval Group

Note:

The SharePoint development best practice is you shouldn't use the Farm Administrator in you development machine or testing because this is not real case in production and according to the system account user role, he passed everything

 

Handling custom HTTP error messages on IIS 7 by SharePoint 2010

HTTP errors are returned to the client when something goes wrong on the server. Error status codes are returned if the requested file isn't found (404), or due to coding errors in the web page (500), and due to temporary issues such as failed database connections (500). The most common errors are 404 (file not found) and 500 (application) errors.

Check the following list of IIS errors

  • 400 Error (bad request)
  • 401 Error (unauthorized)
  • 403 Error (forbidden)
  • 404 Error (not found)
  • 500 Error (internal server error)

How to Custom HTTP Errors?

To implement SharePoint support of the custom HTTP error you have to editing in WebConfig file by adding the below section inside <system.webServer> tag and then you can replace "/Pages/404.aspx" with your own dynamic page.

<httpErrors errorMode="Custom" existingResponse="Auto">
     <remove statusCode="404" subStatusCode="-1" />
           <error statusCode="404" prefixLanguageFilePath="" path="/Pages/404.aspx" responseMode="ExecuteURL" />
</httpErrors>

Actually the important part in the above snippet code is in <httpErrors errorMode="Custom" existingResponse="Auto"> because if you are working in SharePoint Config file you have to add to the httpErrors element setting error mode to custom and this will inform IIS to you out custom page.  


Note:

This configuration is just supported in newest versions of IIS starting from IIS7

Difference between List Definition, List Template and List Instance

25. January 2012 01:04 by Mahmoud Farhat in SharePoint 2010  //  Tags:   //   Comments (0)

 List Definition:

A list definition defines a schema for a SharePoint list. It contains information on what views are being used, which columns and content types are being used, and other metadata information.
 

List Template:

A list template can either be created by end users through the SharePoint user interface using an existing list as a pattern or using an existing list instance. If based on a user-created list it is called a custom list template. A custom list template includes everything that defines the list, including list columns and site columns used by the list, content types used by the list, views defined for the list, and so on.
 

Tips

A list template may sound like a list definition but they are effectively the same thing, a pattern for a SharePoint list. They differ mainly in how they are created:

- A list templates are created in SharePoint or SharePoint designer.
- A list definitions in Visual Studio.


List Instance:

A list instance is an instance of a specific SharePoint list definition or list template. All of its data is stored in the relevant content database. Typically a list in SharePoint used by end users to enter and view data and it is based on either a list template or list definition.


References:
Addison Wesley - SharePoint 2010 Development with Visual Studio 2010

Sharepoint 2010 Build Error: Failed to extract the cab file in the solution

As usual we faced some problems in SharePoint 2010 during building without more clarification or description to know what is the error message means?  so you have to investigate and search by yourself which part of the solution this problem? How to fix it?

but furthermore i am still like Microsoft :)

Error Message: Error occurred in deployment step 'Add Solution': Failed to extract the cab file in the solution.

This happen with me during deployment because there is image name in my layout folder contain brackets like "add(2).png" So you have to check if you have any files with special characters including brackets ' copy (2) filename ' and remove them.

Solution: To work around this problem, remove any parentheses in the names of SharePoint project items.


Here’s a list of some problems:
http://msdn.microsoft.com/en-us/library/ee330922.aspx