How can I limit feature visibility in SharePoint 2010? - deployment

I have a SharePoint 2010 (farm) solution that contains exactly feature:
The feature is site-scoped.
The feature's visibility is set to "true".
The assembly deployment target is set to "Web Application".
The feature contains one webpart.
After adding this solution to the solution store I can deploy the solution to a specific web application. However, after deploying the solution to exactly ONE web app, the feature is actually visible on ALL site collections! I would assume that the feature should only be visible in site collections hosted by that ONE web app?. Trying to activate the feature and add the webpart to a page will (expectedly) fail in all site collections of other web apps (the assemlby cannot be loaded).
Is that a SP2010 bug? Is there a workaround? I just want to limit the visibility of a feature to specific site collections...
Please help!
Thanks

Jan,
Are all your web apps running on the same WFE server? If you have multiple WFEs, you can do this:
Deploy feature to web app A in WFE A.
You should see the feature in the Site Collection Features of web app A.
Now, go to a web app B in WFE B. When you look at the Site Collection Features in web app B, your feature shouldn't be there.
If your web apps are running on the same server, then they are using the same 14-Hive/TEMPLATES/FEATURES folder. Once you deploy the feature to just one web app on that server, the features-folder is sitting in that server's TEMPLATES/FEATURES folder, which will make the feature visible on the Site Collection Features of all apps in that server.
If you have multiple apps running on the same WFE and if it still your requirement to limit the visiblity of the feature, you may have to look into sandboxed solutions.
Another possiblity is you make the feature hidden (visiblity off--it will never be shown on any Site Collection Features) and just have the SP administrators do command-line/cmdlet deployment of your feature for that one web application.
-Gabe

Related

"Blank tabs" on Teams App update deployment (Teams Toolkit)

My Teams app:
multi-tenant
deployed using Teams Toolkit to Azure Storage, CDN enabled with a Custom Domain
in alpha use by internationally distributed organisation (third party, not me), users around the world
the app functionality works fine including multi-tenant
in rapid development so frequent code updates. Very rare manifest updates.
Problem:
I frequently update the app's code and deploy the update to Azure using Teams Toolkit
when I do this users often report 'blank tabs' for a period of time, can be many hours. They see the tab menu but the tab contents are simply blank. Purging the CDN doesn't seem to help.
seems most common using Teams desktop app but also reported using browser and mobile Teams app
I think this may be an issue of code deployment .js files (each of which gets a new filename) not being available to the install, I can sometimes reproduce but very unreliably. Other times I can access the app, using a user account on the client's AAD, successfully from different locations (using a VPN to emulate location).
Previously the app's Custom Domain was managed on Cloudflare's proxy.
I disabled this and implemented Azure CDN.
Users continue to report the problem.
This is very poor user experience.
Does anyone have experience of this or hypotheses on what may be happening?
Thanks.
Would suggest to test one thing first: manually deploy a new code change to Azure storage, with the same storage-CDN-custom domain setup.
See if this also causes the hours delay symptom.
By doing this, if the issue is reproducible, it may indicate that the Azure Storage-CDN configuration needs to be optimized.
Otherwise please share the result and it will help narrow down the root causes.

Distributed CMS or content management platform?

I have been trying to find an open source or affordable platform / CMS that is distributed.
And by distributed I mean that there is a single control panel with all the content, but you can have multiple websites on multiple web hosts that query an API that holds this content. Not the usual "one install, multiple websites" as you can do with Wordpress MU.
Ideally there would be an API that the website can connect to and get the data, or use push technology from the control panel once new content is added.
If there is no client side platform built but there is a sophisticated content management platform with an API that allows me to build my own client/website connecting to it, that would be fine too.
Does anyone have tips if there is such a thing?
Govento CMS is a distributed CMS, that allow you, to manage all projects with a single installation and present your content via push publishing dynamic and current on different remote delivery-platforms.
german: http://goventocms.com
or english:
http://translate.google.de/translate?hl=en&sl=de&u=http://govento.de/&prev=search

Web app roll out

I've been developing web apps some years now, actually as a hobby. When I write something, unsing Laravel, Sails.js, or Meteor and I add a feature, I upload it and it's there, for everyone.
However, I've always been wondering how bigger sites like facebook manage to roll out features to just some users. Do they push their changes to just some servers? But in that case - how do they manage the make the selected users access just these servers?
Or some db entry to see if the user has access to the feature/ version?
So how does it work?
Really interested in this :)
Large sites like Facebook use a technique called Feature toggles to control the functionality that is active at run-time. The following blog article describes Facebook's approach:
https://abhishek-tiwari.com/post/decoupling-deployment-and-release-feature-toggles

CMS with built-in A/B testing

I would like to start trying new layouts and visuals on web pages that I manage. So far I am managing all my pages via scripts on my local machine and just upload static html files to a hosting machine; I am happy to set up almost any basic CMS or "static site manager".
What are some CMS (or a more basic platform for managing static html pages) that has built-in support for keeping track of multiple versions of a page and recording a user's flow from age to page?
Wordpress does thas job very well. Also you can use "Google Content Experiments" (aka "Google Analytics Experiments") for FREE, and just add a link to two different versions of your page. For A/B testing google experiments is a PERFECT tool.
How to set-up an A/B experiment read here:
https://support.google.com/analytics/answer/1745216

Help to choose Alfresco or Nuxeo for DMS

I have requirement to develop DMS(Document Managemen System) with some initial requirements:
If possible DMS should be open source
Initially DMS should support up to 500 users
System should be scalable in sence od users or content
Docuemtns/Content should be stored on a file system
Document should be able to be marked for later destruction
Mandatory to have workflow capabilities
Mandatory to have version control capability
Nice to have SSO(Single Sign On) with Liferay portal
Nice to have posibility to expose some of funccionality via portlets in Liferay
Document management should be done via the web interface
Nice to have shared drive capability
Nice to have events and notifications about add/change content
At the moment I am in doubth to choose between Alfresco and Nuxeo.
I will appreciate any help to choose between them.
Thanks in advance
I have not much experience with Nuxeo, but here is for Alfresco:
1.If possible DMS should be open source
Yes.
2.Initially DMS should support up to 500 users
Yes, if you have a good server.
3.System should be scalable in sence od users or content
Yes.
4.Docuemtns/Content should be stored on a file system
Yes. Only metadata is stored in a database.
5.Document should be able to be marked for later destruction
The free Records Management module has retention capabilities.
6.Mandatory to have workflow capabilities
Yes.
7.Mandatory to have version control capability
Yes.
8.Nice to have SSO(Single Sign On) with Liferay portal
Yes.
9.Nice to have posibility to expose some of funccionality via portlets in Liferay
Alfresco and Liferay work very well together.
10.Document management should be done via the web interface
Yes.
11.Nice to have shared drive capability
Yes.
12.Nice to have events and notifications about add/change content
Not sure about this one. The Share module has this feature, but not sure about the main DM application.
Don't know the Nuxeo system, but we are using Alfresco as a document storage and session server. We have our own GUI and only use it as a back-end system. So far we had no problems. Plus Alfresco has a nice REST interface which makes it easy to integrate into any existing system.