Home » Purchase » Support Policy

Support Policy

Get expert support directly from WPML’s developers.

We will be able to answer about anything related to WPML, point you in the right directions and help you use WPML better (much better).

Typical support:

  • How to do stuff with WPML
  • How I should make my theme multilingual
  • Choosing the best alternative for translating site elements
  • Webmaster help on translation workflow

Please note that we can’t do your work for you and we can’t work magic. Here are some of the things that we can’t do and don’t promise as part of our standard support.

All technical support is provided via our forum, where WPML’s developers answer every question.

What’s NOT INCLUDED with WPML’s Support

Fix Compatibility Issues With Your Server

Folks run WordPress on many different server types. We try very hard to make sure that WPML is compatible with any environment. However, some compatibility problems remain.

We can help you trace issues and find solutions. However, we can’t always fix everything, at least not immediately.

Fix Compatibility With Other Plugins and Themes

We do our best to make WPML compatible with everything else in the WordPress world. However, much of it is not in our hands.

If you’re having a problem that involves a different plugin or theme, we can’t make it work.

We’re going to do our best to help. If you show us code fragments, we can tell you what needs changing, but we can’t maintain other plugins.

Fix Your Custom Themes

We’ll answer any question and help you get it right, but we can’t take your entire theme and debug it.

Add Features to WPML

Many great features in WPML came from user suggestions. If you have an idea for a cool new feature, we’ll take it seriously and discuss it with you. However, we can’t promise anything.

Fix Bugs in WPML

This one may sound strange, but it’s true. If you find a bug in WPML, we take it very seriously. We’ll add it to the bug-fix queue and work on it. However, we can’t fix everything right that minute. So, if you hit a bug that’s keeping you from doing something, we can’t promise that we’ll fix it right away.

We’ll work with you to find a sensible temporary solution and will let you know as soon as it’s fixed, but we can’t guarantee any schedule.

108 Responses to “Support Policy”

  1. Pranav Sharma says:

    Hi Guys ,

    I am using My Calendar plugin and WMPL full purchased edition.
    I wanna know a way to change my calendar months ,days and button text to french/english using WMPL language switcher .Please Help !

  2. Daniel says:

    Hello,

    i have a problem with the update of my WPML Multilingual CMS now i use Version 2.3.4 and it is possible to update it to Version 2.4.2.
    I have 1 year support and upgrades!?
    I bought it 6 month ago, what can the problem be and how can i get the new version?

    thanks and greetz from germany
    daniel

  3. Hector says:

    Hello there, I cannot access to my “downloads” in my account. Purchased the plugin in October/2011 … that means I should have access to download updates for a year but I cannot access. Any help please? Thanks,

    • Amir says:

      I see that your order was refunded. This is why you cannot download new versions. We refund orders when people request refunds or when PayPal notifies us that the transaction has failed.

  4. Miguel says:

    Hello WPML – I urgently need to spend 30 to 60 PAID minutes verbal on with someone this morning to get over the hump of our confusion and problems with the way WPML works. Neil is on vacation. No response from others. Please, this is hugely urgent for us. Any ideas? Thank you.

  5. Michel says:

    Hi,

    I am trying to install Site-press-multilingual-cms.2.4.3 on
    WP 3.3.1 (Godaddy site)
    Over Easy Theme from WooThemes

    No other plugin.

    This is the message I am getting:

    Unpacking the package…

    Installing the plugin…

    Destination folder already exists. /home/content/79/8889779/html/wp-content/plugins/sitepress-multilingual-cms/

    Plugin install failed.

    Please let me know what I should do.

    Michel

  6. Miguel says:

    When i activated the plugin i got this : 0
    Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, cgiadmin@yourhostingaccount.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.”

    I’m using WooeCommerce , I don’t know if i have to talk to my hosting server providor or it doesn’t work with my theme.

    Thanks.

  7. sofia says:

    Hello,

    What is the delay for answering in the support section.. .I’ve been trying to ask questions for the past 24 hours, without any results and answers…

    Thanks for letting me know what happening,

    Sofia.

    • Amir says:

      There shouldn’t be such delay. I’d like to know the URL of the forum thread that you started, so that I can look into it.

  8. Kevin says:

    I am using the latest version of Types. I just updated it today through WordPress.

    I translated a custom taxonomy. The problem is that the translation I created is exactly the same as the original. In my case, I have a (location) taxonomy. For a location, I want to have a city of Trieste in both English and Italian. But, when I “translate” Trieste from English to Italian, I end up with (Trieste @it). I want Trieste to show up for both English and Italian. Trieste is what I entered for the Italian “translation.” How do I get rid of that @it part?

    • Amir says:

      WPML adds the @lang to the taxonomy when it’s duplicate. WordPress doesn’t allow two taxonomy terms to have the same value, so we went to this solution. WPML also filters the taxonomy display calls and removes these additions.

      Can you tell me how you output the taxonomy name? If you’re using WordPress API for the output, you shouldn’t see ‘Trieste @it’, but ‘Trieste’.

    • Kevin says:

      I’m using the following code to display the taxonomy values. I guess this is the wrong code to be using because I do get the @ displaying.


      $terms = wp_get_object_terms($post_id, $taxonomy_name, $arguments);
      foreach($terms as $term)
      {
      echo $term->name;
      }

      Can you tell me what code I should be using?

Leave a Reply

Please leave here comments about this page only.
For technical support and feature suggestions, head to our forum. We are waiting there!

You can use these tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>