Title: WPML Compatibility
Last modified: December 21, 2017

---

# WPML Compatibility

 *  Resolved [Alexandre Gauvin](https://wordpress.org/support/users/pictogram/)
 * (@pictogram)
 * [8 years, 7 months ago](https://wordpress.org/support/topic/wpml-compatibility-124/)
 * After days of struggling with a multilingual project including WPML and GigPress,
   I came with a fix that could be included in future releases of your plugin.
 * This fix will allow to translate the strings in the input fields in GigPress’s
   settings page. By adding some code, GigPress input fields will be scanned by 
   WPML
 * Here is what could be done :
    1- Open gigpress.php in /wp-content/plugins/gigpress/
 * 2- Below the line #243 `global $wpdb, $gp_countries, $gpo;`, add the following
   code
 *     ```
       $test = get_option('gigpress_settings');
       $buy_tickets_label = $test['buy_tickets_label'];
       ```
   
 * 3- Then go to line #325 and change the following code
    `case 'active': $showdata['
   ticket_link'] = ($show->show_tix_url && $show->show_expire >= GIGPRESS_NOW) ?'
   <a href="' . esc_url($show->show_tix_url) . '"' . gigpress_target($show->show_tix_url).'
   class="gigpress-tickets-link">' . wptexturize($gpo['buy_tickets_label']) . '</
   a>' : '';` to
 *     ```
       case 'active': $showdata['ticket_link'] = ($show->show_tix_url && $show->show_expire >= GIGPRESS_NOW) ? '<a href="' . esc_url($show->show_tix_url)  . '"' . gigpress_target($show->show_tix_url) . ' class="gigpress-tickets-link">' . wptexturize($buy_tickets_label) . '</a>' : '';
       ```
   
 * 4- Go to WPML and translate.
    -  This topic was modified 8 years, 7 months ago by [Alexandre Gauvin](https://wordpress.org/support/users/pictogram/).
    -  This topic was modified 8 years, 7 months ago by [Alexandre Gauvin](https://wordpress.org/support/users/pictogram/).

Viewing 2 replies - 1 through 2 (of 2 total)

 *  [Barry](https://wordpress.org/support/users/barryhughes-1/)
 * (@barryhughes-1)
 * [8 years, 6 months ago](https://wordpress.org/support/topic/wpml-compatibility-124/#post-9953734)
 * Sounds good!
 * We’re open for pull requests, so if you’d like to propose a change to the code
   please do feel free to send us one:
 * [github.com/moderntribe/gigpress](https://github.com/moderntribe/gigpress)
 * One of our developers can then review and, if they agree, merge in the change
   🙂
 *  [Ed](https://wordpress.org/support/users/erishel/)
 * (@erishel)
 * [8 years, 2 months ago](https://wordpress.org/support/topic/wpml-compatibility-124/#post-10362584)
 * Hey there,
 * Since this thread has been inactive for a while, I’m going to go ahead and mark
   it as resolved. Don’t hesitate to create a new thread any time you help again!
 * Ed 🙂

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘WPML Compatibility’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/gigpress_8434ab.svg)
 * [GigPress](https://wordpress.org/plugins/gigpress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/gigpress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/gigpress/)
 * [Active Topics](https://wordpress.org/support/plugin/gigpress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/gigpress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/gigpress/reviews/)

 * 2 replies
 * 3 participants
 * Last reply from: [Ed](https://wordpress.org/support/users/erishel/)
 * Last activity: [8 years, 2 months ago](https://wordpress.org/support/topic/wpml-compatibility-124/#post-10362584)
 * Status: resolved