SharePoint Form Library files cannot be edited in IE - sharepoint

Could anyone advise what settings need to be checked?
My form library on SharePoint 2013 can create new files in the published form.
But when click on a file, it opens as plain xml in IE; also can be edited in InfoPath if it is installed. But cannot be edited in IE.
Checked: Use the server default (Open in the browser)
There are other form libraries work fine on the same server.

It turned out that the subsite template is wrong (but it cannot be changed). Created a new subsite of Document Center, then it works.

Related

File not displaying in sharepoint 2010 library all items

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.

Creating an item in a SharePoint Form Library from a SharePoint Designer Workflow

I'm using MOSS (SharePoint 2007) and InfoPath 2007.
I have a Form Library with an attached InfoPath form, and would like to create new items (forms) in this library during a workflow built in SharePoint designer.
I've tried using the "Create List Item" action, but it doesn't assign the correct metadata (the new item looks fine in a view of the list, but can't be used to render the form (the generic "form has been closed" error comes up if you try to view the item)).
I'm not adverse to writing my own custom WFA to do this in .NET if need be, although it'd be nice to find a simpler solution.
Can anyone provide any resources for how to achieve this in SPD, or programmatically? My searches on the topic so far have been unfruitful...
Found the solution to this, thanks to a video on YouTube: http://www.youtube.com/v/bcnC_XwCcAg&hl=en&fs=1&rel=0
For anyone else out there who (like me) might not be able to watch YouTube content where they need this information, here's the process:
Create IP form
Publish to SP Server (as doc lib)
On document library, change settings:
allow management of content types
display in browser
"Fill out" a blank version of the form and save it to the doc lib with name "template"
Open context menu for "template" form and select Download a Copy
Delete "template" form from document library
Open library in windows explorer
Open Forms dir
Paste downloaded copy of "template" form into the Forms dir (as template.xml)
Go back into doc lib settings
turn off management of content types
change template url to template.xml
press OK to save changes
Go back into advanced settings ago, and turn management of content types back on
In SPD, make a WF which uses Create List Item to put an item in that library
And that's it. Just 12 steps needed to publish an InfoPath form so that it behaves as you'd expect, and any SharePoint developer should be familiar with 12-step programs.

Title Bar with a picture in Sharepoint

We have the standard Sharepoint site for our group at work and was wondering if we could add into the title bar where our group name is (like to the right of it), or above the announcements/calender widgets a
picture that resembles our group
and a mission statement right next to it
Does anyone know if this is possible? Thanks.
If you have the appropriate permissions, you can edit the page (More likely the master page) for the site using SharePoint Designer which is free from Microsoft. If you upload the image you want to a document library you can use that url for the img src.
SharePoint Designer 2010
SharePoint Designer 2007
But a simpler solution would be to edit the page, add a new web part and choose the Content Editor Web Part where you can put your mission statement and an image (that you previously uploaded to a document library).
You don't specify which version of SharePoint you are using, but changing the logo of a site hasn't changed much since the 2003 version. Office.Microsoft.com shows the user perspective of changing a logo. You could change the same setting through the API.

Can't open PDF files in SharePoint 2010 with Internet Explorer

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

Force InfoPath form to open in Browser

I created an InfoPath form that uses VB code to push fields into a custom list I created on a SharePoint 2007 site. This part works.
I "published" the form into a form library.
I changed the settings on that form library to open items in the browser and allow editing of content types.
In InfoPath under Form Settings I chose the compatibility setting to allow this form to be opened in a browser, I linked to my Forms service online, and ran the design checker. No errors.
When I try to open it in the browser using the "Edit in Browser" setting I get this error message:
This form template is not currently
browser-enabled. It must either be
republished as a browser-enabled form,
or opened using Microsoft Office
InfoPath 2007.
No matter what I do, the form will not open in the browser. This is all I want. Did I miss something??
You need to upload your form thru Central Administration because you use code in your form. See this MSDN acticle.

Resources