cinderalla

Thank you, John!

Hi Peter (@yscik8),

Changing the mailer type to PHPMailer does not resolve the issue and the email log says “Failed: SMTP Error: Could not authenticate.”

When the mailer type is set to PostSMTP, the email log says “Failed: This email has empty body”. However, when you click to view the email in the PostSMTP email log, the email displays (even though the notification email was not sent).

It appears that this is a known issue as per this support thread: https://www.ads-software.com/support/topic/notification-emails-not-being-sent-are-in-plain-text-but-rich-text-selected/. The links in that thread to a fix are broken. Could you supply a working link to the fix?

Hi @stevejburge

The issue started on a new website that was duplicated from another WordPress site.

I checked the Capabilities screen, and that was the problem. Only one of the capabilities was turned on for the Administrator role. I turned them all on, and all works as expected ??

Thank you !

My mistake. It was a widget. This is what we used to display the list:

$instance = array( 'title' => '', 'limit' => '3' );  
      the_widget ( 'Tribe__Events__List_Widget', $instance ); 

That no longer displays anything.

Hi Pods Developers!

Just wondering if you have any idea when you’ll be able to resolve this issue? It’s become quite an urgent issue, because any time a new attachment is added to a media item, all the existing attachments are deleted.

Thank you so much for your time!

@webbistro

The media categories element/widget is missing the “Add New Category” link.

That can be ignored, since the link was missing from the duplicated category list/box.

An update on this issue is that when I reverted back to the current version (2.8.9), the categories now show in two positions on the media edit screen: at the bottom of the page and in the sidebar.

Hi @stevejburge,

There are no errors in the site log or with wp_debug enabled. Were you able to test with a role with spaces in it?

I wasn’t able to add one like that via the WP Admin interface, so it must have been added to the database with the spaces somehow. Strange is that we were able to edit the role with the spaces before version 2.3.3.

– Can you confirm the error exists in 2.3.4?

Yes, it does happen in 2.3.4

– Does it happen with new roles?

No, it doesn’t happen. When you create a role with spaces, the spaces are replaced with underscores when you save it.

Hi @stevejburge,

I’ve found that the problem started in version 2.3.3.

Steps in the previous version 2.3.2:

• Go to WP Admin > Capabilities > Roles
• Click on the role with a space in the name. (This takes you to the edit screen.)
• Click to turn on “Edit Others” capability.
• Save Changes
• See the messsage “Settings saved.”

Steps in version 2.3.3 and current development version:

• Click on the same role as above, with a space in the name.
• Expect to see the edit screen with the capabilities.
• Instead, see the message “The selected role is not editable.” and no capabilities.
• Go back to the Roles page and mouse-over the role > click on Delete.
• See warning message “Are you sure you want to delete this role?”
• Click on OK, but the role will not delete.

Hoping that there is a way for you to make the role work again with the spaces. Thank you for your time.

• This reply was modified 2 years, 9 months ago by cinderalla.

Thanks for your quick response, Steve.

This problem is not just on one site, it’s on hundreds of our websites using the custom role.

Are you saying you will not take a look at your plugin to see how a role could not be editable and be stored without spaces in the role_name?

Awesome!

@yehudah Thanks for your suggestion. I wasn’t able to get it to work using “new PostmanWpMail()”. However, it turns out that wp_mail does work. I was able to get the notifications to send via Post SMTP with just wp_mail() in my function.

Thank you @jasonlazarus ! That solved it for us as well.

Agree with @kvvz – Wondering what @takayukister position is…

Not sure if this could help explain, but when a user is logged into WordPress the contact form works as expected. ReCaptcha seems to only block the submission with the user is not authenticated.

Appreciate any insight on how to fix this.