98

WPML 2.0 is a major change from previous versions. It implements a complete translation process, with translators, a jobs queue and a side-by-side translation editor.

A Complete Translation Workflow

Wouldn’t it be nice if translators could only edit content in their language?

Not only that WPML 2.0 allows that, but it’s the way things will work naturally.

Instead of hacking it with Role management plugins, WPML now defines a new translator role. A translator can do jobs assign to him/her. Translators can’t just go in and write content in their language. They do jobs that the admin assigns.

Admins go to the WPML->Translation Management. There they give users translator privileges. Then, they go to the Translation Dashboard and send jobs to translation.

WPML sends notification emails to the translators, they translate and WPML notifies back the Admin that translation is done.

Side-by-Side Translation Editor

It’s a little inconvenient having to run back and forth between the original and translation. It’s also not going to be needed anymore.

WPML 2.0 includes a new Translation Editor. This editor shows each field for translation. It shows the original text and allows writing the translation. Just like the standard WP editor, you can switch between Visual and HTML modes.

BTW, we’re already working on even more powerful translation capabilities. Look out for Trados interface, an integrated Translation Memory and other goodies in the next WPML releases. If you want to help, take our poll about which translation tools you’re using.

Integration with Themes and Plugins

Another painful point was always:

“which custom fields need translation?”

Much of the power of WordPress comes from its impressive array of plugins. Plugins typically use custom fields in order to store their data. For instance, SEO plugins store meta description and page title (among other fields).

It was pretty difficult to tell WPML which custom fields should be translated, which to synchronize and which to leave alone.

Now, with the introduction of language configuration files, it’s mighty easy.

You can include a small XML file with your theme or plugin. WPML reads those files and learns from them what to include when sending content to translation.

Users can also edit this information via GUI by visiting WPML->Translation Management->Multilingual Content Setup.

