Warnings related to WPML in blog categories pages

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,

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

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

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, 10 months ago by p_castro.

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

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

Thanks Andy!

Regards,
Diego