I want to translate the name of page present in liferay. The first page name is welcome provided by liferay. How we can translate this name to a specific language.
Thanks
asif aftab
6.1 or 6.2 ?
as for 6.2 you can localize friendly urls: see this blog entry
for 6.1 it is not possible out of the box, ( see this there is a proof of concept provided, maybe you can find a workarround.
Or you can create multiple pages and for each one create a friendly url in the requiered language( i don't think this is a good way :))
Well, you CAN translate the name of your pages even in version 6.1 (though translation of friendlyURLs is not supported before 6.2 version). Here is how you can do it: http://javarushi.blogspot.com.au/2014/01/localize-names-titles-of-liferay-pages.html.
I have used this feature myself. It works w/o any issues.
Related
First: i am kind of a beginner in web administration. Please be patient ;)
I got a cloned VM from a server with a typo3 website on. i want to make it a test server to test updates and stuff before trying it on the real site.
I want the typo3 website to use staging.mywebsite.com instead of its normal url, but i am not sure where i need to change stuff in order for typo3 to work correctly.
what i did so far:
renamed the folder under /var/www/old.mywebsite.com to staging.mywebsite.com
change entries in /etc/hosts
But i am quite sure i need to change some config files too. Typo3 Version is 9.5
I found this:
TYPO3 How to change the name of a TYPO3 website
But i think thats not what i need?
Thank you in advance.
The URL for the website is defined in the site configuration, see here.
You should modify the entry point as shown in the second image of the documentation (2) or just use the slash "/".
In your example you should use "https://staging.mywebsite.com/". Please keep in mind not forget the slash "/" after the domain.
I use the TYPO3 extension t3events. The docs are not up to date with the current version of Typo3.
I know I have to add some code of routeEnhancers in sites config.yaml. But don't know what and how.
How can I realize readable URLs for t3events within TYPO3 version 9 LTS and above?
You are right with the routeEnhancers in site config.
If you need help implementing https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/9.5/Feature-86365-RoutingEnhancersAndAspects.html it might be easiest if you write down the different type of URLs you get.
I don't know t3events but I am sure somebody can help then.
I'm using Joomla EasyDiscuss component for running a discussion community. And that is for Bengali. Unfortunately the component isn't supported for UNICODE alias, as I invested already, at this moment it's not possible to move to another one. And their support told me that they will release a fix with their next release. So now can anyone help me by suggesting a temporary fix?
Thanks in advanced.
I presume you mean the EasyDiscuss extension by StackIdeas, which runs on top of the Joomla content management system. (i.e. it's not really correct to say the "Joomla EasyDiscuss" component; the Joomla folks didn't make EasyDiscuss.)
StackIdeas announced version 2.0 of EasyDiscuss on January 9, 2012, after you posted your question. I don't see anything on their site which says that version 2.0 supports the full complement of Unicode characters, or languages beyond Western European, or international use, or anything like that.
However, I was able to get on their demo site and create a category Testing Only テスト, which includes the Japanese characters テスト ("test") in both the title and alias. Check the link, which was copied from the demo site: the URL includes the string %E3%83%86%E3%82%B9%E3%83%88. (N.B. The demo site might get cleared periodically, so by the time you follow the link, this text might be gone.)
But it sure looks like EasyDiscuss 2.0 has some degree of support for non-Latin text in aliases.
There is a comment thread on the 2.0 announcement page. I've put a pointer to this question there. Maybe the StackIdeas folks will come here and give a definitive answer.
Update: the EasyDiscuss 2.0 announcement page now has this reply, which I think is official: "The latest version 2.0 already comes with unicode support and I think you have tested it yourself in our Demo page. All you need to do is activate it in the EasyDiscuss backend: Settings -> General -> SEO and click YES to allow unicode aliases. :D Thanks for the input! We will add this feature in the what's new page."
Have you tried downloading the latest version from the site? This issue should be fixed in their latest version as it supports unicode aliases.
I am new to joomla and wanted to use JoomFish for multi-lingual support. Can anyone please let me know details of how can we use JoomFish to translate the site content. Also how can we translate the content of customly developed components / modules. Also how can we translate the static content in the components/modules i.e. the label which are used statically?
Can any one provide any reference which has a good understanding of doing the above mentioned things.
Regards,
Atul
Joomfish does not do any translation, all of it has to be entered by the admin. It takes a bit of configuration - language packs have to be installed, extension content elements need to be translated, etc. Your best bet is to install it on your site and go through the tutorials.
http://www.joomfish.net/en/documentation/tutorials
There is no shortcut that could easily be entered as an answer here.
I want to add a 'Plone portlet' widget in Faceted criteria config screen. In particular, here I need a static portlet to add URL links. How do I fill the 'Portlet macro' field for a static portlet? Helper message is 'Path to portlet macro', and I already try values like 'here/portlet_static/macros/portlet' and 'here/portlet_recent/macros/portlet', all failed.
Plone 4.0.2 + eea.facetednavigation 4.0rc1
I don't know anything about eea.facetednavigation but it sounds to me like you have a bad mix of portlet technologies.
The /macros/portlet slot was only available in classic portlets based on simple templates as used in Plone 2.5. Since Plone 3 we have a completely different portlet machinery which no longer has any TAL macros in them.
As far as I know the EEA site is still using Plone 2.5 - so I wouldn't be surprised if many of their add-ons aren't compatible with later versions of Plone.