Thanks Andy!

Regards,
Diego

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 @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

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

Hey Elliott,

Thanks for letting me know!

Regards,
Diego

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

Hi,

I’ve just found the solution in another thread, Adding a header widget to the logo container (sorry, yesterday I could not find it :)), so the solution consists in adding the following piece of code to functions.php:

add_action( 'ava_before_bottom_main_menu', 'enfold_customization_header_widget_area' );
function enfold_customization_header_widget_area() {
	dynamic_sidebar( 'header' );
}

I believe this solution should be added to the guide Enfold Theme Documentation | Adding a widget area to the header, given the fact that it is absolutely necessary for those users who are pursuing to keep the widget area aligned to the right of the container of the header – as opposed to the header itself – specially for viewports wider than 1310px. Obviously, custom CSS will be needed, for example:

#header_main .inner-container .widget {
    position: absolute;
    right: 0;
    padding: 0;
}

Regards,
Diego

• This reply was modified 9 years ago by p_castro.

Hi Andy,

By saying:

it is working as expected:

and

The problem is that you are first calling a text block element and then calling a separator element. Obvious that things get messed up

are you implying that Enfold’s users should never use the shortcode generator present on the Visual Editor when using the ‘Advanced Layout Editor’ (‘Avia Layout Builder’)? Really :)?

In one word, are you saying that I am doing something wrong when I am simply using an element present in Enfold’s UI (shortcode generator)?

Sorry but If that shortcode does not work properly nested within the Text Block shortcode then, please, remove it from the shortcode generator, do not offer it misleading the user. BTW is this incompatibility explained in Enfold’s documentation?

Thank you.

Best Regards,
Diego

• This reply was modified 9 years, 5 months ago by p_castro.

Hi,

I needed this to be solved ASAP so I have been debugging it myself.

The origin of the problem
I have found out that the problem is caused by ENFOLD’s separator shortcode (default), when it is placed before de list, then the marker (bullet point) of the first list item gets misaligned (in webkit browsers like Chrome (OS X) and Safari).

The reason why this is happening is because of ENFOLD’s class .hr and its property float: left;

Possible Solutions
I came out with two solutions. I haven’t had the time to thoroughly test them in order to detect some possible undesirable secondary effects, so I would like to ask Kriesi’s team to do it as I am worried about harming other elements of the theme like navigation menus or other types of separators.

Solution 1

main ul, main ol {
    clear: left;
}

Solution 2

.hr {
    float: none;
}

In case you want to reproduce the issue here you have the code I used on my page:

[av_hr class='default' height='50' shadow='no-shadow' position='center' custom_border='av-border-thin' custom_width='50px' custom_border_color='' custom_margin_top='30px' custom_margin_bottom='30px' icon_select='yes' custom_icon_color='' icon='ue808' font='entypo-fontello'] <ul> <li>Measures:</li> <li>Materials:</li> <li>Dyes:</li> <li>Condition:</li> </ul>

Please, can someone confirm the best solution in order to minimize the possible adverse effects in other elements of the theme?

Thanks!

Best Regards
Diego

• This reply was modified 9 years, 5 months ago by p_castro.

Hi!

Maintenance mode deactivated.

Cheers!

HI,

As I have not received any response yet I am not quite sure if I made clear what I need, perhaps my previous comment was a bit confusing.

The point is that I need to keep Enfold’s default styling list-style: disc outside;

Employing list-style: disc inside; is not a solution for me, I mentioned it just in case it helps to understand what is going on.

So please, does anybody have a solution to solve the issue?

Thanks.

Best Regards,

Diego

Hi!

OK, thanks anyway.

Cheers!
Diego

Hi Yigit,

Chrome version 43.0.2357.81 (64-bit) running on OS X 10.10.3 (14D136)

Regards,
Diego