this error “the attribute ‘autoeventwireup’ is not allowed in this page” or “the base type is not allowed for this page. the type is not registered as safe”indicates that you need registered you dll as safer control in web.config.
Most users always suggest to detach and re-attach DB to remove the log file when dealing with large Transaction log file. There is one proper way to truncate the transaction log file to certain size. Here are the sample steps to truncate SQL Log file:
Truncate the log by changing the database recovery model to SIMPLE
ALTER DATABASE 
SET RECOVERY SIMPLE;
Shrink the truncated log file to 5 MB
DBCC SHRINKFILE ([_Log], 5);
Reset the database recovery model.
ALTER DATABASE 
SET RECOVERY FULL;
Once the user photos are in AD you need to update the SharePoint user picture property . Open Central Administration and navigate to your User Profile Synchronization Service Application. Click on Manage User Properties.
Scroll down to the Picture property and choose Edit from the drop down menu.
Scroll down to the Add New Mapping section. Choose your AD data connection, select the thumbnailPhoto attribute and click Add, followed by OK to save the change. This maps the SharePoint picture property to a user’s photo attribute in AD.
Run a full user profile synchronization.
Once the user synchronization has finished open the SharePoint 2013 Management Shell. Run Update-SPProfilePhotoStore -CreateThumbnailsForImportedPhotos 1 -MySiteHostLocation %MySiteURL%
You need to run above cmd with Farm Admin account.
once completed, the profile image will be showing in the profile
The Secrets of SharePoint Site Mailbox
A site mailbox serves as a central filing cabinet, providing a place to file project emails and documents that can be only accessed and edited by site members.
It can be used from a SharePoint team site to store and organize team email. It can also be used from Outlook 2013 that ships in Office 365 ProPlus or Office Professional Plus for team email, and as a way to quickly store attachments and retrieve documents from the team site.
User will not see a site mailbox in their Outlook client unless they are an owner or member of that site mailbox.
Secret 1: Remove Site Mailbox from outlook client
Anyone in the default owners group or the default members group for the site (anyone with Contribute permissions) can use the site mailbox from SharePoint. People can be listed in the owners or members group as individuals or as part of a security group.
There are two ways to hide the site mailbox appearing in user’s outlook
A. Managing the site mailboxes from Outlook Manually
Users can simply right click on the personal mailbox. By selecting ‘Manage All Site Mailboxes’, users will be directed to a list of all site mailboxes they have access to. They can easily pin and unpin site mailboxes to the outlook view from there.
B. But if you don’t want users to see the site mailbox from the outlook at all. Here is the tip, do not add users to the default members or owners group of the SharePoint site. Create a separate SharePoint group with Edit permission and add users to the new group so that they can still access the site mailbox through the web but the mailbox will not appear on their outlook.
Secret 2: Rename an existing site mailbox
Here is another tip, what happened if users are not happy with site mailbox name appears on the Global address list? There is lots of efforts to delete the site mailbox and reassign the permission.
But here is the work around, you need to follow the steps below:
- In Office 365 admin center > Active users, find the site mailbox.
- Choose the site mailbox and edit its display name.
- Then go to the site with the mailbox, go to Site Settings -> Title, descitption and logo
- Update the Title with the new site mailbox name too
NB: if you did not update the site name, Exchange will reverse back the site mailbox name back to the site name. Smart enough, isn’t it 🙂
<Control Id=”AdditionalPageHead” Sequence=”93″ ControlAssembly=”$SharePoint.Project.AssemblyFullName$” ControlClass=”RibbonCustomization” />
<Control Id=”AdditionalPageHead” Sequence=”94″ ControlAssembly=”$SharePoint.Project.AssemblyFullName$” ControlClass=”ScriptsRegistration” />
<Control Id=”AdditionalPageHead” Sequence=”95″ ControlAssembly=”$SharePoint.Project.AssemblyFullName$” ControlClass=”SomeOtherActions” />
<Control Id=”AdditionalPageHead” Sequence=”500″
You can check the result element file via going to the Feature folder under “\15\TEMPLATE\FEATURES\”
How site columns become managed properties
When you add columns to a SharePoint library or list, you can choose to add regular columns or site columns.
In SharePoint Server 2013, only site columns that contain values will automatically become managed properties when they are crawled. Regular columns will not automatically become managed properties when they are crawled.
In SharePoint Online, content is automatically crawled based on a defined crawl schedule. The crawler picks up content that has changed since the last crawl and updates the index. In some cases, you may want to manually request crawling and full re-indexing of a site, a document library, or a list.
Re-index a site
WARNING Re-indexing a site can cause a massive load on the search system. Don’t re-index your site unless you’ve made changes that require all items to be re-indexed.
- On the site, click Settings > Site Settings.
- Under Search, click Search and offline availability.
- In the Reindex site section, click Reindex site.
- A warning appears, click Reindex site again to confirm. The content will be re-indexed during the next scheduled crawl.
Re-index a document library or a list
- On the site, go to the list or library that you want to re-index.
- In the ribbon, click the Library tab or the List tab.
- In the Library ribbon, choose Library Settings,
In the List ribbon choose List Settings.
- On the Settings page, under General Settings, choose Advanced settings.
- Scroll down to Reindex Document Library or Reindex List, and click the button. The content will be re-indexed during the next scheduled crawl.
Re-index after changing managed properties
When people search for content on your SharePoint sites, what’s in your search index decides what they’ll find. The search index contains information from all documents and pages on your site.
The search index is built up by crawling the content on your SharePoint site. The crawler picks up content and metadata from the documents in the form of crawled properties. To get the content and metadata from the documents into the search index, the crawled properties must be mapped to managed properties. Only managed properties are kept in the index. This means that users can only search on managed properties.
When you have changed a managed property, or when you have changed the mapping of crawled and managed properties, the site must be re-crawled before your changes will be reflected in the search index. Because your changes are made in the search schema, and not to the actual site, the crawler will not automatically re-index the site. To make sure that your changes are crawled and fully re-indexed, you must request a re-indexing of the site. The site content will be re-crawled and re-indexed so that you can start using the managed properties in queries, query rules and display templates.
You can also choose to only re-index a document library or a list. When you have changed a managed property that’s used in a library or list, or changed the mapping of crawled and managed properties, you can specifically request a re-indexing of that library or list only. All of the content in that library or list is marked as changed, and the content is picked up during the next scheduled crawl and re-indexed.
Learn more about search and crawled and managed properties in Manage the search schema in SharePoint Online.
In SharePoint Online, when you create a new managed property, it will have some limitations. For example, the property can only be of typeText or Yes/No, and it can’t be refinable or sortable.
Yup, no sorting for you, and no refinement panel goodness. And no search queries against date ranges. You can potentially search for a particular date, but not ‘between 1st Feb and 23rd March’.
I hope Microsoft can improve this function at least provide date ranges for the search query