Tag Info

New answers tagged

0

You dont have an OOTB solution for this however there are various features that might make this process easier and more reliable: Establish good naming conventions ("the horse" is not a well-accepted name, one would naturally choose "horse") so that editors will naturally give the same name to the same subject. Make it easy for editors to find similar ...


1

No there is nothing like this ootb. You might be able to rig up something that takes input from when they create the page title and leverage search to pull back a list of possible matches, just like how the stack exchange sites work.


0

I think, there is no problem using your suggested approach. That can be useful when you are working on some static kind of stuffs. I usually prefer this kind of approach, when static content is there. Thing you need to remember is that in case you are upgrading your SharePoint with cumulative update, there might be a chance that that wiki page will get ...


2

The short of it is you can't with workflow, they operate after the item has been added or changed. You need to use an event receiver to do that if you want to perform some operations before the item is saved. You would want to look at the ItemUpdating event, since you want to do it as part of the edit operation.


1

This message will show when we edit the properties of a page no matter which library / wikis we upload it to, it seems to be by design. If you have any webpart on the page, once you click on it, it will give you control to perform maintenance on the webpart i.e. Close, Reset. Delete etc. To remove that i think you need to Customized the EditForm.aspx.


0

I change the script, I use CSS directly. It works well <style> #MSOZoneCell_WebPartWPQ2 .ms-alternating { background-color: green; } </style>



Top 50 recent answers are included