In my project , I have a wiki which has user guides for build contributors in my org. I have given right to contributors to edit it but at the same time I do not want them to edit without my knowledge (to avoid accidental edit) something like a review request. Apart from forcing this manually as a procedure what else can be done? Some wiki policy that I am unaware about? Some tricks?
Is it achievable?
What you want to do is at odds with Wiki's Open and Trust Principles. However, you could achieve it with Azure DevOps Wiki by visiting each page you want to watch and "Following" the page. You would then receive notification of edits and could review them (View Revisions) and make any changes you deemed necessary.
For what it's worth, I find these open feature requests:
Follow Entire Wiki
Follow a tree in a wiki page
Related
I am making edits to a client's Sharepoint site.
I checked out the page, made all the changes required, checked it back in, and am waiting on their go-ahead to publish.
I want to double-check that certain elements are the same as they were before I started editing. Generally I would go to site contents > pages > version history of the page I am working on, and look at the currently published version (because, as an editor, it seems to only show me the unpublished draft when I am on the page URL).
Tried to do that today and am getting an error: Sorry, something went wrong
Exception from HRESULT: 0x80131904.... Insightful and intuitive Microsoft error - well done guys (NOT).
Is there any other way that is more straightforward to just view what is currently published?
The quickest way to do this is to either log on as a test account that has only got read only permissions, or to ask one of your colleagues that doesn't have edit permissions to browse to the page and you can see what they see.
Version history, while is helpful when you need to roll back, won't show changes to web parts or other hidden elements when viewing it, so it's not always that helpful when using it for a case like yours.
As a side note, to log in as another user in SP2013, append this to your URL: http://yoursite/_layouts/15/closeconnection.aspx?loginasanotheruser=true
For a project I want to show/export all visitors with visitortags from an engagement plan. The export is for creating an overview and checking purposes. It's important to show the business I have done my work correctly. I prefer a way without writing any programcode.
Does anyone know how to do this?
Thanks a lot.
Jordy
This is not possible by default in Sitecore, so you will have to write some code.
If you click the supervisor you will be able to see the USERS in a state in an engagement plan, but not VISITORS. Even though you can see the users, you won't be able to see the visitor tags, for that given user.
We have chosen Alfresco for our project because Alfresco meets most of the functional requirements we need.
Share is a great app, nevertheless it has too much functionality for our scenario, much more than we need in our project. This is the reason of posting this question, we don't know what's the best option: either customize Share creating custom pages, custom dashboard, custom actions and metadata etc. or create a new web application that interacts with the repository.
Roughly, we have these requirements:
Custom header with custom menu, disabling direct access to Repository (users only can collaborate using Sites)
Custom dashboard that contains
On the left, list of Sites
On the center, custom dashlets which shows several content in different ways and formats
One of the dashlet would be a "dynamic" dashlet as I explain in my last question
Custom document details page, with custom actions and custom metadata
I would like to know opinions based on experience, explaining when and why would be a good idea to create a new web app that interacts with the Alfresco repository or when to customize Share according to your needs. I'm highly interested on knowing Share customization limits.
Thanks.
Alfresco Share doesn't really have any limitations, it's already an UI built upon the repository.
I've seen Share modification till the sky and one can't even see it's Share any more.
The things you've described above are just templating and building the rightfully freemarker templates/js to view the piece of information.
If you take a good look at the default templates with their regions and shift around the default regions you'll see that you don't need heavy customizations to achieve a different layout.
The only thing one probably lacks is experience with Share.
I need embeddable commenting system for web site where I can control posts. I want to delete posts I don't want to see and think that you can't do that if you use FB embeddable comments.
There is DISQUS, FB comments and many more solutions. What do you think is best? For me controlling comments, deletion of unwanted ones and banning users is priority n1.
Ideal solutions would be comment management that allows my users to login via numerous systems, like stackoverlow, and allow me to manage them, like stackoverflow does, but embeddable!
Opt out but possibility for posting to parent service is likeable feature
Looking for best solution! thx
I'd probably go with DISQUS, or if 'social' features aren't that important I'd choose IntenseDebate.
DISQUS has all the features you mentioned above (minus posting comments to another service, but 'likes' can be propagated to Facebook and Twitter).
IntenseDebate has probably better spam detection (it's managed by the same guys which run WordPress.com) but it lacks some features - you can login only with IntenseDebate account, WP.com account or by typing in OpenID URL (most of Facebook users probably don't realize they have one without so it's more or less useless without a 'Login with Facebook button'), but it has better customization features than DISQUS (easily modifiable CSS) and some sort of plugins you can install (haven't seen lot of those).
Also, there's Echo - it has all the features you need, but it's not free - price ranges from $10 to $100 per month.
I'm looking to throw up a web site that supports user submitted entries and allows voting and comments. Similar in form and function to FMyLife.
Basic requirements of site:
Users can submit text entries - generally 1 liners
Enters can be up or down voted
Comments allowed - presentation collapseable
Would like the fastest path possible. Ideal solution is configurable vs requirement for programming.
Have you had a look at Drupal? You can get a site up and running pretty quickly, it's very configurable, and it'll allow you to add to the site you're proposing if it grows...