98 Responses to “WPML 2.0”

  1. Hey guys,
    great job…
    did you manage in some way to increase the compatibility with wp e-commerce?
    Thanks for this wonderful plugin!!
    I’m going to buy the one year support next week!
    cheers

    enrico

    • You hit the nail on the head. The more support subscriptions people purchase, the more resources we have towards e-commerce compatibility. If you purchase these support subscriptions before you need any help, you’re actually supporting us.

      • Hi Amir, this bug persist also in 2.0

        http://forum.wpml.org/topic.php?id=2122

        For fix it, in /modules/cms-navigation/cms-navigation.php, add AND post_type ‘nav_menu_item’ where you have sql that contains AND post_status=’publish’.

        Example:

        $sub = $wpdb->get_results("
        SELECT p1.ID, meta_value AS section FROM {$wpdb->posts} p1
        LEFT JOIN {$wpdb->postmeta} p2 ON p1.ID=p2.post_id AND (meta_key='_cms_nav_section' OR meta_key IS NULL)
        WHERE post_parent='{$pid}' AND post_status='publish' AND post_type 'nav_menu_item' ORDER BY {$order}");

          • Solved. Line 560:


            $sub = $wpdb->get_results("
            SELECT p1.ID, meta_value AS section FROM {$wpdb->posts} p1
            LEFT JOIN {$wpdb->postmeta} p2 ON p1.ID=p2.post_id AND (meta_key='_cms_nav_section' OR meta_key IS NULL)
            WHERE post_parent='{$pid}' AND post_status='publish' ORDER BY {$order}");

            change with:

            $sub = $wpdb->get_results("
            SELECT p1.ID, meta_value AS section, post_type FROM {$wpdb->posts} p1
            LEFT JOIN {$wpdb->postmeta} p2 ON p1.ID=p2.post_id AND (meta_key='_cms_nav_section' OR meta_key IS NULL)
            WHERE post_parent='{$pid}' AND post_type 'nav_menu_item' AND post_status='publish' ORDER BY {$order}");

    • I am currently trying a combination of PHPurchase and Gravity Forms.

      PHPurchase does not support multiple languages (yet), but Gravity Forms does and there are some cool ways to integrate the two.

      Together with a WPML backbone, I think you can get very far in making it work!

      It goes without saying that supporting Amir and the rest of the WPML team is money very well spent!

  2. Hi Amir,
    Wow, just upgraded to 2.0 and many cool changes indeed, thanks!
    One question about the compatibility packages. I saw the following line:
    WPML compatibility packages will soon be obsolete and removed. Please use other means to make your site multilingual-ready.
    I am running the Headspace2 compatibility package. If this becomes obsolete and will be deleted, will that have any negative impact on my site(s)?

    • We have a tiny XML languages setup file that sets everything that HeadSpace2 needs. Now, all we need to do is convince HeadSpace2 author to include it in their plugin.

      Otherwise, you’ll need to manually choose which custom fields and Admin texts to translate (once).

      • Sounds good to me. Obviously it would be ideal if Urbangiraffe includes it, but I don’t mind doing it manually.

        Something else.

        I noticed that few settings changed after the upgrade. One example was that I had to redo the settings of the language switcher in the header. Not a big problem of course, but perhaps a tiny buggy?

    • Hi Amir,

      First off, I’m excited for this upgrade, as it’ll help a lot for a huge translation project coming up. And yes, I’m more than happy to announce that I’ll be using the professional translation service.

      I’m with Piet on this one, I too get the same message:

      “WPML compatibility packages will soon be obsolete and removed. Please use other means to make your site multilingual-ready.”

      I’m running Atahualpa 3.4.9 with the following compatability package: Extra options for the Atahualpa theme 1.0 This package enables basic Atahualpa-WPML compatibility. atahualpa (3.4.4).

      How would I go about remedying this?

      • Great. I’m glad that you noticed that message. Have a look at this page:
        http://wpml.org/documentation/support/language-configuration-files/available-config-files/

        You’ll see the language configuration file for Atahualpa, proudly available for download.

        What you need to do is download it, unzip and place in Atahualpa’s root directory.

        Then, turn off the compatibility package for Atahualpa, as this tiny file replaces it.

        Next, head over to the Atahualpa form and ask them to include this XML file with the theme. This way, everyone using Atahualpa gets WPML pre-configured.

        Let me know how it’s going.

  3. Hi, I’m Paolo from Italy – proud user of WPML!
    I’ve just upgraded to 2.0 (still checking all the new feature).

    After the installation, now I noticed that on the Admin dashboard I can’t open the various boxes (like the QuickPress, Blog WordPress, etc…) and even the Language box in the Edit Post page do not open/slide down – seems like the js of the admin stop working (the left menu sidebar still working thou). Any clue?

    Thanks. Ciao
    Paolo

    • Try to force a full reload. Maybe the new JS in WPML 2.0 is not loaded and you’re getting an older cached version.

      If this doesn’t help, try:
      1) A different kind of browser.
      2) Use FireFox and Firebug and check if you’re getting errors in the JS console.

      Let us know what you find.

      • forgot to copy the code line:

        addLoadEvent(function(){
        jQuery('#locations-0 option').first().html('not translated in current language');
        jQuery('#locations-0').css('font-style','italic');
        jQuery('#locations-0').change(function(){if(jQuery(this).val()!=0) jQuery(this).css('font-style','normal');else jQuery(this).css('font-style','italic')});
        });

      • (Sorry, I don’t know if you received my first…)

        I have the same error, Firebug console says:

        jQuery("#locations-0 option").first is not a function

        Thanks a lot
        Alessandro

        • WP core uses JQuery, just like WPML and anything else on that page.

          You can try to view the HTML source of the page and check if the selectors are defined twice.

          I can’t see how WPML will cause something like this, since it uses the WP API to create forms.

          • maybe this can help: if I activate the plugin, it doesn’t recognize the default language (en) in the languages section.

            What I did is uninstall the previous WPML version, remove all wp_icl_[…] tables from db and reinstall the latest plugin version uploading all files via ftp.

            Thanks
            Ale

  4. I upgraded to ver 2.0 and I like the dashboard. One thing I noticed is that when I activated manual translation in the “Select how to localize the theme” > “Translate the theme by WPML”, the language switcher disappears in my secondary language. Using the “Using a .mo file in the theme directory” option resolve this.

  5. Hi, I’m using wordpress 3.1 (i know it’s an alpha release) and updated WPML to version 2, now I’m seeing a message that says “WPML requires database upgrade” the problem is that the “Run Upgrade Process” always return a popup saying error. No clue what’s happening. Any advice?

    Thanks in advance

    • Try using Firefox and Firebug and see if you’re getting any errors in the JS console. We didn’t try with WP3.1 Alpha, so I don’t know what you’re seeing. Also, I suggest to enable WPML’s debug mode, to catch any PHP errors. And, go to WPML->Support->Troubleshoot. Look for the checkbox to ‘raise MySQL errors’. This will cause a PHP error for any MySQL error. It’s a very strict debug mode.

      • Hey, I seem to have the exact same problem. I checkd with FireBug and it sends an AJAX request wit the params
        icl_ajx_action = wpml_upgrade_2_0_0
        init = 1

        And the respnse is just this: -1

        What can I do?

  6. Hi Amir, I just updated to 2.0 and it seems it just destroyed my website and it seems the navigation.php will not work as the change you have talked about it on above comments, can you help me if I can get previous version or get my site back in shape please? thanks

    • What you should do is:
      1) Get the DB snapshot that you created just before the upgrade and use it.
      2) Download WPML 1.8.3 from http://wordpress.org/extend/plugins/sitepress-multilingual-cms/download/

      Then, create a testing site with your DB and the recent WPML 2.0 and use that to debug the problems. E.g., don’t do debug work on your live site.

      If you have in-depth questions about WPML, you can purchase a support subscription and our developers will be happy to assist. Please note that this doesn’t cover debug work on your server. We can help with that too, but at a per-hour support rate.

  7. Hi,

    I’d have the comments appear in all the languages for the posts AND for PAGES POST.
    I download the pluging “Wmpl Comment Mergin”, it works really good but only for “normal” posts.
    It doesn’t work for “PAGE POST”.

    This is the code of the plugin:

    comment_ID - $b->comment_ID;
    }

    function merge_comments($comments, $post_ID) {
    // get all the languages for which this post exists
    $languages = icl_get_languages('skip_missing=1');
    foreach($languages as $l) {
    // in $comments are already the comments from the current language
    if(!$l['active']) {
    $otherID = icl_object_id($post_ID, 'post', false, $l['language_code']);
    $othercomments = get_comments( array('post_id' => $otherID, 'status' => 'approve', 'order' => 'ASC') );
    $comments = array_merge($comments, $othercomments);
    }
    }
    if ($languages) {
    // if we merged some comments in we need to reestablish an order
    usort($comments, 'sort_merged_comments');
    }
    return $comments;
    }

    function merge_count($count, $post_ID) {
    // get all the languages for which this post exists
    $languages = icl_get_languages('skip_missing=1');
    foreach($languages as $l) {
    // in $count is already the count from the current language
    if(!$l['active']) {
    $otherID = icl_object_id($post_ID, 'post', false, $l['language_code']);
    $otherpost = get_post($otherID);
    // increment comment count using translation post comment count.
    $count = $count + $otherpost->comment_count;
    }
    }
    return $count;
    }

    add_filter('comments_array', 'merge_comments', 100, 2);
    add_filter('get_comments_number', 'merge_count', 100, 2);

    I know this comment isn’t really related to this post but I’ve tried during 2 months to find the solution without success.
    I wrote the question on the blog of the plugin but I haven’t received answers.

    Do you know how to do?

    Thank you!

  8. I would like to know how the translator role is being called.

    I am using the Members plugin by Justin Tadlock and have set up a role for siteowners. Unlike Gravity Forms that adds a lot of visible capabilities to the Members menu, there is nothing on the capabilities of the WPML Translator role.

    I have tried to browse through the plugin files, but there are quite a few. I saw that it should show if the current user has the list_users capability, but my siteowners role has that capability and the translation menu (?page=sitepress-multilingual-cms/menu/translations-queue.php) doesn’t show.

    • WPML’s translator role is set privately and is not accessible to the Members plugin.

      You can assign users of any kind as translators. Most sites should have translators as subscribers, so that they can only translate and not edit anything else that’s not specifically assigned to them.

      If it was accessible, what would you assign to translators in the Members plugin?

  9. problem is that I switch OFF manage_options for the siteowners role.

    The reason for that is that there are so many things that siteowners potentially can ruin if they start murking around in settings.

    So instead of having to tell the siteowner “you cannot touch this, look at that, etc.”, now everything that I don’t want them to have access to is just not there.

    So I am looking for a way to still have manage_options disabled for the siteowners role, but at the same time do show the WPML translations menu (and that alone, because they have no business in WPML setup either)

    If it would be accessible, I would think of capabilities such as
    view_translation_menu (to be able to view the menu of translations)
    edit_translations (to be able to do translations)
    translate (to be able to do translations)
    assign_translations (to be able to assign translations to other users)
    etc.

    • I think that the simplest way would be to create another account with type ‘Subscriber’ and have them translate via that account. Everybody has more than one email and it would be pretty convenient to get the notifications about translation work separate than other admin issues.

      A subscribe account has access to nothing and WPML will give it the translator rights. It’s a bit of a hack, but would solve everything and requires no work from anyone.

      What do you think?

      • OK that works wonderful indeed!

        Now I just have to hope that the client likes it this way… 😉

        I personally think that ideally this “Translation interface” should be able to be added as a capability to a role to be used with for example the Members plugin.

        I think that the more WordPress is going to be used as full-blown CMS, the more developers will want to protect their work and give the client (user) only access to what is needed.
        In such cases using some kind of role manager plugin with the ability to add this translation interface is a must.
        Maybe something for you to think of for the future?

        PS what info do u need to have a website added to the showcase? next week my site is finally ready!

        • Role management should be in WP core. Until that happens, it’s very difficult to make things work together. Believe me, we’ve tried it.

          This is why we chose to implement it as we did. When you can create translator users as subscribers, you don’t run the risk of them doing anything they’re not supposed to do.

          And, if you’re interested, WPML 2.x will solve this even better. We’re going to offer an even improved translation tool with a translation memory, terminology management and visual editing. You’re not even going to need WP users for that. What you’re seeing now is the start, not the end.

          Did you and your client already take the poll?

          • Didn’t take the poll yet, will let ask the client next week and then fill it in on his behalf.

            Don’t get me wrong, the way you suggested to set it up works fine as far as I can see and you’re right that translators cannot mess up anything 😀

          • Hmmm I did encounter one problem to this solution.

            As the siteowners cannot see anything of WPML, they also cannot add an order to translate something and therefore the users with the subscriber role will never be able to translate anything, for the simple reason that the siteowners cannot assign any jobs to them…

            So it will have to be an administrator (or at least someone with manage_options capability) to create a translation job and send that to the translators. Then again, the subscriber role does not have the manage_options capability. So what does a subscriber have that a siteowner doesn’t have? Is it because I added the role of siteowner? Would it work if I edit one of the standard roles?

            Or I have to take a “standard” role and give that role only the manage_options capability and nothing else, but that means then yet another login. Unless it is a huge organization (which my client is not) people are not going to think this is very efficient…

            • The site owner cannot see anything in WPML, because the way you’ve limited access rights. Normally, admins can see WPML’s menu just fine.

              I’m not 100% sure how the roles plugin works. Maybe it’s worth for you to add some code in functions.php which will put some order into it and get everything as you want it.

              • Well that is basically what I asked in my initial question 🙂

                In the meantime I have tried to give the “standard” roles the same capabilities as what I have now for siteowners, and then indeed the Translation interface appears. So basically, as far as I can see, the Translation interface will only be enabled for the standard roles and those standard roles can be edited to add capabilities.

                But only the Translation interface appears, for now only the Administrator can assign translation jobs, no-one else can.

                Yup, and they also see lots of other stuff that I don’t want the users of this site to see.

                Justin once told me that his Members plugin only writes additional capabilities to the Roles and adds Roles to the table where those are registered.

                On the one hand I would love to add some code to my functions.php file to make this work! Do you know what I should add?

                On the other hand I think it is necessary to decide upfront whether to work with separate translators or not. Because if the siteowners are going to be their own translators, then the Translation interface is not necessary at all, as the siteowners are able to do the translations in the edit Post/Page screens anyway…

              • sorry sth went wrong so 2nd post (this one) is correct one…

                Well that is basically what I asked in my initial question 🙂

                In the meantime I have tried to give the “standard” roles the same capabilities as what I have now for siteowners, and then indeed the Translation interface appears. So basically, as far as I can see, the Translation interface will only be enabled for the standard roles and those standard roles can be edited to add capabilities.

                But only the Translation interface appears, for now only the Administrator can assign translation jobs, no-one else can.

                Normally, admins can see WPML’s menu just fine. Yup, and they also see lots of other stuff that I don’t want the users of this site to see.

                Justin once told me that his Members plugin only writes additional capabilities to the Roles and adds Roles to the table where those are registered.

                On the one hand I would love to add some code to my functions.php file to make this work! Do you know what I should add?

                On the other hand I think it is necessary to decide upfront whether to work with separate translators or not. Because if the siteowners are going to be their own translators, then the Translation interface is not necessary at all, as the siteowners are able to do the translations in the edit Post/Page screens anyway…

              • maybe I have to resort to deleting the SiteOwners role and just using the standard Administrator role.

                Do you know if it is possible to hack the dashboard with something like this:

                wp_get_current_user();
                if ( 1 == $current_user->ID ) {
                // is webmaster, show all dashboard menus
                } else {
                // other users, don't show all dashboard menus (with CSS if needed)
                }

  10. I use WordPress 3.0 and have updated from 1.8.2.1 to WPML 2.0

    Fatal error: Call to undefined function get_user_meta() in /var/www/www.domain.dk/www/wordpress/wp-content/plugins/sitepress-multilingual-cms/sitepress.php on line 28

        • After commenting line 28 so it reads:
          /* print_r(get_user_meta(3, $wpdb->prefix.’language_pairs’), 1); */
          it actually worked and the upgraded plugin could be activated.

          Now the database upgrade just froze halfway through saying:
          “Processing translations…”
          Luckily I could just “Resume upgrade” when I went back to the page.

          GREAT – thanks for the help!

    • I’ve just updated my WordPress 3.0 to 3.0.1. Afterwards when i tried to activate my WPML 2.0 i was prompted to update my database structure which i did. The plugin is now activated, but my content om my site is no longer intact. Parts of my frontpage is missing (widgets).

      I’m glad i did this on my copy and not my running site.

      I only remember updating my functions.php so that wordpress would no longer interfere with my posts (correcting and adding missing and stuff).

      • Do you want to create an account for us on your test site so that we can check what the problem might be? If so, Mihai will email you privately.

      • For some reason, my widget informations were emptyed during the database update. Readding the informations seems to get the frontpage running again.

        Seems to me if several settings in WPML have been changed (to default). The language footer was ticked of and every settings related.

        • We’re looking into this to see why widgets may disappear. Maybe it has something to do with the theme too.

          We haven’t seen this happening on our own sites. For instance, the sidebar widget here:
          http://www.icanlocalize.com/site/blog/

          Nor, on wpml.org.

          In your test site, can you check with the default theme?

          1) Go back to the DB backup and WPML 1.8.3.
          2) Switch to the default theme.
          3) Upgrade to WPML 2.0.

          See if the widgets still disappear.

          If they remain, it might have something to do with the way the theme works. We can still help with that but I’m trying to narrow down the problem to something that we can reproduce.

        • We tried to replicate this again on 4 different themes and didn’t manage.

          We’ll be happy to debug this further but we need a test case.

          What we need is:
          1) Site with WPML 1.8.3, before the upgrade.
          2) We will upgrade to 2.0 and see the widgets gone.

          Then, we can check how the theme and DB interact and what is causing this. For now, we can’t continue because we can’t reproduce.

          • I’m working on to restore the database. As soon as it’s ready I can give you access to my test blog.
            I believe that the problem might have occoured as the database upgrade froze halfway – as Christian Brix experienced. I was never prompted with the ability to resume the database upgrade.

            • I now have the test-site restored with a exact copy of my running site, you can contact me on my email for login details.

              • Ok, tried again to update the plugin from my restored 3.0.1 WP with 1.8.3 WPML. The database upgrade froze again: Finalizing upgrade…

                Afterwards i get the error:
                Warning: require() [function.require]: Unable to access /var/www/www.mysite.dk/www/wp-content/plugins/sitepress-multilingual-cms/inc/translation-management/translation-management.class.php in /var/www/www.mysite.dk/www/wp-content/plugins/sitepress-multilingual-cms/sitepress.php on line 93

                • From the error, you can see that PHP cannot find the top level file of the plugin.

                  You surely understand that if the top-level file was actually missing from the installation, we would have gotten a few more reports about it (around 25,000 by now).

                  Something is configured very strangely in your server. Maybe it’s doing some PHP caching that it shouldn’t do.

                  There’s no generic solution I can help with. This requires specific debug on your server.

                • Ok – thank you.
                  I did move my website to the root of my domain, as I wanned to see if this did help me out. I’ll just recheck my installation.

  11. Is there any way to download the old versions? I really need to make my blog work in other languages again and 2.0 does not work for me.

    For now it is completely messed up, so please allow for download of version 1.8.2 somehwere..

    THANKS!

    • I’m not sure that WPML is going to work right now with this permalink structure.

      Try setting it to something like:
      /%year%/%monthnum%/%postname%/

      • Mmkey. I think it would only be fair to aknowledge the fact that WPML requires the use of a specific permalink structure in the documentation. We are not the only users struggling with this issue, looking at the comments on your blog, it has been reported on multiple occasions for some time now. And please do not leave bug reports hanging for months if you know its a design issue. WPML is great, but this could have been handled better.

  12. Sorry to keep bugging you guys, but this upgrade have caused a NEW problem:

    When adding a translation (by going to Posts and clicking the “+” by the post I want to translate) and then clicking “Publish” I now end up with a completely blank page! (The URL is domainformywebsite.com/wp-admin/post.php

    This does not happen when just adding a new post (no matter what language is chosen), so that is why I expect that WPML causes this problem.

    Anybody else get this?

    • 1) Did you enable WPML’s debug mode to check for PHP / MySQL errors?
      2) Are you tracking JS errors in the browser?

      • 1) Sorry: I have been looking around for a while now to find the debug mode but have not suceeded. It does not seem to be at Support the link Troubleshooting from the support-page as far as I can tell..
        2) There are no javascript error on the blank page. If I click “Go” or whatever when at the blank page the list of Posts are shown and the translation have actually been saved..

          • I did not realize that I’m switching back and forth.. First I tried to upgrade, but did not succeed. Then I tried to upload the old zipped version from the internal plugin handler in WP, but it was not installed due to the fact that the old folders still existed. Then you came up with the solution to comment out line 28, and the upgrade succeeded (although freezing up first it allowed me to resume and complete).
            So I do not expect that I have any problems with the database or that I even got to do any switching back and forth..

            I go ahead and look at the debugging now. 🙂

            • Debugging reports this in the front end as well as admin:

              file_exists() [function.file-exists]: open_basedir restriction in effect. File(/customers/eeepc.dk/eeepc.dk/httpd.www/wp-content/plugins/subscribe-to-comments.php/wpml-compatibility-packages) is not within the allowed path(s): (/customers/eeepc.dk/eeepc.dk:/var/www/diagnostics:/usr/share/php) (2)
              File: /customers/eeepc.dk/eeepc.dk/httpd.www/wp-content/plugins/sitepress-multilingual-cms/inc/compatibility-packages/functions-packages.php
              Line: 169

              In the admin this error also occurs:

              Invalid argument supplied for foreach() (2)
              File: /customers/eeepc.dk/eeepc.dk/httpd.www/wp-content/plugins/sitepress-multilingual-cms/menu/dashboard-widget.php
              Line: 84

              Does this mean anything to you? 🙂

  13. Hi, the same error message appears whrn trying to upgrade database. If I look to the troubleshooting page there are some tables missing but apart of it my site appears to work properly without the database upgrade.

    Yes, there is not JS errprs, no PHP or mySQL errors appear at the top of page after activating WPLM debug mode and catching mySQL errors.

    Maybe you can tell me where is the database upgrade code so I can try to troubleshoot it by creating a special PHP page to run the upgrade?

  14. Hello! I installed wpml 2.0, but now all of my navigation has disappeared… This is with wp 3.0.1, on a live site…ouch…Any help to get?

  15. Is it because of WordPress 3.0 -> 3.0.1 or WPML 1.8.2.1 -> 2.0 that my links in string translations gets updated from a “nice looking link” to a “?page_id” link.

    If i create a link in the string translation like href=”/my/link” it changes to href=”?page_id=1231″

    This has never happend before, but I’m unsure if it’s because of the updated WordPress or WPML – maybe you guys knows the answer?

      • Hi Amir

        Any update on this matter?

        I’ve tried to rollback to WPML 1.8.2.1 but still with WP 3.0.1 – this dosnt seem to fix the “link updates”. Seems if it’s WP 3.0.1 that might have been updated in some way?

        The SQL was cleared so there shouldn’t have been any leftovers from WPML 2.0

        • It’s difficult to say what’s wrong there without debugging everything on your server.

          We’re done going through possible bugs, fixed a few small issues, but nothing explains the problems you were having.

          It may be interaction with other plugins, theme functions or a special setup on your server.

          If you like, we can review your DB and check what’s wrong. Our normal support subscriptions don’t cover this kind of work and we can do it on an hourly consultancy basis.

  16. Hi, we are big fans of WPML.

    I think that after updating the plugin the ‘database upgrade’ was interrupted. It was possible to ‘resume’, however it seems to be taking an inordinately long time, and the progress bar has extended well off the right side of the page.

    Using FF and Firebug console reports something like:
    {“error”:0,”completed”:0,”message”:”Starting the upgrade process…”,”step”:3418,”barWidth”:85450,”stop”:0}

    …every couple of seconds, but incrementing steps and barWidth. So it appears to be doing something – but has been doing this for 30 minutes or so.

    Any help greatly appreciated.

    P

    • The upgrade process creates several DB entries per post/page. If this is taking a very long time, it normally means that the DB or PHP are slow.

      Is your site responding quickly to visits when you’re in the WP Admin panel?

      • Hi Amir,

        Thanks for the prompt reply. Yes, all other other admin and site features are working as expected and seem to be returning pages in normal time. I’ve just started the upgrade process again to see if it makes any difference (maybe to leave it for a long time), but otherwise I am a bit stumped.

        I’ve not been able to progress past ‘Starting the upgrade process…’.

        Best regards, Paul

        • I should add that everything appears to be working correctly (i.e. old translations are still there and accessible via in-post links) – but the WP Admin still says:

          WPML requires database upgrade

          This normally takes a few seconds, but may last up to several minutes of very large databases.

          Resume Upgrade Process

          Do I have anything to worry about. I.e. will it continue to work as normal?

          P

          • It needs to be fixed. I don’t want to suggest what to change in the DB without being 100% sure what needs fixing.

            If you like, we can review your DB and check what’s wrong. Our normal support subscriptions don’t cover this kind of work and we can do it on an hourly consultancy basis.

  17. Actually I have discovered what seems to be a bug…
    The situation is the following:
    I have a multi-language website set up with WPML, and when I send pages to be translated to Italian, my pages disappear in my navigation menu if I call them with wp_list_pages. I deactivate the plugin and reactivate, then my pages reappear in my navigation, but the list of pages I sent to translate to my Italian translator also disappear in his translation list.

    This does not happen when I send posts to be translated, only when I send pages…very weird behavior of the plugin…

  18. The widget body is not displaying the translation I provided for the sidebar text.

    Here is how I reported it yesterday on http://code.google.com/p/wpml/issues/detail?id=28. (So far, no response and I’m cross posting here in the hope of finding a solution.)

    What steps will reproduce the problem?
    1. I go to WPML/String Translation
    2. Find the Widget Body for the one text widget in the 1 sidebar on http://savannahmedicalclinic.com
    3. Manually add the Spanish translation for the text, “Servicios de aborto y cuidados de la salud de la mujer – Savannah, Brunswick, Hinesville, Statesboro, Hilton Head and Beaufort, SC ” Select “Translation Compete” and save. (I also did this for the widget title)
    4. Test front end.

    What is the expected output?
    I expected the text widget to display in Spanish when the Spanish page and Spanish Widget title are displayed.

    What do you see instead?

    When the Spanish translation is selected, the widget title is translated, the text body is in English.

    What version of WPML and WordPress are you using?
    Using WPML 2.01 and WP 3.02,

    Can you also specify PHP
    and MySQL versions?

    The latest, the site is hosted on hostmonster.com.

    TIA!!!