eqhes
Forum Replies Created
-
AuthorPosts
-
Hi,
I’ve updated to Geodirectory 1.1.6 and I still have problems with strings translated with WPML. I know how to solve them. @stiofan, @rightmentor or @guust, can you tell me how to send code changes to you?
Fine. Thank you very much.
This reply has been marked as private.More information that may be interesting in order to check the issue:
If on step 3b) I don’t check “Use different slugs in different languages for Places.”, but I go to “WPML –> String Translation” and there I translate the URL slug (looking for “%gd_taxonomy%” gets me the string to translate), then I see the URL getting translated properly in the public side, but the new URL throws a 404 error when accessing to it.
Hope you can understand me and see what I’m talking about :).
This is how I do this:
1. Make that custom post type translatable
a) WPML –> Translation Management –> Multilingual Content Setup –> Custom posts
b) Check “Translate” for those custom post types you want to translate. For example: “Places”.
c) “Save”
2. Enable slug translation for the site
a) WPML –> Translation Management –> Multilingual Content Setup –> Custom posts slug translation options
b) Check “Translate custom posts slugs (via WPML String Translation).”
c) “Save”
3. Select to use different slugs in different languages
a) WPML –> Translation Management –> Multilingual Content Setup –> Custom posts
b) For your preferred custom post type (p.e. “Places”) you can check “Use different slugs in different languages for Places.”
c) Read the issue with this option on my first missage on this thread.
Hi @stiofan,
Sorry about the delay. You can follow the official WPML documentation: http://wpml.org/documentation/getting-started-guide/translating-page-slugs/
Regards.
Yes, @paolo, I followed the steps. I’m not sure if this is working or not because I don’t know where I should see the analytics information. Maybe if you could send us a screenshot I could check if I’m looking into the right place.
@sporkmarketing I think the instructions are easy enough. If you check the “Google Analytics password for api” section you will get the answer to your questions. API is needed to get Google Analytics data. Without using the API, developers can’t get access to this information.
I’ve found a hardcoded text in /geodir_event_manager/gdevents_template_function.php:
echo '<h3>How to Register</h3>';
Should be:
echo '<h3>'.__('How to Register', GEODIREVENTS_TEXTDOMAIN).'</h3>';
Found the solution to my sitemap problem here: http://theme-fusion.com/forums/topic/seo-by-yoast-avada-404-sitemap-error/#post-49023
I tweaked the Avada theme for my own and here is the result, if you want to check it out: http://ebrencs.cat
😉
Hi,
When loading http://mydomain.com/sitemap_index.xml I get a 404 error page. This happens to you also @fabien?
Regards.
This reply has been marked as private.Geodirectory –> Notifications
Any of this texts are able to be translated. At least using WPML… I’ve checked the “WPML –> String translation –> Translate texts in admin screens” and there aren’t this strings also.
?geodir_signup=true
All the strings on the two forms (sin in and sign up), including all error messages.
-
AuthorPosts