Hi,

Due to inactivity, I have closed this topic.

Please respond to the topic if you have further questions and/or would like to activate the discussion topic further.

Thank you!

Hi Hans,

thank you very much for your feedback and questions.

To answer them:

1) This is the SharePoint limitation to display library templates in the language chosen in installation process. I’ve created new OnePlaceMail library templates in http://dl.dropbox.com/u/58378674/ScinapticOnePlaceMailEmailLibrary%20nl-BE.stp" rel="nofollow">Dutch-Belgium and in

Hi Ilia,

First of all, thanks for your time and help. I'd like to post that the sandbox solution works as you described! That is the good news :-)

We do have a couple of concerns:

1) When using the sandbox soluion in a site collection that has been created in another language than English (our company language is Dutch), the OnePlaceMail Email library cannot be seen in the library list.

2) We have a clear preference for a farm solution as opposed to a sandbox solution for the following reasons:

-- Using the sandbox solution, we need to deploy and activate the feature every time we provision a new site collection. This is tedious compared to the farm solution, where we can configure our site defintions to activate the required features at the moment the site collections are provisioned.

-- In the farm solution, 4 separate features are provided, while everything is grouped into one feature in the sandbox solution. This is not so convenient in those situations where we would want to activate specific features and not others.

Do you expect to offer the new features in the farm solution as well? Or will you only be working with the sandbox solution in future? We hope not, but if this were the case, perhaps it would be a good idea to remove the farm solution from your server component installations files so as not to confuse customers?

Thanks for your feedback!

Hi Hans,

thank you for your update.

To answer your question, you were able to activate Farm Solution because it was previously installed from previous version (5.2 or older) of OnePlaceMail Server Components.

Currently it's only possible to unstall the solution using OnePlaceMail Server Components. When solution is completely uninstalled then the corresponding tabs will disappear from the OnePlaceMail Server Components.

It's better to use Sandbox solution as it has several improvements comparing to the provious versions of Farm Solution, including that fix we are talking about (solution is based on Content Type rather then List Type), https support, etc.

Hope this will help. Please update this topic with the results. Thank you.

Hello Ilia,

Thanks for your advice. In fact we are not using the OnePlaceMail SharePoint Sandbox Solution v3. Instead we are using the farm solution that is included in the package. Is there a specific reason we should be using the Sandbox solution rather than the farm solution? Is it best practise? How come the farm solution doesn't work?

We will test the Sandbox solution today and post our findings here.

Hans,

could you please also confirm you are using the OnePlaceMail SharePoint Sandbox Solution v3?

Thank you in advance.

Hi Hans,

thank you for your message.

Image, Audio and Video content types in the standard Asset Library are also based on the "Document" content type, so it's possible to use existing content types for this particular library to perform feature testing.

Please take a look at the following testing results:

1) I've uploaded and activated the OnePlaceMail Sandbox Solution:

https://d37wxxhohlp07s.cloudfront.net/s3_images/820152/12-11-19%20sandbox%20solution.png?1353294044

2) Created new asset library, uploaded chat.txt file (I've selected "Image" content type) and changed the library view to the "All Assets":

https://d37wxxhohlp07s.cloudfront.net/s3_images/820153/12-11-19%20feature.png?1353294229

Information regarding the content type for this feature is stored inside the "elements.xml" file in the OnePlaceMail-SharePoint-Solution-v3.wsp\OnePlaceMailSharePointSolution_Feature1\EmailAsAttachment\Elements.xml:

https://d37wxxhohlp07s.cloudfront.net/s3_images/820155/12-11-19%20elements.png?1353294879

Hope this will help. Please update this topic if you have any question, I'll be happy to help.

Ilia, thanks for your insights.

If I understand Ilia's answer correctly, the "Email as Attachment" feature should work on any List Type, as long as it has associated with it the Content Type "Document" or any other Content Type derived from "Document". Is that correct?

We performed the following test:

1) Downloaded OnePlaceMail 6.3 from following link: http://www.scinaptic.com/support/0006.html

2) Installed the server component on a clean SharePoint 2010 test system and activated the feature on our site collection

3) Added a standard document library. The feature appears as expected :-)

4) Added a library of type Asset and associated the Content Type "Document" to it. Then added a document to this library, selecting the "Document" Content Type for it. The feature doesn't work :-(

When we looked at the feature.xml file in de server component that we installed, we can't seem to find anything that indicates the feature would work as you described.

Are we overlooking something? Thanks for any help!

Hi Hans,

thank you for reporting the issue.

Custom features (like "Email as Attachment") contain two attributes which determine their availability depending on the List Type or Content Type.

As the "Content Type" is more generic SharePoint entity than the "List Type", the "Email as Attachment" feature is available for the most common parent content type ("Document" with ID 0x0101) and any content type which is based on it.

To solve this issue, please make sure your content type is based on the "Document" content type.

Hope this will help. Please update this topic if you have any questions. Thank you.