Hi,

sure, do as you like!
That was exactly the idea why I’ve posted it.

I hope your holiday celebrations are full of lots of fun, surprises, and magic!

Cheers,
Jürgen

Dear Rikard,

perfect, works like a charm!
The line will be included in the next version, I assume!?

Thanks for taking care and thanks to the dev team for the solution!
Best,
Jürgen

Hi Nikko,
always at your disposal. :-)

Question on the side: how about documentation of the icon grid feature? Couldn’t find any, everything about it is here in the forum.

Best,
Jürgen

Hey Nikko,

see private area.

best, Jürgen

Dear Ismael,

very strange!

For sure I can provide site access, please see the details in the `private section.

Strangely, one cannot edit the functions.php file of my child theme from the admin panel via “Appearance > Editor”.
So I have created a custom field named ‘fix_region_param’. In conjunction with a corresponding function, this works as a switch (whether you want to fix the error or not). The function looks like this:

// fix HTML entity conversion error
function dawn_content_filter( $content ) {
	global $post;

	$fixIt = get_post_meta($post->ID, 'fix_region_param', 'true');
	if($fixIt='true')
    		$content = str_replace( 'amazon®ion=', 'amazon&region=', $content );

    	return $content;
}
add_filter( 'the_content', 'dawn_content_filter', 1 );

By editing the value of ‘fix_region_param’ on the page in question, you can select to fix the misbehaviour or not (true/false).
Currently the switch is set to ‘true’, so everything works properly. If you set it to false, you can see the erroneous output on the page.
PLEASE DO NOT FORGET TO SET IT TO TRUE AGAIN!!!

To reproduce the error in the editor, just do the following:

• Open the page in the editor
• Edit any text block and save it (no need to change anything)
• Update the page

The iframe in the text block you’ve just edited will still look good. If you scroll down to another text block containing an iframe, you will just see some dummy content in the iframe (content delivered by amzn because of now invalid src link).

If you edit a text block with such a “broken” iframe, that one will look good again.
Now update the page again (so it reloads in the editor). Result: the others will be broken now!

In fact, you have to touch all the text blocks containing iframes before saving the page. That’s the only way to make them all look good when you open the editor next time.

Best regards and many thanks in advance for your help.

Hey Mike,

the problem is *not* the stripping in visual mode, but in text mode.
Anyhow, thanks for pointing in the right direction!
I’ve learned that my “problem” was basically caused by TinyMCE (and NOT Enfold!).

Unfortunately the link you’ve posted is not what I would call a “clean solution”.
Read about using the ‘entities’ element in tiny_mce_before_init here. As you can see, you always have to add value *pairs* (consisting of the character code and the character name).

According to the TinyMCE spec, ‘entity_encoding’ must also be set to ‘named’ to show the defined names.
This is the TinyMCE default, but apparently that gets changed to ‘raw’ somewhere before my tiny_mce_before_init filter function get’s called.
So I ended up with the following code:

/* Show ­ and   in TinyMCE editor's text mode */
function override_mce_options($initArray) {
	// Add entities to the default array (nbsp, shy) 
	$initArray['entities'] .= ',160,nbsp,173,shy'; 
	$initArray['entity_encoding'] = 'named';

	return $initArray; 
}
add_filter('tiny_mce_before_init', 'override_mce_options');

As the comment states, the code shows the two non-printable characters ‘soft hyphen’ and ‘non-breaking space’ as their corresponding HTML entities ‘­’, resp. ‘ ’ in the editor’s text mode.

My suggestion ist to display all non-printable characters (think of en space, em space, thin space, …) as their corresponding HTML entities by default: that’s the only chance to identify them again after one has inserted them.

Best regards,
Jürgen

Don’t worry, I’ve disabled logging of PHP notices at that particular line.
So just solve it whenever it suits you guys.

Removing all logs by a cron job is not a good idea: normally you want to see the errors (and notices, since there you’ll find e.g. hints of deprecated PHP functions being used, which might be not available in a future version) on the page.

Best,
Jürgen

Hi Basilis,

we’re using PHP 7.1.27.

Regards,
Jürgen

Excellent idea! :-)
THX!
Jürgen

Regarding the custom styles issue, it might be a good idea to mention, that the developer options must be switched on in the layout builder. ;-)
Since I’ve changed that, it remembers the custom class.