When we open a PDF in the browser from a document library, and then press the back button we get page expired.
One possible solution we have found is to open the PDF in adobe reader, as per this post.
Is their a way to solve this that does not involve changes to the registry on the client.
When you open the PDF inline in browser you get a "page expired" when you go back?
Where do you open the document from? Is it from inside a document library or from custom code?
I am asking this because getting a "page expired" is connected to doing a POST request (postback) and accessing from a document library is a GET request.
Caching can also be an issue, but again only in combination with a POST. You can examine what output cache profile you are using (an easy way to do this is by checking the Cache-Control header in the response header of the page using a program like Fiddler
Scenario: We have an internal application that ties Excel spreadsheets stored in a SharePoint doc lib with specific Opportunities in CRM. The user clicks on a button in the Opportunity and a Web... if they just created the document (i.e., they clicked the button, the folder didn't exist, and so it creates the folder and copies the new Excel file into it). Sometimes they were working on it earlier... that user opening it may get it returned to them as read-only, often other users, even multiple other users, can click the button and the spreadsheet will open for them in edit mode! Questions: What
One of the functionalities advertised for Office 2010 was that "People can access document templates stored in SharePoint 2010 via the New Document Wizard in Microsoft Office applications" (see page... 2010 -> Backstory -> Options -> Advanced -> File Locations...) - I can't store URL or UNC paths - or even a mapped network drive to the SharePoint document library. Trusted Locations (Word 2010...? Anyhow, it seems that the functionality to have a master document library of corporate templates is not (yet?) available in Office 2010 with SharePoint 2010.
I'm trying to create folders in a set of custom lists I've created. However, when I try to do this, the New Folder button in the Ribbon is disabled. I read up on the matter; and this lead me to look to enable folder creation in List Settings -> Advance Settings. However, there doesn't seem to be an option to enable folder creation on the page. It shouldn't be a permission related issue; as I created the lists; and I'm also an admin on the farm. I could use a document library; but we will not be uploading documents to the list; so this is more then I need. What are my options, or what am I
So I recently had a nice hitch in the SharePoint app I made for my client. We have a Document Library which is supposed to contain PDFs, converted from drawing files made in other programs. The test... of things, but naturally I failed to take into account user-based errors. The testers uploaded a file in its normal file format instead of converting it to PDF first. And it's already passed through... situation. Because this is a real field test, I cannot simply upload the new PDF file and run it through the process, I need to maintain the field data from the original file, in all of its versions
It's weird but it's true. If I click the new button on a document library it takes me to the 'Upload Document' page and not the 'Create Page' page, which is strange as it used to work correctly. Has anyone experienced this behaviour themselves?
It appears that there's at least one folder in one of our crawled network shares that's not getting indexed properly, as evidenced by searching for unique words known to be in PDF documents in that folder and not getting the documents back in the search results. Documents in this folder are showing up in the crawl log as being successfully crawled, either with a "Crawled" or "Not modified" status. There are no errors or warnings in the Windows event log, and none that I can find in the SharePoint trace logs. Of the 42 PDF files in this folder, all are less than 5MB in size and most
We are storing quite a lot of pdf documents (images with no dual layer text) and do not wish to add a pdf iFilter (with the resultant storage and search performance costs). As we do not have an iFilter, SharePoint crawls the documents as list items (bringing back the metadata only) and displays the result link as a link to the DispForm.aspx instead of to the actual document. How do I get Search to return the results witha link to the document itself instead of DispForm.aspx? I want something easier than a custom PDF iFilter that ignores the document content or hacking the search result
I've changed the master page on a publish site collection. When I browsed back to the start site to check the new master page the browser just returned a 404 error, telling me that the page could not be found. But when I open the site collection with the SharePoint Designer very thing seems to be ok and in its place. All pages are as expected in the page library. Within the Designer I could even open the pages for editing. So does anyone has an idea why the browser cannot find and open the pages? UPDTAE To clarify my problem I should say, that also switching back to the default master
We are using WSS 3.0. We have a webpart that shows a list of documents in a document library. If we click on a MS Word file with a doc extension, it opens in MS Word. However, if we click on a text file with a txt extension, it opens in view mode in the browser. Is there any way that we can get the txt file to open in notepad?