[Resolved] Blog not displayed with abundance and woommerce

Home Support English Support [Resolved] Blog not displayed with abundance and woommerce

This topic contains 11 replies, has 3 voices, and was last updated by  Jussi 2 weeks, 4 days ago. The support staff assigned to this topic is Adriano.

Viewing 12 posts - 1 through 12 (of 12 total)
Author Posts
Author Posts
January 3, 2013 at 12:14 pm #94020

Cedric

Hi,
I using the latest version of abundance theme and my the site is translated in FR and NL and I'm using those plug-ins:

- wordpress 3.5
- woocommerce 1.6.5.2
- WPML Multilingual CMS 2.6.1
- WPML String Translation 1.5.1
- WPML Translation Management 1.4.1
- WooCommerce Multilingual 1.3
- WPML Media 1.2.1

The problem is that the blog is no more displayed. Here is the error:

Fatal error: Cannot use object of type WP_Error as array in /customers/3/f/0/laboul.com/httpd.www/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 5199

Here is the blog:
http://www.laboul.com/blog/

thx for your help.

ps: fyi, I already posted this same bug here, http://wpml.org/forums/topic/blog-not-displayed-with-abundance-and-woommerce/.
Seems again the same problem.

January 3, 2013 at 12:36 pm #94025

Adriano

Dear Cedric,

All WPML plugins and addons are updated with the latest version? WordPress is also updated?

January 3, 2013 at 1:00 pm #94030

Cedric

I didn't realized there where an update available for wpml. So now, wpml is up to date and here is the version of plugins I'm using:

- wordpress 3.5
- woocommerce 1.6.6
- WPML Multilingual CMS 2.6.3
- WPML String Translation 1.5.3
- WPML Translation Management 1.4.3
- WooCommerce Multilingual 1.4
- WPML Media 1.2.2

Still having the issue:

Fatal error: Cannot use object of type WP_Error as array in /customers/3/f/0/laboul.com/httpd.www/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 5203

January 3, 2013 at 1:08 pm #94032

Adriano

Hi Cedric,

Please tell me what is on line 5203 of your file sitepress.class.php

January 3, 2013 at 1:14 pm #94036

Cedric

the line 5203 is the 'if'

function get_terms_filter($terms){
        foreach($terms as $k=>$v){
            if(isset($terms[$k]->name)) $terms[$k]->name = $this->the_category_name_filter($terms[$k]->name);
        }
        return $terms;
    }
January 3, 2013 at 1:27 pm #94039

Adriano

Hi Cedric,

I will send you an email to request some further information that will help me troubleshoot the issue further.

January 3, 2013 at 1:38 pm #94043

Cedric

Ok, thx, you can send it to martin attt laboul dottt com

January 3, 2013 at 5:18 pm #94099

Adriano

Hi Cedric,

Abundance isn't compatible with WPML, there are some compatibility issues. Can you please try to involve the theme author to our go global program –http://wpml.org/documentation/theme-compatibility/go-global-program/ . Because not much we can do now, all fixes/changes should go in their side.

January 7, 2013 at 1:38 pm #94646

Cedric

I know there is some compatibility issue bug this is almost the same bug here:

http://wpml.org/forums/topic/blog-not-displayed-with-abundance-and-woommerce/.

and it has been resolved by your support.

You can really not help me on this?

thx

January 7, 2013 at 2:12 pm #94652

Cedric

Thx to Harshad of this forum, the solution was to add a "if" statement before the foreach:

function get_terms_filter($terms){
      if(is_array($terms)){
        foreach($terms as $k=>$v){

            if(isset($terms[$k]->name)) $terms[$k]->name = $this->the_category_name_filter($terms[$k]->name);

        }
        }
        return $terms;

    }
January 7, 2013 at 2:48 pm #94659

Adriano

I will talk to Harshad.

May 31, 2013 at 10:17 am #131799

Jussi

I had exactly the same problem and Cedric's solutions fixed it for me.

I encountered this problem when I translated Woocommerce attribute.

My setup:
WPML 2.8.2
WPML String Translation: 1.7.1
WPML Translation Management: 1.6.1
WooCommerce Multilingual: 2.3.2
WooCommerce: 2.0.10

Viewing 12 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic.