I am new to Liferay, how to add specific web content to only single page.for example i have 2 pages like Financial Service and Products.I have related web contents for those two pages.If i add those web contents to pages,both the contents are displaying in both of the pages.
Add a page on your portal
http://www.liferay.com/documentation/liferay-portal/6.0/administration/-/ai/page-creation-and-manageme-2
Then you can add two web-content portlets pointing to those 2 pages.
Related
There are two SharePoint sites, each based on its own SharePoint installation.
Both are in the same domain.
The first site is for a document flow.
The second site is for a knowledge base.
I need to put a set of web parts (search, search results, indexed document library) from the second site in the master page of the first site.
The services and data will stay on the second site but they would be available in the first site.
I tried to apply the Page Viewer Web Part but it’s impossible to avoid using the second site’s master page layout.
Question
What other ways exist to solve this task?
You can index content of first SharePoint farm with search service application in another SharePoint farm.
You should configure search service application and add new website content source in search service application setting.
In this scenario you dose not need to move any thing and SharePoint crawl your content periodically.
I am new to Liferay portal. Is there any possibility within Liferay portal to extract portlet as different web application?
Plugin portlets are typically deployed as a separate web application. If you're asking about Liferay's core portlets: No, they are contained in Liferay. All of the plugins are downloaded separately and installed as a different web application
If you want share your portlet, Liferay has some features.
Drag and drop your portlet in page and then click on configuration icon.
In the popup select Sharing tab
You can choose your preferred sharing mode (embedded javascript, facebook,.).
When you share a portlet, be careful about permission settings otherwise users will not be able to view it.
Another chance is to use porltet url, see FriendlyUrlMapper wiki
This is an example for portlet HelloWorld in /web/guest/home page
http://localhost:8080/web/guest/home?p_p_id=helloWorld_WAR_HelloWorld&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&p_p_col_id=column-1&p_p_col_count=1
Reading this question regarding using portal engine vs. aspx, there is also the option for a "Mixed" template which the training defines as:
This page template is based on an ASPX page located in the path specified in the File name field. ASPX+ Portal page templates are based on an ASPX page with additional page components that enable the Design tab.
What isn't clear is what the use case is for this mixed template. When would you use this versus the other two?
Update
I read the following in the Developer Training materials:
Sometimes, you may need to combine ASPX page templates or external ASPX pages with
Portal Engine page templates on a single web site. When developing or maintaining a
web site built on ASPX page templates, you must manually modify the code of a page
every time you want to change its design. But you can add flexibility to ASPX templates
by defining areas that can be edited directly through the browser using the CMS
administration interface (similar to the Portal Engine development model).
This explains clearly that it is a true hybrid where you have both ASPX template and Portal Engine functionality, but it isn't clear what benefit you have by using this approach versus a Portal Engine template that utilizes widgets or web parts.
I'd say there is no "benefit" as such. You can use this mode e.g. when you are migrating existing ASPX web site to Kentico portal engine pages and replacing components (such as controls and web parts) one by one. When you finish the migration you can switch to portal engine mode. The goal was to provide this functionality for those who need it. It is recommended to use portal engine as you have complete control over the pages from CMS Desk.
The most common place I use them is when adding templates to a site using ASPX page templates, usually sites tend to have a content page, where I can swap out the controls (usually editable regions) with web part zones, then use that one template file to create multiple ASPX + Portal templates.
That way I can add a lot of new functionality into an existing site, without having to create half a dozen new .aspx templates.
I imagine it's also still useful for a new project where you want to keep your templates under source control, while utilizing the portal engine/web part functionality of Kentico.
I am a .net developer and want to learn SharePoint. Usualy we use MasterPages to have a constant layout for all or some of the pages. My confusion here is SharePoint uses Site Template and MasterPages which both sounds to do same thing. am I right?
thanks
MasterPages and Site templates are absolutelly different thing. Master page is usually layout of some pages. It's same like in ASP.NET.
In Sharepoint you can create some sites in site collection. These sites are created according to site template. When you creating (for example) team site, it's created according to team site template, which is stored in Sharepoint folder on file system. In site templates you can specify which features should be activated when site is created, which features should be activated on site collection scope etc. Also you can specify list, which should be created, modules... And also you can specify default master page which will be used on site.
You can find more informations on msdn
I am creating a site template in Sharepoint. I also have some custom .aspx page, that I want to deploy in Layouts\myDirectory. Using my site template I will create a Web (SPWeb) that should use the custom pages and reference them by an url of the form http://site/MyWeb/MyCustomPage.aspx. How do I integrate the pages in my custom template?
Pages stored in the Layouts folder are Application Pages and should always only be referenced through the _layouts virtual directory
If you want to reference the page as http://site/MyWeb/MyCustomPage.aspx then it should be a Site Page
A site page can be put inside a feature or directly inside a Site Definition (even thought I recommend that you only use the Site Definition to activate features). The way you provision the page is throught the Module & File elements see MSDN
A site template can only contain the contents of a single site/web. So you can't deploy files to the layouts folder using this technique.
However you can use site templates in combination with a solution package that copies your files. There is an example here. Deployment of the solution package will deploy your custom .aspx pages once. From then on they will be accessible to sites created by your site template.