If after following all the instructions from our checklist before opening a ticket in WPML support, you are still having issues or struggling to translate your site, it may be time to come to our support forum.

The first thing you will notice is that our system will ask you to describe what are you trying to achieve. This allows our system to check its database and see if there is already a solution to your issue. Try to describe your situation in an easy and simple way. This will increase your chances to find a match.

Opening a support ticket
Opening a support ticket

Once you do it, some new content will appear on the page. First, an Errata & Support FAQ matching your question section pop-ups. This section lists different pages from our documentation that may be helpful for your situation.

Below this section, there is another section called Support tickets matching your question which, as the name suggests, points you to all our support tickets that may be related to your issue.

Finally, If you still can’t find what you are looking for, it is time to click the Open a new support ticket button.

Open a new support
Open a new support

Providing WPML debug information

In order to give you a better and faster support, we need as much information as you can provide us.

There is an important section at WPML -> Support under the debug information link. When you add this information at the moment of opening a ticket, we will have a general view of your site: from which PHP and server configuration, theme and plugins installed to your WPML settings.

Often, the issues that you are experiencing have been already solved by upgrading or modifying any of your settings. When we have access to your debug information, we increase the chance to easily provide you with a solution for those cases.

WordPress debug information

In addition to WPML debug information, there is something else called WordPress debug information. This information usually points to plugins, themes or server errors which help developers to find bugs and improve their code standards.

For users, this information is specifically important for situations where you have the infamous blank screen as usually there is a PHP error what will appear once the WordPress debug information is activated. Furthermore, it will also point to possible incompatibilities with themes and plugins which may not be designed to be multilingual-ready.

To activate this feature, you need to access to your server using FTP and edit your wp-config.php file as described in the WordPress Codex.

If you have access to this information, don’t hesitate to share it with us, our support will find it really useful.

Provide us with clear steps to reproduce the issue

It may sound obvious but this is a more important step at the moment of creating a ticket in our support. Sometimes, it’s hard to describe what is happening in your site and what you are trying to achieve. Thus, the clearer and more direct your description of the issue is, the sooner and faster our support will understand what is happening and help you.

An easy way to describe your issue may be something like:

  1. I want to do [action].
  2. When I go to this [section] and I try to [action], I get [undesired output] while I should get [desired output].

This formula is not a general rule, but sometimes it helps to verbalize what is happening on your site.

Sometimes, describing an issue with words can be difficult so feel free to also provide screenshots or even a video.

Sharing a copy of your site

Sometimes, it may happen that your issue is not as easy to solve as changing a setting or upgrading your WordPress site version. In this case, our supporters may need a copy of your site to start the debugging process and find what could be causing the issue.

In the following tutorial we explain how to easily share a copy of your site with our supporters.