I have a sharepoint 2013 website with a list of items,
i want that on an item page (displayForm.aspx) the webiste users will be able to add comments (wordpress like) to the item, how can i do that?
I think discussion board list may meet your requirements without doing any custom development.
Please see the article at url
http://www.learningsharepoint.com/2012/12/19/create-discussion-board-in-sharepoint-2013-complete-tutorial/
If you are interested in creating custom UI you may also consider creating custom action which may link to a separate comments page where you would pass id of the item.
Please see below url for more details on how to create custom actions.
https://msdn.microsoft.com/en-us/library/ms473643(v=office.12).aspx
Another option is create your own page layout based on a custom content type the page layout may contain a custom web part which would store comments on custom list or custom database based on your requirements.
Please let me know if you need more help or knowledge on any of the above options?
Regards,
Hiren Gondhiya
Related
Does anyone know if it is possible to share data between sites on a Kentico platform, such as news articles? I have tried searching but could not find an answer.
Thank you,
Yes. If you want the content to be the same and keep the URLs and Domains separate, then this is best accomplished with linked documents between the sites. This way if they are updated on either site, they will remain in sync on the other site. Read more here: https://docs.kentico.com/k9/managing-website-content/working-with-pages/copying-and-moving-pages-creating-linked-pages
https://docs.kentico.com/k9/e-commerce-features/managing-your-store/products/linking-existing-products-or-sections
Basically what you'd want to do in your content tree, is click "new page" and then select "Link an existing page" from the bottom of the next menu. After that, you will see a content tree to select a page from. Use the site selector in the top left to choose a different site, and then select the page you'd like to link in.
Note: Keep in mind that the page type will need to be allowed in that section of the tree (for example, if you are trying to nest a news article under a folder but folders are not an allowed parent type, you will get an error).
If you'd like to pull data from another site in via repeater and leave the content on the other site, then you can user a repeater or similar viewer control, and specify a site within the properties in order to pull the pages from the other site.
Each of these methods assumes the Kentico sites are on the same instance of Kentico with a shared database.
If you have multiple sites in one Kentico instance, in your repeater getting the news articles, specify the site you want to get the news articles from and it will be displayed on that site. If you want to combine them then create a custom query and use the query repeater to show the news articles.
I find that Liferay concepts are quite confusing.
When I add new items, I don't know what is the best to choose:
Use the web content concept with template and structure
Use the dynamic list records
Use a specific model (using service builder).
All of these are really similars and can achieve same goals.
Have you got any clue or advice on what concept to choose when you develop some new features in Liferay?
You should use the components in this way :
Web Content : Web contents provide convenient way to create, update, view, modify, create RSS feeds, customize the content of the web site. It is one of the main component of the Liferay CMS. You should use web content when,
You have static content and want to show to the site.
You have specific structure of the content (like content with an inline image and a document link), then please use web content with the structure and template
You want to use ready to use content portlets ( web content list, web content display, web content search) instead of creating new set of portlets for your own type.
After all this, Liferay provides customization of web contents by allowing user to add new content type, creating rss feeds, structures, templates, ready workflow, content type roles etc.
Dynamic List : Consider dynamic list as a database with display functionality. Here, you can create a custom type of data and provide display functionality. If you have any requirement like user can create his/her own type of list maintain them, then go for it.
Custom Portlet : If your requirement is very case/scenario specific that you cannot achieve using list or web content or any other Liferay portlets (blogs, wiki, knowledge based articles etc) then go for custom portlet, here please remember, that at every liferay upgrade, you need to review the portlet and update the code accordingly in case of any API change or something. For OOB portlets, Liferay takes care of it.
Hope this helps!
It deends on what you want to have and how much control you want to have over your code.
To make simplistic application use web content concept with template
and structure.(need not to know technologies)
-To make some complex applications use dynamic list records
To make extremely complex applications and have full control over the flow use liferay service builder.(need t be a expert java programmer)
Hope that helps :)
I have a SharePoint portal which displays daily news in a visual webpart. This webpart is linked to a list. I would like to provide users the possibility to suscribe to this list (mail or RSS) so that they can receive the content of the news without having to go on the website. I have never used this SP functionnality, therefore I would like to have your opinion about the best way to handle it ?
I have thought of creating a "subscribers" list. A button "suscribe" on the aspx would add the current user to this list, which would be taken as a source for the RSS feed/mailing list.
Another possibity would be to redirect the user to the RSS suscribing page of sharepoint "view RSS feeds", or the mailing list "Alert me", but maybe would it be less ergonomic... I don't know.
Don't hesitate to give me your point of view, thank you very much !
Unless you have some special requirements you didn't mention, there's no need to create a custom solution - just add two links to your Web Part:
link to an RSS feed of the list,
link to a page allowing to create alerts for the list.
I have a website in Sharepoint 2007 (it is a publishing portal).
I want to create a site with more specific info than what it comes with Sharepoint.
You know, when you create a new site, the only info you can enter is title and URL.
I would need an image and a description.
The solution is not a custom list, because i need to have pages inside and other lists.
How can i extend this site list?
Write an application page or web part that creates the new site. Programmatically update it with what users enter in your custom form.
Creating the site
The SPWebCollection.Add() method creates the site from a site definition. Create a custom definition that includes the site columns, content types and lists required. These will then be created as part of the site.
Further customisations
This won't perform all customisations however - for the rest develop a feature receiver. On activation it will run any arbitrary code on your new site.
For example as you are using a publishing site, retrieve its default page with the DefaultPage property. This is an SPFile object which has an Item property that can be edited like any other SPListItem. Update the image field and description field for the item based on its content type. The page will then render these properties.
All of the above can be wrapped in an SPLongOperation for a nicer user experience.
There are other options as well, for example the SPWebProvisioningProvider. The two separate steps above of creating a site definition and activating a feature receiver could be tied into one with this.
There is more information on the above techniques (plus others) and their pros and cons in part 3 and part 4 of this series by Raymond Mitchell.
I'm very new to SharePoint, so apologies if this sounds a little basic.
I want to create a List in SharePoint that is just purely URL links, but then make it available to every site collection that we will create.
Once this list is created, I need it to display in a webpart (like that standard 'links' webpart). I guess I will need to create a Feature, so that it can be activated at Site Collection level.
Any ideas how this can be achieved please?
Thank you all kindly in advance, Ash ;-)
I did something similar - but I created it as a Web Part with it's own security trimming. I covered some of the basics here:
http://www.codersbarn.com/?tag=/webpart
What you would need is a view on your list of links (that view will display the content of your list). Have a look here for more details on List View Web Parts. Once you figure out how to create it and what you want in your view, coding it shouldn't be too hard (You can either use SharePoint Designer on your site to create the view you want and then reverse engineer it into code using SPSource or you can create it from the schema.xml of you list).
You should note however, that with WSS you will not be able to view the content of a list on another site collection (i.e. you can only views of your list on the site collection where the list was created). Cross-site list views are a lot more complex to implement (you can buy components that do it though). I'm not sure how MOSS deals with cross-site list views but if you use MOSS, you should make sure that you can do it before you start developing your view.
EDIT : I would definitely go with what IrishChieftain suggested if your list isn't too complicated and has a structure that won't change much. Dealing with cross-site list views is a pain.