Sam Bull

It explicitly says on the dashboard:

Elementor requires WordPress version 5.2+.

Why would any of the above suddenly make it work?

I just reverted the extension for now.

Hmm, looking back at my history, it looks like it was a different theme I reported this issue on. My client must have changed themes at some point.

Exactly the same issue and solution though.

Hmm, that’s weird. Logically, you should be unable to display any page on the frontend using this theme, as that header.php is going to hit that error every time.

You can check the documentation and see that the function was only introduced in 5.2, so there is no way it should work in older releases:
https://developer.www.ads-software.com/reference/functions/wp_body_open/

1.7.7 appears to be the last working version. All later versions need to be fixed, or their requires field updated to WP 5.2+.

Any ideas at all?

Form

<p>Full Name (required)<br />
    [text* your-name] </p>
<p>Email (required)<br />
    [email* your-email] </p>
<p>Phone Number<br />
    [text Contact-Number]</p>
<p>Subject<br />
    [text your-subject] </p>
<p>Message<br />
    [textarea your-message] </p>
<p> Attach a file...<br />
    [file  your-file limit:2mb] </p>
[checkbox opt-in "Subscribe to our newsletter"]
<p>[submit "Send"]</p>

Mail
To: jobs@<client-domain>
From: [your-name] <jobs@<client-domain>>
Subject: Get in touch contact form <client-name> “[your-subject]”
Body:

From: [your-name] <[your-email]>
Subject: [your-subject]
Phone Number: [Contact-Number]
Message Body:
[your-message]

-- 
This e-mail was sent from a contact form on <client-name> (https://<client-domain>)

Attachments: [your-file][your-another-file]

Mail-2
From: [your-email]
To: <client-name> <jobs@<client-domain>>
Subject: Thank You For Contacting <client-name>
Body:

<h1 style="font-family: 'Cooper Black', sans-serif;"><a style="text-decoration: none;" href="https://<client-domain>/"><strong><span style="color: #000000;"><client-name></span><span style="color: #ff0080;">.</span></strong></a></h1>
Thank you for your message, a member of the team will be in touch shortly.</strong></a> 
<br>
If you haven't already, you may wish to <span style="color: #ff0080;"><a style="color: #ff0080;" href="https://<client-domain>/newsletter-signup/">subscribe to our newsletter</a></span> for regular digital marketing news, job seeking help and recruitment tips! 

<br><br/>We look forward to working with you and wish you continued success in the meantime.

<h4><b><span style="color: #ff0080;"><a style="color: #ff0080; text-decoration: none;" href="https://uk.linkedin.com/in/<client-ceo>"><client-ceo></a></span>, </b>Director of<b> <span style="color: #000000;"><client-name></span><span style="color: #ff0080;">.</span></b></h4>

<br>
<br>
-
This mail is sent via the contact form on <span style="color: #ff0080;"><a style="color: #ff0080;" href="https://<client-domain>/">https://<client-domain></a></span>

Use HTML content type

• This reply was modified 5 years, 4 months ago by Sam Bull.

Thanks for highlighting that. No idea why that’s needed on your install and not mine, but I’ve updated the plugin.

If you could upgrade the plugin and double check that everything is working, that would be great.

If I understand the Google translation of your message:

Good to know everything is working well for you.

The plugin does not get updated often, as it is very small and simple, and therefore very rarely requires changing.

Rest assured, that I am still using the plugin and pagespeed myself, and will update the plugin if the need arises.

That page just shows:

You don’t have any WordPress sites yet.

https://wordpress.com/themes/penscratch-2/?ref=login-to-download

With or without the ref=

Is there a reason it’s not available in the normal WordPress repository? I didn’t know it existed. Also, all I see is:

Login to WordPress.com to download Penscratch 2 for your self-hosted WordPress site.

While I am logged in to the site.

I’ve added support for Basic Auth. Waiting for the author to accept the pull request. You can find the change here: https://github.com/pdclark/uploads-by-proxy/pull/6

The issue is here, with links to the pull requests. Each pull request includes an explanation as to what went wrong.

https://github.com/pdclark/uploads-by-proxy/issues/4

I’ve fixed the issues we were having. They were not to do with the WordPress version though, but problems with the way it expected our local environment to be set up. I’ve submitted pull requests for the fixes, waiting for the author to respond.