Plugin Author
Brecht
(@brechtvds)
That’s strange. Do you have a link to an example page with this problem so I can take a look?
Hi, Sorry for the delay in response. I’ve attached some before and after screenshots.
BEFORE: This is at normal, 100% zoom in the browser, and with content protection disabled.
https://ibb.co/3zNDrjz
AFTER: This had to be zoomed to 50% to fit in frame, but is after the content protection is enabled.
https://ibb.co/7Ww6ZPq
As you can see the preview image is blown by a massive amount (1000% ?) when the content protection is enabled for the page.
Plugin Author
Brecht
(@brechtvds)
I’ve been trying to replicate this problem on my end using the VLP and Simple Membership plugin but I can’t seem to cause this problem.
Can you send me a link to the issue to [email protected] so I can take a look?
Hmm strange. I did verify in both Firefox and Chrome that the issue persists across both browsers. Unfortunately the page in question is only on a localhost so I am unable to send a link.
Is there more information I can provide to help with troubleshooting? Plugin list? Theme?
Thanks
Plugin Author
Brecht
(@brechtvds)
Could you test if it happens when using a default theme (like Twenty Twenty) and no other plugins except for Visual Link Preview and Simple Membership?
Sorry for the delay. I just did a fresh install on my localhost (Bitnami) using Twenty Twenty theme with only Simple Membership and Visual Link Preview, and the image enlarging issue still occurs with content protection still on.
To be more specific, I have enabled the “more tag” content protection setting in Simple Membership plugin settings. When the test page has the more tag in place with the content protection on, the image enlarging happens in the preview.
Plugin Author
Brecht
(@brechtvds)
I wasn’t aware of that setting. Just enabled that and I do see the issue then.
In the /simple-membership/classes/class.swpm-utils-misc.php file you find the following function starting line 443:
public static function format_raw_content_for_front_end_display( $raw_content ) {
$formatted_content = wptexturize( $raw_content );
$formatted_content = convert_smilies( $formatted_content );
$formatted_content = convert_chars( $formatted_content );
$formatted_content = wpautop( $formatted_content );
$formatted_content = shortcode_unautop( $formatted_content );
$formatted_content = prepend_attachment( $formatted_content );
$formatted_content = capital_P_dangit( $formatted_content );
$formatted_content = do_shortcode( $formatted_content );
return $formatted_content;
}
Here the do_blocks function should get added for compatibility with the block editor. Basically having it like this:
public static function format_raw_content_for_front_end_display( $raw_content ) {
$formatted_content = wptexturize( $raw_content );
$formatted_content = convert_smilies( $formatted_content );
$formatted_content = convert_chars( $formatted_content );
$formatted_content = wpautop( $formatted_content );
$formatted_content = shortcode_unautop( $formatted_content );
$formatted_content = prepend_attachment( $formatted_content );
$formatted_content = capital_P_dangit( $formatted_content );
$formatted_content = do_shortcode( $formatted_content );
$formatted_content = do_blocks( $formatted_content );
return $formatted_content;
}
If they make that change in their plugin files, things should be working as expected!
Thanks! I have alerted the plugin maintainer, feel free to follow up with them directly too. I assume they will more likely respond to you, than a regular user like myself.
https://ww.wp.xz.cn/support/topic/content-protection-issues-with-link-preview-plugin/#post-14956392
