Viewing 25 posts - 1 through 25 (of 25 total)
  • Author
    Posts
  • #535333

    Hi,

    I am getting the following warnings on a particular blog category page:

    Warning: Illegal offset type in isset or empty in /homepages/30/d529233942/htdocs/cloracion_salina_es/sitio/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 5504

    Warning: Illegal offset type in isset or empty in /homepages/30/d529233942/htdocs/cloracion_salina_es/sitio/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 5508

    Warning: Illegal offset type in isset or empty in /homepages/30/d529233942/htdocs/cloracion_salina_es/sitio/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 5504

    Warning: Illegal offset type in isset or empty in /homepages/30/d529233942/htdocs/cloracion_salina_es/sitio/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 5508

    Warning: Illegal offset type in isset or empty in /homepages/30/d529233942/htdocs/cloracion_salina_es/sitio/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 5504

    Warning: Illegal offset type in isset or empty in /homepages/30/d529233942/htdocs/cloracion_salina_es/sitio/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php on line 5508

    Note: in the other categories pages I get similar warnings.

    Could you please have a look at it? I enclose a link to the page in the private content area.

    #535686

    Hey Diego!

    Looks like it has something to do with the WPML plugin. Is the plugin updated? Try deactivating all of your other plugins.

    I found this which may help, https://wpml.org/forums/topic/warning-illegal-offset-type-in-isset-or-empty-in-sitepressclassphp/.

    Best regards,
    Elliott

    #535803

    Hey Elliot,

    Of course, before posting my first message, I made sure:

    • WPML, Enfold and WP were all updated
    • I disable all plugins, except WPML
    • I deactivated my child theme

    I have found out that the problem just occurs when, in Enfold Settings > Blog Layout (tab) >Blog Layout (the dropdown menu), the Grid Layout is chosen. I don’t get the warnings if I chose any of the other blog layouts (Multi Author Blog, Single Author small previewPic, Single Author big previewPic, etc).

    My conclusion is that there must be something in Enfold’s Grid Layout function that is colliding with WPML.

    Please, let me know your thoughts about the matter.

    Thanks!

    Best Regards,
    Diego

    #535857

    Hi!

    Can you provide us your backend access, together with the page you run the issue, so we can give it a look?

    Thanks a lot

    Regards,
    Basilis

    #535893

    Hi Basilis,

    I enclose the login details and page in the following private message.

    Thanks!

    Best regards,
    Diego

    #536878

    Got the same problem on http://www.schnell-medical.ch/2015/11/
    When I change to non “Raster-Ansicht” it works fine.

    Is there a solution already?

    Thanks in advance!

    Micha

    #538884

    Hey!

    you are using an old version of WPML. Please update to WPML v3.3: https://wpml.org/version/wpml-3-3/

    Best regards,
    Andy

    #539076

    Hey Andy!

    I posted my first message on November 13th, i.e., 6 days ago, while the new version of WPML was released yesterday, November 18th. Your colleague Basilis asked me for my credentials on the 14th and I gave them to him but never got a reply up till now.

    There is at least one more user that has been experiencing the issue. I would appreciate if you could confirm if it has been caused by a bug (either Enfold’s or WPML’s). Also it would be great if you could check out if updating to WPML will solve the issue, perhaps performing some testing on your side.

    Thanks!

    Best regards,

    #539079

    Hey Andy!

    I would like to add to my previous post that finally I updated to WPML 3.3 and the warnings persist. It has been 6 days since I opened this thread, 3 days ago another user reported the same problem but it seems Enfold’s team has not taken any action to solve it.

    Could you please test it on your side and provide us with a solution?

    Thanks.

    Best regards,
    Diego

    #539080

    I can just relate to p_castro, Andy.

    Can you confirm that the issue will not longer be there when updating to WPML 3.3 because it means a lot of testing again on our site and maybe troubleshooting with some new issues with the newer version?!

    Thanks and best regards from Switzerland

    #541634

    Hey!

    I did some testings on my own installation and followed your steps:

    I have found out that the problem just occurs when, in Enfold Settings > Blog Layout (tab) >Blog Layout (the dropdown menu), the Grid Layout is chosen.

    I can’t reproduce the issue. There are no warning messages for me at all.

    Try to delete all theme files via FTP completely and afterwards get a fresh copy from your themeforest account. Maybe there are some corrupted files. Make sure to deactivate ALL plugins but “WPML Multilingual CMS”.

    Regards,
    Andy

    #541649

    Hey Andy,

    I was wondering, on your instalation, are you testing on a category page? I mean like mydomain.com/category/a_particular_category.

    Thanks!

    Regards,
    Diego

    #562246

    Hi p_castro I am suffering the same problem, have you solved it?

    #562529

    Hi @alebrandcare,

    I am afraid I have not solved it yet although it would be more precise to say that Kriesi’s team has not solved the bug, they have not even been able to reproduce the issue, apparently.

    I followed Andy’s advice:

    Try to delete all theme files via FTP completely and afterwards get a fresh copy from your themeforest account. Maybe there are some corrupted files. Make sure to deactivate ALL plugins but “WPML Multilingual CMS”.

    …but the issue is still there.

    I am on the latest versions of Enfold and WPML but I can confirm the issue has been there for the rest of the versions in between.

    Andy never replied to my previous message (November, 24). On his last message he said he had done some testings but he never shared an url to let us check.

    I would really appreciate from Kriesi’s team more timely responses and transparency when they claim they are performing testings and can not replicate the issue. I gave them credentials of my install with administrative privileges, I can see they never used them.

    At least three users have reported this issue and none of us have confirmed that it has been solved.

    I suppose you (@alebrandcare) and @mkellenberger have something to say about how this issue is being handled in the forum.

    Best regards,
    Diego

    #562534

    Hi p_castro check here: https://wpml.org/forums/topic/warning-illegal-offset-type-in-isset-or-empty-in-2/#post-667754
    It is a common problem and the only solution provided is oscuring the php warning.
    I’ll check Google and I found maybe 30 messages that asks Kriesi support the same thing. So or they are using a worst knowledge base because I thinkg it’s really impossible that they can ignore such an issue reported by so many users, or they don’t want to solve the problem and the give obscure replies to make sure that a user will be tired of asking.

    I have reported another problem mansory/portfolio related (the pagination do not work, the category filter do not work) and the same… They do not solve nothing, they said as usual they cannot found the problem, they said I have to disable all the plugins, etc, etc…
    But Google is my friend: https://kriesi.at/support/topic/problem-with-portfolio-filtering-paging/
    The problem is known since 2013, it is a classic example of bad design rather than an error. It would be easier to give me that link and tell me that I had to accept the issue insted giving me obscure and superficial replies. So I’ve lost 20 hours of debugging and the only solution I found is to rewrite all the code!

    Anyway the php warning problem is related to blog grid, if you check archive.php you can see:

    $atts = array(
    ‘type’ => ‘grid’,
    ‘items’ => get_option(‘posts_per_page’),
    ‘columns’ => 3,
    ‘class’ => ‘avia-builder-el-no-sibling’,
    ‘paginate’ => ‘yes’,
    ‘use_main_query_pagination’ => ‘yes’,
    ‘custom_query’ => array( ‘post__in’=>$post_ids, ‘post_type’=>get_post_types() )
    );
    $blog = new avia_post_slider($atts);
    $blog->query_entries();
    echo “<div class=’entry-content-wrapper’>”.$blog->html().”</div>”;

    the query $blog->query_entries(); (raw 60) gives an error because the post_type “grid” is not properly created as usual.
    I am not very keen in php, but I think that is the problem…

    Please reply to me if you have red, because I think Kriesi will cancel my comment… :)

    #562824

    Hi @alebrandcare,

    Thanks for such a detailed response.

    You are right, there are quite a few threads in this forum related to this issue, with plenty of users reporting that they are experiencing it:

    Having gone through those threads, some facts have arisen about the members of Kriesi’s team that have participated on them:

    • At least they know about the issue since September 2014 (more than a year ago), as it has been repeatedly reported by users since then.
    • Either if the bug is on Enfold side or the WordPress Multilingual Plugin side, they (Kriesi’s team) have not fixed their code to solve the problem nor they have managed to get a fix from the WPML compatibility team.
    • They have only provide the users with instructions to obscure (hide) the warning messages, e.i. they have not given any real solution.

    Given those previously mentioned facts, I am wondering:

    • How is it possible that none of the three members of Kriesi’s team on this thread have informed us straightaway that it was a known issue? Notice that all of them have participated on those other threads related to the same issue.
    • How can be that @Andy has not been able to reproduce the issue?

    It is a pity how Enfold, an excellent product, can be spoilt by a support service that is not up to the task.

    Please, Kriesi’s team, if you are not willing to provide us with solutions for certain matters, the least you can do is be open and tell us so we do not waste our time waiting for a solution.

    I hope that, despite my harsh words, a moderator will give a reasonable explanation to what has occurred on this thread.

    Thanks!

    Best regards,
    Diego

    • This reply was modified 8 years, 11 months ago by p_castro.
    #564169

    Hey!

    I checked your backend and the page in private content but can’t see any warning messages. Can you provide us a precise link please? where we can see the issue?
    I will tag this thread, so you will get a faster response from now.

    Regards,
    Andy

    #564217

    Here you are: http://www.alessandracolucci.com/enfold/category/brand/
    I think my friend p_castro has solved by this: https://wpml.org/forums/topic/warning-illegal-offset-type-in-isset-or-empty-in-2/#post-667754
    But Andy, I am sorry that is not enough, that is an error, and it is tiring and boring that every time we, users, have to repeat and repeat everytime the same things…

    #564219

    Hi!

    thanks for the links. Glad that there is a workaround which kind of “solves” the issue. As you can imagine Kriesi is very busy and he has lots of new features, bug fixes etc to do. If there is a already a workaround for an issue, then Kriesi need to spend his time for things with higher priority. Hopefully he can implement a permanent fix in the future.

    Best regards,
    Andy

    #564895

    Hi @Andy,

    You can’t see any warning messages anymore because I added some code in wp-config.php in order to hide them. There are at least two possible ways to hide the warnings that worked in my case, one recommended for local testing and staging installs and another one for live websites. Just replace the line define('WP_DEBUG', true); or define('WP_DEBUG', false);. Both of them allow you to keep a log file of warnings and errors. Here you have:

    For local testing and staging installs (it will save the warning and errors in wp-content/debug.log, it is safer if the file is manually created):

    define('WP_DEBUG', true);
    define('WP_DEBUG_LOG', true);
    define('WP_DEBUG_DISPLAY', false);

    For live websites (it will save the warning and errors in wp-content/phperrors.log, the path and file name can be changed):

    define('WP_DEBUG', false);
    
    @ini_set('log_errors','On'); 
    @ini_set('display_errors','Off'); 
    @ini_set('error_log','wp-content/phperrors.log'); // path to server-writable log file


    @alebrandcare
    , the solution that you pointed out, provided by the WPML team in https://wpml.org/forums/topic/warning-illegal-offset-type-in-isset-or-empty-in-2/#post-667754, works fine aswell, but just as long as WP_DEBUG is set to false. I still prefer the solutions I used as they allow me to keep a log file with all the warnings and errors.


    @Andy
    could you please tell Kriesi that:

    • This is a tricky bug that could easily pass undetected by developers if they don’t thoroughly test their sites and it is not nice to see all those warning messages piling up
    • To improve the knowledge base in order to achieve much better support in this forum so we don’t have to waste our time in such long threads on issues that have already been known for such a long time.

    Thanks!

    Best regards,
    Diego

    #565404

    Hi!

    I will tell him, but I can imagine his answer:
    It’s not a bug, as the theme functions well. The only “bug” is that there are any error messages appearing although they don’t do any harm and if they don’t do any harm it’s not a real bug and the workaround mentioned should be sufficient enough in this case. Time and energy is limited and we need to focus on the real bugs.

    However, I will follow you suggestion and I am going to report it to Kriesi. Let’s hope he can find a fix for this.

    Regards,
    Andy

    #565423

    Hi,

    If this issue is not going to be fixed soon I think Kriesi should include –in the documentation of the theme– the description of the problem and the workaround to hide the warning messages, something like:

    “If you are using the WPML plugin and you select the option Grid Layout in Enfold Settings > Blog Layout (tab) >Blog Layout then include the following code in your wp-config.php file in order to avoid warning messages on category pages:…”

    Thanks!

    Best regards,
    Diego

    #565474

    Hey!

    thanks for the suggestion, I will forward this to one of our team members who asked me once for any new ideas for a new documentation.

    Regards,
    Andy

    #565481

    Thanks Andy!

    Regards,
    Diego

    #565496

    Hi!

    Let us know in a new ticket if you have some more questions related to the theme. We are happy to assist you.

    Regards,
    Andy

Viewing 25 posts - 1 through 25 (of 25 total)
  • You must be logged in to reply to this topic.