<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title><![CDATA[Realtyna.com]]></title>
<link><![CDATA[https://support.realtyna.com/]]></link>
<description />
<generator><![CDATA[Kayako fusion v4.80.0]]></generator>
<item>
<title><![CDATA[How do I translate WPL?]]></title>
<link><![CDATA[https://support.realtyna.com/index.php?/Knowledgebase/Article/View/537]]></link>
<guid isPermaLink="false"><![CDATA[5ea1649a31336092c05438df996a3e59]]></guid>
<pubDate><![CDATA[Wed, 09 Apr 2014 13:54:53 -0400]]></pubDate>
<dc:creator />
<description><![CDATA[WPL is a translate ready plugin, so you can simply translate it to your language like other WordPress plugins. Please read the following article and generate your .mo file.
https://premium.wpmudev.org/blog/how-to-translate-a-wordpress-plugin/
The WPL de...]]></description>
<content:encoded><![CDATA[<p>WPL is a translate ready plugin, so you can simply translate it to your language like other WordPress plugins. Please read the following article and generate your .mo file.</p>
<p><a href="https://premium.wpmudev.org/blog/how-to-translate-a-wordpress-plugin/">https://premium.wpmudev.org/blog/how-to-translate-a-wordpress-plugin/</a></p>
<p>The WPL default language file is placed on this path: /wp-content/plugins/real-estate-listing-realtyna-wpl/languages/real-estate-listing-realtyna-wpl-en_US.po or /wp-content/plugins/real-estate-listing-realtyna-wpl-pro/languages/real-estate-listing-realtyna-wpl-en_US.po for WPL PRO users. You can copy and rename this file to your language code (e.i. real-estate-listing-realtyna-wpl-es_ES.mo) and then translate the new file.</p>
<p>After that you should place your translated file into the WordPress language directory of plugins (Normally it is <strong>/wp-content/languages/plugins/</strong>) and change the WordPress language in wp-config.php file. If you're using WordPress 4.0+, you can change WordPress language from Settings-&gt;General menu as well. Please check following screenshot:</p>
<p><img src="http://wpl.realtyna.com/wassets/kb_change_language1.png" alt="" width="627" height="582" /></p>
<p>You can also use the WMPL plugin or other plugins if you installed one of them.</p>
<p><span style="color: #ff0000;">Note: After modifying keywords, you should clear listing cached data. You can find it on WPL Settings-&gt;Maintenance section:</span></p>
<p><img src="http://wpl.realtyna.com/wassets/kb_translate6.png" alt="" width="783" height="241" /></p>]]></content:encoded>
</item>
<item>
<title><![CDATA[How to create a multilingual WP website using WPML plugin?]]></title>
<link><![CDATA[https://support.realtyna.com/index.php?/Knowledgebase/Article/View/748]]></link>
<guid isPermaLink="false"><![CDATA[e49b8b4053df9505e1f48c3a701c0682]]></guid>
<pubDate><![CDATA[Thu, 15 Dec 2016 05:08:19 -0500]]></pubDate>
<dc:creator />
<description><![CDATA[Installation
If you want to create a WordPress multilingual website, then you don't have many choices. You can use free plugins such as Polylang, qTranslate etc or use a premium plugin like WPML.
We strongly suggest to use WPML since it's the most compl...]]></description>
<content:encoded><![CDATA[<h2>Installation</h2>
<p>If you want to create a WordPress multilingual website, then you don't have many choices. You can use free plugins such as Polylang, qTranslate etc or use a premium plugin like WPML.</p>
<p>We strongly suggest to use WPML since it's the most complete solution for creating a multilingual WP website.</p>
<h2>Configuration</h2>
<p>After installing and activating the WPML, then you should configure it, wrong configuration can create many problems for your website so please configure it with caution. We suggest to read this article carefully and proceed with its instructions: <a href="https://wpml.org/home/how-to-build-a-multilingual-wordpress-website/" target="_blank">How to Create a Multilingual WordPress Site with WPML</a></p>
<p>Also you can check WPML official guide for language configuration: <a href="https://wpml.org/documentation/getting-started-guide/language-setup/" target="_blank">WPML Language Setup</a></p>
<h2>Translating</h2>
<p>After configuration, then you need to start translating your website contents. Please check the following articles for each section.</p>
<p><a href="https://wpml.org/documentation/translating-your-contents/" target="_blank">Translating Posts/Pages</a></p>
<p><a href="https://wpml.org/documentation/getting-started-guide/translating-post-categories-and-custom-taxonomies/" target="_blank">Translating Categories/Tags/Custom Taxonomies</a></p>
<p><a href="https://wpml.org/documentation/getting-started-guide/translating-menus/" target="_blank">Translating Menus</a></p>
<p><a href="https://wpml.org/documentation/getting-started-guide/translating-widgets/" target="_blank">Translating Widgets</a></p>
<p><a href="https://wpml.org/documentation/getting-started-guide/string-translation/" target="_blank">Translating Strings</a></p>
<p>Anything that doesn’t fall inside posts, pages or taxonomy goes into String Translation. This includes the site’s tagline, general texts in Admin screens, widget titles and many other texts.</p>
<h2>Translate WPL listings</h2>
<p>Using WPL multilingual feature, you can simply configure your WPL to work with WPML. This way you're able to translate property descriptions, property titles, location texts, page titles etc simply. Please check this article completely: <a href="https://support.realtyna.com/index.php?/Default/Knowledgebase/Article/View/601/" target="_blank">WPL Multilingual Feature</a></p>
<p>Also if you added your custom fields using WPL Flex, then you're able to translate those fields using WPML String Translation menu. Please check this article: <a href="https://support.realtyna.com/index.php?/Default/Knowledgebase/Article/View/639/" target="_blank">Translating dynamic WPL strings</a></p>
<h2>Language Switcher</h2>
<p>After translating your website contents, then you should <a href="https://wpml.org/documentation/getting-started-guide/language-setup/#language_switcher" target="_blank">place a language switcher</a> into your website so visitors can simply choose their desired language. Also you may check <a href="https://wpml.org/documentation/getting-started-guide/language-setup/language-switcher-options/" target="_blank">language switcher options</a> to achieve your desired style.</p>
<h2>Appendix</h2>
<p><a href="https://wpml.org/documentation/getting-started-guide/language-setup/setting-the-wordpress-administration-language/" target="_blank">Change WordPress admin language</a></p>
<p><a href="https://wpml.org/faq/server-setting-for-languages-in-different-domains/" target="_blank">Different domains for languages</a></p>]]></content:encoded>
</item>
<item>
<title><![CDATA[How to fix translation issue after upgrading to WPL4.4.0?]]></title>
<link><![CDATA[https://support.realtyna.com/index.php?/Knowledgebase/Article/View/832]]></link>
<guid isPermaLink="false"><![CDATA[7250eb93b3c18cc9daa29cf58af7a004]]></guid>
<pubDate><![CDATA[Tue, 05 Feb 2019 07:11:32 -0500]]></pubDate>
<dc:creator />
<description><![CDATA[To be fully compatible with WordPress translation project we did some changes on WPL text domain and strings since 4.4.0If you have a multi-lingual website and you translated the language files yourself you may face some issues after upgrading to latest v...]]></description>
<content:encoded><![CDATA[To be fully compatible with WordPress translation project we did some changes on WPL text domain and strings since 4.4.0<br />If you have a multi-lingual website and you translated the language files yourself you may face some issues after upgrading to latest version of WPL but it's simply fix-able.<br /><br />What you need to do is to copy existing language files into the <strong>/wp-content/languages/plugins/</strong> directory and rename them from wpl-[locale].mo to real-estate-listing-realtyna-wpl-[locale].mo<br />Here are some examples:<br /><br />Copy /wp-content/languages/real-estate-listing-realtyna-wpl/wpl-es_ES.mo to /wp-content/languages/plugins/real-estate-listing-realtyna-wpl-es_ES.mo<br />Copy /wp-content/languages/real-estate-listing-realtyna-wpl-pro/wpl-it_IT.mo to /wp-content/languages/plugins/real-estate-listing-realtyna-wpl-it_IT.mo<br /><br />- If you don't see /wp-content/languages/real-estate-listing-realtyna-wpl/ or /wp-content/languages/real-estate-listing-realtyna-wpl-pro/ directories on your website then you shouldn't have any problem.<br />- You can keep the existing language files and also you can copy .po files in addition to .mo files. You just need to rename them.<br />- After copying the files everything should work as before. To copy the files you can use any FTP client or use File Manager tool in your website cPanel.<br />- If you're using PRO version of WPL, you <strong>don't need</strong> to add -pro to the language files anymore.]]></content:encoded>
</item>
<item>
<title><![CDATA[How to translate dynamic strings/keywords?]]></title>
<link><![CDATA[https://support.realtyna.com/index.php?/Knowledgebase/Article/View/639]]></link>
<guid isPermaLink="false"><![CDATA[0f96613235062963ccde717b18f97592]]></guid>
<pubDate><![CDATA[Fri, 06 Mar 2015 12:11:40 -0500]]></pubDate>
<dc:creator />
<description><![CDATA[You may add new Listing Types or Property Types or Fields or new location names such as new countries, provinces etc in your WPL. Therefore you need to translate them as well if you have a multilingual website. WPL PRO has a feature for generating dynamic...]]></description>
<content:encoded><![CDATA[<p>You may add new Listing Types or Property Types or Fields or new location names such as new countries, provinces etc in your WPL. Therefore you need to translate them as well if you have a multilingual website. WPL PRO has a feature for generating dynamic strings in a single PHP file located in /path/to/plugin/languages/keywords.php</p>
<p>For generating dynamic strings go to WPL-&gt;Settings-&gt;Languages and click on "Generate WPL dynamic strings for using in translation plugins like WPML" button.</p>
<p><img src="http://wpl.realtyna.com/wassets/kb_dynamic_strings1.png" alt="" width="1005" height="482" /></p>
<p>Then use one of following approaches:</p>
<p>1- Rescan WPL strings using "WPML String Translation" plugin if you're using WPML plugin.</p>
<p>2- Add /path/to/plugin/languages/keywords.php keywords into your .po file (using some tools like <a href="https://localise.biz/free/converter/php-to-po">this</a>) and translate dynamic strings and then upload new .mo file in <a href="https://support.realtyna.com/index.php?/Default/Knowledgebase/Article/View/537/">language directory</a>.</p>]]></content:encoded>
</item>
<item>
<title><![CDATA[How to translate WPL Data structure (Property Types, Listing Type...]]></title>
<link><![CDATA[https://support.realtyna.com/index.php?/Knowledgebase/Article/View/532]]></link>
<guid isPermaLink="false"><![CDATA[298f95e1bf9136124592c8d4825a06fc]]></guid>
<pubDate><![CDATA[Mon, 31 Mar 2014 01:53:15 -0400]]></pubDate>
<dc:creator />
<description><![CDATA[All of the WPL data structure texts are keywords and you can easily translate them. You can find these strings in the default .po file of WPL. Please see the following screenshots:
    
Note: If you added some new Listing Types, Property Types etc. and ...]]></description>
<content:encoded><![CDATA[<p>All of the WPL data structure texts are keywords and you can easily translate them. You can find these strings in the default .po file of WPL. Please see the following screenshots:</p>
<p><img src="http://wpl.realtyna.com/wassets/kb_translate1.png" alt="" width="315" height="546" /> <img src="http://wpl.realtyna.com/wassets/kb_translate2.png" alt="" width="400" height="258" /> <img src="http://wpl.realtyna.com/wassets/kb_translate3.png" alt="" width="298" height="564" /> <img src="http://wpl.realtyna.com/wassets/kb_translate4.png" alt="" width="327" height="608" /> <img src="http://wpl.realtyna.com/wassets/kb_translate5.png" alt="" width="336" height="379" /></p>
<p><span style="color: #ff0000;">Note: If you added some new Listing Types, Property Types etc. and you want to include new keywords in language file, Please go to WPL-&gt;Settings-&gt;Languages and click "Generate WPL dynamic strings" button.</span></p>
<p><span style="color: #ff0000;"><img src="http://wpl.realtyna.com/wassets/kb_translate_dynamic_strings1.png" alt="" width="582" height="525" /></span></p>
<p>If you're using WPML string translator or any other plugins. Now your plugin should find dynamic keywords. If you're translating a .po file directly you should update your .po file manually.</p>
<p><span style="color: #ff0000;">Note: After modifying keywords or translating keywords you should clear listing cached data. You can find it on WPL Settings-&gt;Maintenance section:</span></p>
<p><img src="http://wpl.realtyna.com/wassets/kb_translate6.png" alt="" width="783" height="241" /></p>]]></content:encoded>
</item>
<item>
<title><![CDATA[How to use multilingual feature of WPL PRO to create a multilingu...]]></title>
<link><![CDATA[https://support.realtyna.com/index.php?/Knowledgebase/Article/View/601]]></link>
<guid isPermaLink="false"><![CDATA[b2f627fff19fda463cb386442eac2b3d]]></guid>
<pubDate><![CDATA[Wed, 19 Nov 2014 08:57:51 -0500]]></pubDate>
<dc:creator />
<description><![CDATA[The Multilingual feature has been added since WPL PRO2.0.0.
For creating multilingual websites using WordPress, you need to use one of the multilingual plugins first, such as WPML, etc.
Note: You should configure your multilingual plugin first. For inst...]]></description>
<content:encoded><![CDATA[<p>The Multilingual feature has been added since WPL PRO2.0.0.</p>
<p>For creating multilingual websites using WordPress, you need to use one of the multilingual plugins first, such as WPML, etc.</p>
<p><span style="color: #ff0000;">Note: You should configure your multilingual plugin first. For instructions, go to the plugin manuals or support forums.</span></p>
<p><span style="color: #ff0000;">Note: If you translate the strings using WPML string translation plugin, don't forget to add .mo files of languages in /wp-content/languages/plugins/ path otherwise some sections won't work properly. For this you can download .po files from WPML and then convert them to .mo files using poedit software.</span></p>
<p>After installing and configuring one of the standard multilingual plugins, you need to enable the multilingual feature of WPL. You can enable it from WPL-&gt;Settings-&gt;Languages-&gt;Multilingual Status. It is disabled by default.</p>
<p><img src="http://wpl.realtyna.com/wassets/kb_multilingual1.png" alt="" width="714" height="227" /></p>
<p>Then you should insert installed languages into WPL language options and select a page as the WPL main page. Each language must have its own WPL main page so you should translate your default WPL main page to other languages:</p>
<p><img src="http://wpl.realtyna.com/wassets/kb_multilingual2.png" alt="" width="1103" height="361" /></p>
<p><img src="http://wpl.realtyna.com/wassets/kb_multilingual3.png" alt="" width="597" height="363" /></p>
<p><span style="color: #ff0000;">Note: If you cannot see translated pages in drop-down field please set your language option to all languages. Please see below figure:</span></p>
<p><img src="http://wpl.realtyna.com/wassets/kb_multilingual9.png" alt="" width="780" height="635" /></p>
<p>After completing these steps, you should specify your multilingual fields. Go to 'flex' and edit one of text or textarea fields.</p>
<p><img src="http://wpl.realtyna.com/wassets/kb_multilingual4.png" alt="" width="844" height="293" /></p>
<p><img src="http://wpl.realtyna.com/wassets/kb_multilingual5.png" alt="" width="712" height="390" /></p>
<p>You're done!</p>
<p><img src="http://wpl.realtyna.com/wassets/kb_multilingual6.png" alt="" width="533" height="322" /></p>
<p><strong>Multilingual Property Link (Alias/Permalink) and/or Property Location Text</strong></p>
<p>For making Alias/Permalink and/or Property Location Text you can simply set their multilingual option to Yes in Flex menu and clear the listing and users cached data in Settings menu.</p>
<p><img src="http://wpl.realtyna.com/wassets/kb_multilingual7.png" alt="" width="611" height="273" /></p>
<p><img src="http://wpl.realtyna.com/wassets/kb_multilingual8.png" alt="" width="577" height="284" /></p>]]></content:encoded>
</item>
<item>
<title><![CDATA[Make WPL RTL for Arabic and Hebrew language]]></title>
<link><![CDATA[https://support.realtyna.com/index.php?/Knowledgebase/Article/View/814]]></link>
<guid isPermaLink="false"><![CDATA[96b9bff013acedfb1d140579e2fbeb63]]></guid>
<pubDate><![CDATA[Tue, 31 Jul 2018 06:29:37 -0400]]></pubDate>
<dc:creator />
<description><![CDATA[Starting from version 4.2.0, WPL provides RTL support for Arabic and Hebrew languages.If you want to use one of these languages for your website, you just need to go to the WP admin panel-&gt;Settings-&gt;Global-&gt;Site Language and choose Arabic or Hebr...]]></description>
<content:encoded><![CDATA[Starting from version 4.2.0, WPL provides RTL support for Arabic and Hebrew languages.<br />If you want to use one of these languages for your website, you just need to go to the WP admin panel-&gt;Settings-&gt;Global-&gt;<span>Site Language and choose Arabic or Hebrew language.<br />The WPL <gwmw class="ginger-module-highlighter-mistake-type-1" id="gwmw-15613882899477417582677">backend</gwmw> and <gwmw class="ginger-module-highlighter-mistake-type-1" id="gwmw-15613882899470842772917">frontend</gwmw> views will be <gwmw class="ginger-module-highlighter-mistake-type-3" id="gwmw-15613882899472720380936">change</gwmw> to the RTL version automatically.<br /><br />If you want to create a WordPress multilingual website, then check this article: <a href="https://support.realtyna.com/index.php?/Default/Knowledgebase/Article/View/748/75/how-to-create-a-multilingual-wp-website-using-wpml-plugin" target="_blank">How to create a multilingual WP website using WPML plugin</a><br /><br /></span>]]></content:encoded>
</item>
<item>
<title><![CDATA[Realtyna WPL PRO Translation Project]]></title>
<link><![CDATA[https://support.realtyna.com/index.php?/Knowledgebase/Article/View/739]]></link>
<guid isPermaLink="false"><![CDATA[df263d996281d984952c07998dc54358]]></guid>
<pubDate><![CDATA[Thu, 13 Oct 2016 21:22:59 -0400]]></pubDate>
<dc:creator />
<description><![CDATA[We are currently building a catalogue in WPL Pro that will provide you with the opportunity to translate your Realtyna website platform into the language of your choice at no cost!
Please see our catalogue below and check if we have your preferred langua...]]></description>
<content:encoded><![CDATA[<p>We are currently<span style="font-size: 10pt;"> building</span> a catalogue in WPL Pro that will provide you with the opportunity to translate your Realtyna website platform into the language of your choice at no cost!</p>
<p>Please see our catalogue below and check if we have your preferred language:</p>
<ol>
<li><span style="color: #333333;">English (US)<br /></span></li>
<li><span style="color: #333333;"><span style="color: #333333;">English (UK)</span></span></li>
<li><span style="color: #333333;">Italian</span></li>
<li><span style="color: #333333;">Serbian</span></li>
<li><span style="color: #333333;">Spanish</span></li>
<li><span style="color: #333333;">Croatian</span></li>
<li><span style="color: #333333;">French</span></li>
<li><span style="color: #333333;">Danish (Denmark)</span></li>
</ol>
<p><strong> Don't see your language?</strong> Since this is a brand new project, you have an opportunity to join the team and reap the benefits!<br /> We are currently building our language portfolio and we want your help! If you have translated WPL to German, Spanish, French... and you don't see that language on the list, let us know! For a limited time, we are offering a 20% discount on our Realtyna products in exchange for your language file.</p>
<p>If you have been contemplating purchasing one of our products, now might be just the time! <br /> <span style="color: #ff0000;"><em>* Coupon voucher is valid up to 6 months</em></span></p>]]></content:encoded>
</item>
</channel>
</rss>