I am the owner of a sharepoint (online) site, and enabled a library files versioning.
I see the "version history" option, but there is an user who can't see it. I tried granting different (all!) permissions, but he still can not see this. What I'm missing?
Normally, as long as Versioning is turned on, you can view the Version History option.
It is recommended that you do the following troubleshooting：
1.Switch to the classic mode for viewing
2.Create a new Document library to test to see if the userself is the problem
3.Clear the browser cache or test with another browser
Related
Is there any way to make a full backup of Sharepoint Online web site based on Office 365 without third-party tools? Tried to google it, but found only ways to manually backup list or libraries. I'm need to save user properties, permissions, webparts, etc.
Thanks for help!
Since it is SharePoint online, you won't be able to perform a full-backup as you'd be able to do with Backup-SPSite.
However, you can save your site as a template. If your publishing feature is enabled for this site, you'll need to enable saving the website as a template via SharePoint Designer. Under the "Site" tab, select “Site Options”, find "SaveSiteAsTemplateEnabled" and set to "true". Then
add this to your site's url:
/_layouts/15/savetmpl.aspx
Fill out and submit the form. In my experience, that should take about 10 minutes, or the working on it screen might never change. If the later happens, you can check for your solution on this page:
/_catalogs/solutions/Forms/AllItems.aspx
This option might not work if your site is over 50MB, so you might need to forgo checking the option that allows including your list content in this backup.
Hi, I have a document library in sharepoint 2010 foundation.when i have uploaded a file into a document library from browser, it is showing a message"uploaded successfully" but it is not showing in document library all items.but when am open the site in IE and in library tab am clicking in file explorer button, in that file explorer the doc file is there.but in site -> doc library all items the file is not displaying. Am the administrator the site.
If your library has versioning with minor versions enabled, uploaded files will be drafts. It may be the sort of confusing case that even as administrator, you do not have the rights to see drafts.
In the Library Settings, open the Versioning settings menu. Try setting the Draft Item Security option to all with read or edit permissions. Ensure that you own the respective rights (personally or as a member of an appropriate group).
Changing this option solved the problem for me. However, I experienced this setting as being kind of weird: Setting the option back to its former state (in which I did not see the documents) did not make the documents disappear again.
I use VS2010 on Server 2008 R2 with Sharepoint 2010 Foundation.
I have created a custom master page following instructions from here: http://msdn.microsoft.com/en-us/library/gg447066.aspx (activating my custom page as feature), and was delighted with the results. But as soon as I changed the images and attempted to deploy them through VS2010, I noticed that my changes were not showing in the page (which was still showing the old images).
Useful observations:
It's a Sandboxed solution.
I checked that wsp is built with the new images, and so it was.
When I retract my solution, I also go to Master Page Gallery, and
delete my custom master page from there to make sure I start from
scratch. No difference.
My SP Designer does not give me an option to "revert to site
definition".
My "Look and Feel" section in central admin does not offer a
"reset to site definition" option.
Checking "CustomizedPageStatus" property of the SPFile for my master page shows that it's set to "none", and indeed, calling RevertContentStream throws an exception. This indicates it may not necessarily be the unghosting issue.
Does anybody know where my images get deployed to, and what the cause of this problem may be? The "Deployment Location" property does not lead to the correct location (in fact, I can't even see my Feature's folder). Could it be something to do with the way variables in the path - {SharePointRoot}\Template\Features{FeatureName}\StyleLibrary\Branding101\Images\ - are parsed?
I am new to Sharepoint, so all and any help would be much appreciated.
Since this is a Sandboxed solution, everything gets stored in the content database, accessible through SharePoint Designer 2010. In SP Designer, open the site you are working on, then look under "All Files" in Site Objects: that's where I found my masterpages, images, etc.
Deployment paths (displayed in module properties in VS2010) are just red herring, as no deployment to the file system itself takes place. Hope this helps somebody else!
So we couldn't open .pdf in the browser in our SP2010 site. I set the setting to permissive browser file handling in central admin. I then found out that there's a bug that if a site is created from a custom template the pdf files uploaded to that site will still prompt for either Save or Cancel. I ran a hotfix on the server
http://support.microsoft.com/kb/2459108
Consider the following scenario:
You set Browser File Handling to Permissive for a web application in the General settings page in SharePoint 2010 Central Administration.
You create a document library, and then upload an html document.
You open the html document in the browser.
Note You are not prompted to download the html document and it is rendered in the browser.
You select to include the content when you save the SharePoint site as a template.
You use the template to create a new SharePoint site in the same web application.
In this scenario, the Browser File Handling list setting for the document library in the new site is set to Strict. Additionally, when you open the html document, you are prompted to download the file.
Now when I click on a pdf with firefox I can open it directly but with internet explorer (8 and 9, default settings) I still can't do it, what's the solution here?
Edit: Maybe it always worked in firefox, anyway, when I create a new library it works as expected. How can I run this setting on all libraries?
There's a different, more subtle, but simpler root cause of this problem.
After much web searching and many hours with MSFT support, as hard as this may be to believe, it turns out that the root cause of my "SharePoint won't open PDF documents" problem was actually an Adobe extension/add-on. The symptom was an Adobe error msg "failed to open" after clicking the PDF list item in a document library. The culprit, an Adobe extension/add-on: "Adobe Acrobat SharePoint OpenDocuments Component".
I do not know how this got installed. What I do (finally) know is that this component actually does the exact opposite of what its name implies, i.e., it apparently prevents PDF documents from opening up when clicked in a SharePoint 2010 document library.
After various failed attempts to solve this problem (including changing "Browser File Handler" settings on the web app server from "Strict" to "Permissive" and other fixes suggested below and elsewhere on various blogs and web sites), nothing fixed the problem until we disabled this Adobe extension/add-on. Then, problem solved.
Note that you may not see this component in the "Tools > Manage Add-Ons" list until after attempting to open a PDF document from the library: apparently the add-on isn't activated (won't appear in that list) until an 'open' attempt is made. SO - if at first you don't see the component listed, try to open a PDF file and check the list again. If this component appears, disable it, and your problem is likely to go away.
Baffling, at best; or worse, actually nefarious on Adobe's part ...?
I'd still like to know how to get the PDF to open in a separate browser tab in IE vs. displacing the active tab. If anyone can help with that, please let me know! No custom coding solutions, PLEASE!
There is a better way to handle "Browser File Handle" issue. Take a look at my blog here: http://www.pdfsharepoint.com/sharepoint-2010-and-pdf-integration-series-part-1/
Solution #2 addresses Pdf extension without exposing entire Web Application to "Permissive" browsing. Setting "Browsing File Handle" to "permissive" opens too many vulnerabilities with other file extensions.
Thanks,
Dmitry
I have the same problem - originally installed Office Web apps, then turned that off, turned on the open in client application, then changed the setting on each doc library to open in browser .. Still have a problem with PDFs though.
If somebody includes a link to them in an announcement, then that person can open, other not. But only in IE - in FF there is no problme
Just change the Browser File Handling for the Web Application from the central admin as:
Central Administration > Application Management > Manage Web Applications
go to your Web Application example "http://sharepoint:80, just select it
from the top ribbon click "General Settings"
go down to "Browser File Handling" and change it to "Permissive"
If am not clear go to http://www.pdfsharepoint.com/sharepoint-2010-and-pdf-integration-series-part-1/
try this:
Make sure you're the site collection admin. Go into the site (not the central admin) and then go to site settings then go to site collection features. In there you will find the setting for " Open Documents in Client Applications by Default " it will probably be deactivated. Active it and you're good to go. users will then open attachments in their windows assigned applications, not the sharepoint web apps.
Also, try going into adobe reader and in the settings there is an option to open with the browser. check or uncheck it based on what you want it to do.
Encryption and SharePoint don't play well together
Right click My Documents or source folder
Select Properties > Advanced (button)
Uncheck "Encrypt contents to secure data"
This should solve many SharePoint problems you might have, including files not opening properly.
Appreciate this is an old post but still very relevant today. I spent a while trying to get this to work - just thought I'd share my findings.
This is specific to Adobe Acrobat. If you use a different PDF viewer, such as SumatraPDF the issue does not occur.
1. To prevent the 'Open, Save, Save As' dialog box in Internet Explorer:
This is specific to the versions of Acrobat. Set the following key/value:
Key: HKLM\SOFTWARE\Policies\Adobe\Acrobat Reader\*acrobat_version_number*\FeatureLockDown\cSharePoint
Value Name: bDisableSharePointFeatures
Value Type: REG_DWORD
Value: 0x1 (hex)
e.g.
For Acrobat X:
HKLM\SOFTWARE\Policies\Adobe\Acrobat Reader\11.0\FeatureLockDown\cSharePoint
2. To disable PDFs opening in the browser
This is specific to the versions of Acrobat. Set the following key/value:
Key: HKCU\Software\Adobe\Acrobat Reader\acrobat_version_number\Originals
Value Name: bBrowserIntegration
Value Type: REG_DWORD
Value: 0x0 (hex)
e.g.
For Acrobat X:
HKCU\Software\Adobe\Acrobat Reader\11.0\Originals
Thanks,
References:
Adobe Acrobat - Lockable Settings
Adobe Acrobat - General Application Settings
When I create a new link in quick launch bar in any site, the link is static and is always visible even when a user may not have privileges to view that document, or the document library it is in. When any document library has a link in the quick launch (via the document library's "Title, Description, and Navigation" setting), the quick launch link is subject to permissions and will not display in the quick launch if the user does not have permissions to see that document library.
Is there a way to achieve that same functionality to have my static URL to a document be subject to the same 'visible if user has permissions to view that document' action? Possibly some way to add a link on the SharePoint quick launch for a document much the same way I can add a quick launch link with a document library?
You should use audiences to achieve that. Audiences allow you to target groups of users with specific content. This feature is only available with Microsoft Office SharePoint 2007, it does not exist on Windows SharePoint Services.
You should stick to audiences if possible, but you could also solve the problem by:
creating a custom quick launch as a server side control
creating a JQuery script to check permissions and update quick launch (not recommended)