MarionWante

The widget needs to be set to the property type, I was wondering if the widget could be set to “any”.
If this is not possible it is better that I only use one property type and change for example “warehouse” to “plot”, since we will be needing houses and plots.
Thanks.

Great! Many thanks in advance.

Hi Merv,

I found a workaround the problem. Maybe this will bring you to new ideas.

I use the plugin ‘mqtranslate’ to make the website bilingual, dutch and english. So when I press the according flag the site changes language on the frontend.
The problem with your plugin is that it only shows the standard language as set in ‘define wplang’. So if this is set to ‘dutch’ your plugin shows in the dutch language. If I change ‘define wplang’ to english your plugin shows up in english. But…. it does not change in the admin or frontend when I change language.

What does the trick is the following:
I used mqtranslate codes in listing-meta.php to see what would happen.
For example:
if(isset($property_bedrooms) && $property_bedrooms != 0) {
$i_bed = ‘<span title=”‘.__(‘<!–:en–>Bedrooms<!–:–><!–:nl–>Slaapkamers<!–:–>‘, ‘epl’).'” class=”icon beds”><span class=”icon-value”>’. $property_bedrooms . ‘</span></span>’;

In content-listing-single.php I changed this:
<h5 class=”tab-title”><?php _e(‘<!–:en–>Description<!–:–><!–:nl–>Omschrijving<!–:–>’, ‘epl’); ?></h5>

Now when I view the admin or website and change language it will display ‘bedrooms’ for the english language and ‘slaapkamers’ for dutch etc.

The idea was that through the dutch po-file this would happen automatically, but it doesn’t.

Ofcourse I realize that changing the corefiles will cause problems with future updates of the plugin. I will have to be careful with that.

Than again, in the admin I can change the ‘features’ easily because I can add new features in the dashboard directly in dutch and english and will not have to change corefiles. Also content I can directly add in two languages.

I hope I have explained the problem better.

Regards,
Marion

Anyway, the problem is not that I do not see the Dutch translation on the site, the problem is that the plugin defaults to Dutch when nl_NL mo/po files are in the translation directory and I cannot change to english anymore. So the translations are working but at the same time default to that language.

wplang was already nl_NL on my site and also my language was set in the dashboard settings. And of course I saved to Dutch….

You don’t have to add dutch to the epl.pot file. The file is okay. Anyone can make his own translation with the pot-file. The problem is loading the files when changing language.

hi_IN is for hindi and indian languages….. I do not see the use of changing WPLANG to hi_IN?

This is a whole new perspective…….. I’ll see if I can downgrade to 3.9.

Hi there,
The wp-config.php was allready defined with nl_NL. Dutch is the main language on the site.

I suspect it has something to do with loading the translation-files.

I will provide the translated files I have thusfar on the support forum. I’m not done translating them, but it is good enough for testing purposes. I use Poedit for translating files.

Must be some tiny issue, but finding it can take up all your time. I’ve already spent hours searching for a solution.
Hopefully we will get it right!
Regards,
Marion

Thank you so much for your quick reply!

There is a bug somewhere in mqtranslate_utils.php.
With every update I replace this particular file with a previous one from an older version and ever since no problems with custom links anymore.
Hope this helps someone.

Yes, I know I can define my own, but than again I can only add a new string in one language and not in two languages. But thank you for your answer. I know I have to learn a lot more about WordPress and translations and this particular plugin is probably too complicated for me right now, although it is exactly what we need for the website. For now I will try something else.

Is there really nobody who can help me with this?