Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Jorge Ferrer
Liferay Journal renamed as Liferay Web Content
January 13, 2009 12:27 PM
Answer

Jorge Ferrer

LIFERAY STAFF

Rank: Liferay Legend

Posts: 2757

Join Date: August 31, 2006

Recent Posts

Hey translators!

I just wanted to let you know that in preparation to the 5.2 release we've renamed Liferay's internal CMS as Liferay Web Content. You can read more about the reasons for this change in Bryan Cheung's post: Liferay Journal is now liferay web content management

This change has affected many language keys and thus will need to be taken care of while preparing the improved translations for 5.2. To make it a little bit easier for you, here is a link to the changes that have been made in the Language.properties file:

http://svn.liferay.com/viewrep/portal/trunk/portal-impl/src/content/Language.properties?r1=24899&r2=24948

If you want to see all the changes check this two commits:

http://svn.liferay.com/changelog/portal?cs=24948
http://svn.liferay.com/changelog/portal?cs=24956
Jonas Yuan
RE: Liferay Journal renamed as Liferay Web Content
January 13, 2009 5:04 PM
Answer

Jonas Yuan

Rank: Liferay Master

Posts: 993

Join Date: April 26, 2007

Recent Posts

Hi Jorge,

Thank you,

It is really a good idea to rename Liferay Journal as Liferay Web Content.
As noticed that only the title of CMS portlets was renamed,

e.g., javax.portlet.title.56=Web Content Display

The portlet definition / specification was unchanged, e.g.,

<portlet>
<portlet-name>56</portlet-name>
<display-name>Journal Content</display-name>
<portlet-class>com.liferay.portlet.StrutsPortlet</portlet-class>
<init-param>
<name>view-action</name>
<value>/journal_content/view</value>
</init-param>
...

Any plan to update portlet definition or related info?

Best regards,

Jonas Yuan
Jorge Ferrer
RE: Liferay Journal renamed as Liferay Web Content
January 14, 2009 6:24 AM
Answer

Jorge Ferrer

LIFERAY STAFF

Rank: Liferay Legend

Posts: 2757

Join Date: August 31, 2006

Recent Posts

Hi Jonas,

For now we've only changed the frontend, but the backend remains unmodified. We are considering changing the names in the backend for a future release that it hasn't been yet decided. The main drawback would be that such a huge API change would for sure break backwards compatibility.