4 users online. Create an account or sign in to join them.Users
Frontend Localisation
This is an open discussion with 8 replies, filed under Extensions.
Search
-
-
- xander_group
- 09 Jan 12, 5:01 pm
- Comment #2
Frontend Localisation updated to version 1.3 on 9th of January 2012
- Fixed some bugs regarding Page's Translation management on saving a Page.
- Fixed a bug where the handle of a Translation item wasn't changing on saving through UI.
- Fixed a bug where the relation between Translation and Pages wasn't removed on Translation deletion.
At the moment, the UI allows only changing of Items handles. If you like this extension and want to make it better, you can help with creating the "Add new item" & "Delete item" features.
The primary goal at the moment is to finish the UI so not even the developer should need to edit files manually to add/delete Translation items. Everything should be done through the UI ( lazy dog :) ).
If you find other bugs, please report them on the issue tracker.
@todo list:
- add support for GNU PO and JAVA properties.
- implement
Add new item|Delete item|Item reordering (subgrouping)features (need help with the JS here).
-
-
- iwyg
- 28 Jan 12, 2:54 am
- Comment #3
I get the following error when entering "Translations" Fatal error: Call to a member function getTranslations() on a non-object in /www/siteroot/extensions/frontend_localisation/content/content.index.php on line 56
and also when creating a new page: Fatal error: Call to a member function getTranslations() on a non-object in /www/siteroot/extensions/frontend_localisation/content/content.index.php on line 222
any idea? Language driver is set To Language Redirect v1.0.3
-
-
- iwyg
- 28 Jan 12, 2:58 am
- Comment #4
Ok, seems this only occurs if entry_url extension is installed
-
-
- vladG
- 28 Jan 12, 3:17 am
- Comment #5
Multilingual Entry URL ftw :)
-
-
- xander_group
- 28 Jan 12, 3:32 am
- Comment #6
Ok, seems this only occurs if entry_url extension is installed
Odd. I can't reproduce this. I just activated Entry URL and I was able to navigate to "Translations".
Is your Symphony install a fresh one? Do you have any Pages created?
I would like to fix this. If you are kind, could you post the stack trace?
-
-
- iwyg
- 28 Jan 12, 9:49 pm
- Comment #7
It was a fresh symphony 2.2.5 installation with no pages created at this time, so also no translations.
-
-
- xander_group
- 23 Apr 12, 7:16 pm
- Comment #8
Just added some bonus to FL : Utilities templates.
It now supports params replacement, just like __(...) in PHP.
Translation file:
<data>
<p_news>
<item handle="view-all"><![CDATA[View %1$s or head back to %2$s.]]></item>
<item handle="news-link"><![CDATA[all news]]></item>
<item handle="home-link"><![CDATA[our spify home page]]></item>
</p_news>
</data>
Call template:
<xsl:call-template name="fl__">
<xsl:with-param name="context" select="'p_news/view-all'"/>
<xsl:with-param name="reps">
<rep loc="%1$s"><xsl:value-of select="fl:__('p_news/news-link')"/></rep>
<rep><xsl:value-of select="fl:__('p_news/home-link')"/></rep>
</xsl:with-param>
</xsl:call-template>
If your are slick, you can pass HTML code as well:
<xsl:call-template name="fl__">
<xsl:with-param name="context" select="'p_news/view-all'"/>
<xsl:with-param name="reps">
<rep>
<a href="http://www.xanderadvertising.com" title="Xander Advertising">
<span style="color:red">
<xsl:value-of select="fl:__('p_news/news-link')"/>
</span>
</a>
</rep>
<rep>
<a href="{/data/params/root}">
<xsl:value-of select="fl:__('p_news/home-link')"/>
</a>
</rep>
</xsl:with-param>
</xsl:call-template>
See the utility for more details.
-
-
- xander_group
- 23 Apr 12, 7:16 pm
- Comment #9
Just added some bonus to FL : Utilities templates.
It now supports params replacement, just like __(...) in PHP.
Translation file:
<data>
<p_news>
<item handle="view-all"><![CDATA[View %1$s or head back to %2$s.]]></item>
<item handle="news-link"><![CDATA[all news]]></item>
<item handle="home-link"><![CDATA[our spify home page]]></item>
</p_news>
</data>
Call template:
<xsl:call-template name="fl__">
<xsl:with-param name="context" select="'p_news/view-all'"/>
<xsl:with-param name="reps">
<rep loc="%1$s"><xsl:value-of select="fl:__('p_news/news-link')"/></rep>
<rep><xsl:value-of select="fl:__('p_news/home-link')"/></rep>
</xsl:with-param>
</xsl:call-template>
If your are slick, you can pass HTML code as well:
<xsl:call-template name="fl__">
<xsl:with-param name="context" select="'p_news/view-all'"/>
<xsl:with-param name="reps">
<rep>
<a href="http://www.xanderadvertising.com" title="Xander Advertising">
<span style="color:red">
<xsl:value-of select="fl:__('p_news/news-link')"/>
</span>
</a>
</rep>
<rep>
<a href="{/data/params/root}">
<xsl:value-of select="fl:__('p_news/home-link')"/>
</a>
</rep>
</xsl:with-param>
</xsl:call-template>
See the utility for more details.
Create an account or sign in to comment.
A new extension, "Frontend Localisation" is now available for download. Comments and feedback can be left here but if you discover any issues, please post it on the issue tracker.
Make sure you see the Readme. It's all there.
It provides the tools to add other storage formats like GNU PO and JAVA properties, for example. At the moment I don't have the time to add them, but if there's a brave guy out there to help with it ... :)