Lee Hodson (VR51)

Just making sure you didn’t miss this over the Easter weekend. Do you have any feedback to provide?

Sounds great. Thank you.

I apologise for not replying sooner.

You can get it from https://www.ads-software.com/plugins/essential-addons-for-elementor-lite/advanced/.

Scroll to the bottom of the page where it reads ‘Downloads’.

Alternatively you can use WP Rollback.

The latest version broke one of my sites too.

I have a database backup that I created before I ran the search and replace. If I get time I’ll look through it for those wordpress@ addresses.

It’s always a good idea to create an email address on the server to match the addresses used in WordPress contact forms. I sometimes forget to do it. Should be added to the instructions for all contact forms.

Thanks for your help. If I have anything else to report I’ll add it here.

Thanks for your reply.

The interesting information is near the bottom of here. I have been able to fix it and I think I know where the fault was.

But First

Let’s define a few terms to make sure we know we are talking about the same items:

1) Admin Users, Backend Admin and (site) Administrators: the people in the website’s management team who are meant to receive notice of messages sent through the website.

2) Submitter: The site visitor who populates the form on the contact page in hope of being able to send a message to the Admin Users.

When a contact form is populated and the Submit button is clicked:

1) Admin Users receive a copy of the message
2) The message is recorded in the WordPress database, and
3) The web server logs the outbound email’s path with successful delivery notice received for each recipient.

But,

4) The Submitter does not receive the confirmation email, and
5) The web server does not record the outbound message.

As we can see from 1,2 and 3 the website does successfully send messages by email.

As we can see from 4 and 5, the only addressee to whom the message never arrives is the Submitter. It looks as though the form ignores the confirmation message.

I do receive other automatically triggered notices sent by the website such as security notifications and monthly reports.

The Interesting Stuff – The Fix, Possibly

I’ve switched SMTP plugin. The new one is Post SMTP (www.ads-software.com/plugins/post-smtp/). The test email sent via Post SMTP was successful. Still configured to use the default WordPress email system.

The test email from Post SMTP said it came from wordpress@[THE DOMAIN]. This address is not registered on the server. This made me wonder whether wordpress@ is in use elsewhere within the site’s database and it was.

I did a search and replace in the database using the Better Search and Replace plugin allowing GUIDs to be updated too. I replaced wordpress@ with another address.

Either the fault was fixed by,

A) Switching to the Post SMTP plugin, or
B) The search and replace to change wordpress@ with another contact address

Whichever it was, it worked.

The contact form now sends messages to both admin recipients configured in the form and the Submitter’s email address.

If you want to see the email logs captured by Post SMTP, let me know in a reply to this message and I will send to you through your website’s contact form.

Might I recommend you change the suggested SMTP plugin to Post SMTP.

Hello @thethemefoundry,

I can answer all of them for you.

1) Try this one skinandhairdoc.com/contact
2) I tried several addresses. One gmail address, 2 different private email addresses hosted at different domains. Made no difference to the outcome.
3) The error logs show no errors related to email, the plugin or the site at the times the tests were conducted. WP debug logs showed no errors for the emails.
4) The servers show no failures for outbound email. The form submitter’s email address does not feature in each server’s email logs.

Those answers offer little to work with, I know. I suspect the confirmation email that’s supposed to be sent to the message submitter’s email address is just not triggered. The forms otherwise work: the submitted message is received by the backend admin (so is logged) and is forwarded to the recipient addresses. We receive the message but the visitor’s own copy is not sent.leaves

@arabnas

I got the same problem in a website and the problem was from user profile disabled visual editor.

@amybartlett

For dummies (like me)….:) ….
1). GO TO PROFILE
2). UNCLICK DISABLE VISUAL EDITOR

And if it’s already unticked, tick it and save your profile settings then untick and save again.

Not sure why — though possibly a plugin update causes it — the visual editor setting is lost by the database so has to be reset.

Same problems. I use WPML as well.

1. The Yoast post meta widget disappears when the mouse cursor is focussed on it,
2. The Text/HTML side of the TinyMCE editor is not visible, and
3. WPML permalinks act up every time Yoast updates. I suspect Yoast disrupts the permalink structure on Yoast update. I use a separate WPML compatible plugin to remove the ‘category’ slug.

