DOCTYPE und HTML Grundgerüst bei Shortcode Ausgabe

Hallo Herr Teufel,

ich kann mir noch etwas wenig vorstellen, was hier genau passiert.
Haben Sie einen Screenshot, welcher zeigt, was Sie genau machen, damit der Fehler auftritt? K?nnen Sie das an [email protected] senden?

Mit freundlichen Grü?en

Dennis Schr?der`

@cleverreach43 gerne, Email ist raus! Sofern sich das Problem l?sen l?sst, poste ich hier gerne die L?sung für alle Anderen, falls noch jemand das Problem haben sollte.

Hallo Herr Teufel,

ich kann mir noch etwas wenig vorstellen, was hier genau passiert.
Haben Sie einen Screenshot, welcher zeigt, was Sie genau machen, damit der Fehler auftritt? K?nnen Sie das an [email protected] senden?

Mit freundlichen Grü?en

Dennis Schr?der`

So how has this been solved @ateufel ?
Because we have the exact same problem. Not sure when it started but all we did was update the plugin from time to time.

Alright, so the culprit is this:

public static function get_form_code( $form_html ) {

	// THIS IF-STATEMENT FAILS
	if ( ! class_exists( 'DOMDocument' ) ) {
		return $form_html;
	}

	$dom           = new \DOMDocument();
	$dom->encoding = 'utf-8';

	// and so on

If DOMDocument class doesn’t exist, output normal shortcode. If it does exist, output a full html document… as shortcode? I don’t get it to be honest.

What I did was to take the first line with return out of the if-statement and place it above it – because that’s all I needed from this function.

• This reply was modified 3 years ago by TBschen.
• This reply was modified 3 years ago by TBschen.
• This reply was modified 3 years ago by TBschen.
• This reply was modified 3 years ago by TBschen.

Hi! Unfortunately, this has not been resolved, but there is nothing we can do I guess. This is something that cleverreach would need to fix in their plugin. Whatever you override, it will be lost in the next Plugin update.

But it is really cool that you found the issue, maybe they can fix it with your information?

@ateufel
Oh I see. The topic is marked as solved, that’s why I thought that you’ve found a solution.
I hope that cleverreach can look into it. At least I know what to change if I update the plugin in the future and the issue appears again.

Hello,

our developers would like to check your case.
Could you send us your question to [email protected]?

Regards

Your CleverReach-Team`

@cleverreachsupportteam2
OK, mail sent.