fippy

Hi @geraltrivia I’ve just tried regular sending again via Google Workspace account and espite using the correct credentials I receive the message:

The email could not be sent: SMTP Error: Could not authenticate.

However, turning on 2-step verification in Google Workspace and replacing my usual password with an App password within the MailPoet settings seemed to work, so thank you!

• This reply was modified 7 months ago by fippy.
• This reply was modified 7 months ago by fippy.

Just for info the other approach I took was to use a hook to update the email template on the fly just before it sent. See example below:

add_filter('mailpoet_rendering_post_process', 'mailpoet_modify_content', 10, 1);

function mailpoet_modify_content( $email_template ) {	
  $find = [
    660', 
    'padding-left:20px;padding-right:20px', 
  ];
  $replacement = [
    '600', 
    'padding-left:7%;padding-right:7%', 
  ];
  $email_template = str_replace($find, $replacement, $email_template);
  return $email_template;
}

@woody24 didn’t find a workaround?

Facing same issue. I too would like to change the default width to 600px and increase the left and right padding from 20px to 50px.

The only way I found was by overriding the values in the following file (presumably this gets overritten on update – any way to make this permanent/maintain the override?)

wp-content/plugins/mailpoet/lib/Newsletter/Renderer/Template.html

Hi, for me it seems to be related to our use of Admin Menu Editor Pro. (This plugin incudes an Toolbar Editor too.) Essentially for Authors and Editors we turn off admin notices, so when switching to users with these roles, the “switch back” option does not appear! (ie the notice next to the green profile icon in your screenshot)

Unfortunately, neither does the option appear in the profile drop down menu you show in your screenshot. I have been trying to find a way to provide permissions that will do this, but no luck so far as it seems to be driven by the permissions of the user switch to, rather than the permissions of the initialy (admin) user.

The offending code appears to be this block at the end of the csp-src.inc.php file:

<p<?php echo !isset($csp_value[$item]['*']) ? NULL : ' style="display: none"'; ?>>
	<input type="text" 
		name="hh_content_security_policy_value[<?php echo $item; ?>][source]" 
		class="http-header-value" 
		size="40"
		placeholder="<?php echo $host_sources[0]; ?>"
		value="<?php echo esc_attr(@$csp_value[$item]['source']); ?>"<?php echo $content_security_policy == 1 ? NULL : ' readonly'; ?>
</p>

I can see it is missing an ">" at the end of the input but that alone does not fix the issue.

Thanks Shea, problem found and solved.

Hi there, please see response from Wordfence:

This is due to the plugin authors not releasing new versions correctly so you can ignore these scan results.

They do not add a tag release number for a new version and only use trunk for a new version which is frowned upon by WordPress:

https://plugins.trac.www.ads-software.com/browser/leadin/#tags

https://developer.www.ads-software.com/plugins/wordpress-org/how-to-use-subversion/#always-tag-releases

If they don’t release a tag number then we can’t properly scan version changes.

Kind regards,

XXXX
Customer Support Engineer

Will you be contacting WordFence to get this comparison and false vulnerability corrected?

Would love an answer to this… it should not be passing on/off by default, it should be passing true/false if anything. Control over exactly what it passes is the ideal…

Please ignore above:

Just tested the latest version: Custom Breakpoints for Elementor v1.0.9

with

Wordpress 5.7,
Elementor 3.1.4,
Elementor Pro 3.2.1

and it does not work.

My WordPress site requires the use of the get parameter. Any other fixes?

+1 same issue

would really like to see this happen… well over a year now?

Hi Hector,

thanks, I think I’ve managed it following the advice you gave… I created a snipped that ran ONLY ONCE with the following:

function update_my_metadata(){
    $args = array(
        'post_type' => 'post', // Only get the posts
        'post_status' => 'publish', // Only the posts that are published
        'posts_per_page'   => -1 // Get every post
    );
    $posts = get_posts($args);
    foreach ( $posts as $post ) {
        // Run a loop and update every meta data
	update_post_meta( $post->ID, 'views_total', '1' );
	update_post_meta( $post->ID, 'views_daily', '1' );
	update_post_meta( $post->ID, 'views_weekly', '1' );
        update_post_meta( $post->ID, 'views_monthly', '1' );
    }
}
// Hook into init action and run our function
add_action('init','update_my_metadata');

• This reply was modified 4 years, 3 months ago by fippy.