Hoped Yoast 9.2.1 would fix the problems in 9.2.0 but they still exist.

I’ve reinstalled 9.1 in all sites I manage.

You can use WP Rollback to easily revert to an older plugin version.

That means GADWP and Yoast need to have a chat about script conflicts. It’s possible one of them is not loading scripts the proper way i.e. register, enqueue and no-conflict mode.

I could check the code of each but have other things to do today. It’s something GADWP and Yoast need to resolve. As issues like this are common with GADWP I’d wager that GADWP contains the faulty script(s).

Thanks for writing back, Piet.

• This reply was modified 6 years, 1 month ago by Lee Hodson (VR51).

You are welcome.

I would look at the host side. The host might have adjusted the server software. I would also check whether a plugin has autoupdated. Both Wordfence and Yoast updated this past week, if you use them, for example.

Check your server error logs. Maybe also enable WP Debug (instructions for this are in the WordPress documentation).

Specific to GADWP. The last update to GADWP was last week, I think. It caused some of my sites to lose their GADWP authorisation token to connect with Google Analytics. One site I looked at today had out-of-memory errors caused by GADWP. The cause of those errors is probably different to your own errors. Neither one of these 2 errors caused the widget stats to load slowly.

Slow loading of the widget is, as I mentioned, normally caused by a script conflict or by a script being rate limited by the host.

• This reply was modified 6 years, 1 month ago by Lee Hodson (VR51).

I’m not the plugin developer so chiming in here only to add my experience with GADWP and 500 errors.

Are you using Cloudflare?

Which web host are you using?

The GADWP dashboard widget usually loads slowly when there is a script conflict with another plugin or when the scripts used by GADWP are blocked by your web host.

I recently had a problem with a web host that stopped working nicely with Cloudflare. The host’s security settings caused certain scripts to return 502 errors. This caused Cloudflare to determine the site to be offline or caused Cloudflare to let the site load but with reduced script based functionality. The outcome was that the GADWP dashboard widget loaded slowly, if at all.

Check for plugin conflicts. Test with Cloudflare disabled.

In honesty, GADWP has been an issue since ExactMetrics took over the plugin.

• This reply was modified 6 years, 1 month ago by Lee Hodson (VR51).

See whether switching from gmagick to imagick or to gd image processing PHP modules makes a difference. It usually does. I prefer to use imagick.

Another item to check is the compression rate set for image processing. WordPress lowered it to something silly like 82 in WP 4.5. If the theme has been updated and the correct image compression filter was set in the parent theme’s functions.php file then you’ll notice a drop in image quality (functions.php will have been overwritten).

Use either a plugin to add image quality settings (like this one in the WP repo) or use the filter in your child theme’s functions.php file.

This sets the quality to no compression i.e 100% quality / disables JPEG compression:

add_filter('jpeg_quality', function($arg){return 100;});

• This reply was modified 6 years, 3 months ago by Lee Hodson (VR51).
• This reply was modified 6 years, 3 months ago by Lee Hodson (VR51).

Still no answer?

This needs to be fixed in the core plugin.

Please adjust the plugin to change line 32 to disable the plugin’s frontend script output when administrators are previewing posts, thus:

if ( !empty( $uid ) && !empty( $template ) && !current_user_can('administrator') ) {

You might even change it to editor or implement a check at that line to prevent script output in page previews.

I’m not this plugin’s developer. Just want to let you know that Jetpack includes shortcodes for archive.org. You need to enable the Shortcodes Embed module (Settings > View all settings (bottom of page) > Shortcode Embeds.

Example usage:

Audio/Video

[archiveorg Experime1940]
[archiveorg https://archive.org/details/Experime1940 poster=https://archive.org/images/map.png]
[archiveorg id=Experime1940 width=640 height=480 autoplay=1]

Books

[archiveorg-book goodytwoshoes00newyiala]
[archiveorg-book https://www.archive.org/stream/goodytwoshoes00newyiala]
[archiveorg id=goodytwoshoes00newyiala width=480 height=430]

Hope this helps.