shamrock82

Great! 🙂

However, your plugin page https://ww.wp.xz.cn/plugins/wp-approve-user/ has the warning across the top:

“This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.”

… so it would be easy to assume it is stale or no longer supported. I’d recommend testing it with the latest versions of WP.

To help others, I wanted to share that I’ve determined this is a conflict between MemberPress and this PDF Embedder plugin. It would be helpful if you could add this to the plugin’s documentation @slaffik

MemberPress Support: “After checking the issue, I noticed a conflict between the PDF Embed plugin and MemberPress. I think that’s because the PDF Embed plugin adds its stylesheets into the body, not into the head, which is not the best practice. So, I came up with this code snippet to load the PDF Embed stylesheet into the head, add it to the site theme’s functions.php file, and the PDF enclosure renders correctly now for logged out users.”

// Load the PDF Embed style add_action('wp_enqueue_scripts', function() { wp_enqueue_style( 'pdfemb_embed_pdf_css', plugins_url('pdf-embedder/assets/css/pdfemb.min.css') ); });

I requested a code fix that would only load the PDF Embedder CSS if a PDF was actually embedded on a page, rather than loading it (potentially when not required) on EVERY page.

// Load the PDF Embed style add_action('wp_enqueue_scripts', function() { if ( has_block('pdfemb/pdf-embedder-viewer') ) { wp_enqueue_style( 'pdfemb_embed_pdf_css', plugins_url('pdf-embedder/assets/css/pdfemb.min.css') ); } });

We don’t have caching enabled on our site because MemberPress advise against it and I have disabled the only plugin we had that optimizes/minifies CSS or JS (SWIS Performance).

Have you tested your plugin with Beaver Builder? Are there customizations that need to be made to your plugin or to our Beaver Builder theme in order for PDF Embedder to work properly?

AppPresser have a solution for disabling WP plugins in the app version of one’s website:

https://docs.apppresser.com/article/438-plugin-blocker

• This reply was modified 1 year, 2 months ago by shamrock82.

Screenshots uploaded here:

https://drive.google.com/drive/folders/17R14uyAaTMdOgQzwx6XZ6PRmR9Xm9uYa?usp=sharing

Marking resolved

Thanks Val! To clarify, I’ve never had this plugin working, it’s failed in the same way on 2 different WP instances (both WP Engine) I’ve tested on.

Using Chrome Dev Tools, here’s what I see in the 502 Bad Gateway request response:

General:

Request URL: https://scldevlp.wpenginepowered.com/wp-json/media-cleaner/v1/extract_references
Request Method: POST
Status Code: 502 Bad Gateway
Remote Address: 141.193.213.11:443
Referrer Policy: strict-origin-when-cross-origin

Response Headers:

Alt-Svc: h3=":443"; ma=86400
Cache-Control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Cf-Ray: 87c9b9234a002aa4-LAX
Content-Length: 6412
Content-Type: text/html; charset=UTF-8
Date: Tue, 30 Apr 2024 18:53:04 GMT
Expires: Thu, 01 Jan 1970 00:00:01 GMT
Referrer-Policy: same-origin
Server: cloudflare
X-Frame-Options: SAMEORIGIN

Request Headers:

:authority: scldevlp.wpenginepowered.com

:method:POST

:path: /wp-json/media-cleaner/v1/extract_references

:scheme: https

Accept:

*/*

Accept-Encoding: gzip, deflate, br, zstd

Accept-Language: en-US,en;q=0.9

Authorization: Basic c2NsZGV2bHA6ZWY5MTFhMzU=

Cache-Control: no-cache

Content-Length: 32

Content-Type: application/json

Cookie: wordpress_test_cookie=WP%20Cookie%20check; _ga=GA1.1.1962695284.1714252481; wp_lang=en_US; wpe-auth=5bfe14d731590d92644d4953a7571078250b240cbf177d37c89025ffd93ba290; wordpress_logged_in_2d395f41fe5c6d41f09beb0a010dcb18=donalrafferty%7C1715696081%7CwxHGTz0ZAEhCV5jL6ddzTNcc5b8f15RX4YbuOLDt1UK%7C0fbcf8fe03257b33f190ae00c9531e3dc6652f0f49e28382d010b921a5c9fbfe; wp-settings-13596=editor%3Dtinymce%26posts_list_mode%3Dlist%26libraryContent%3Dbrowse%26imgsize%3Dlarge%26nua_registration_complete_message_editor%3Dtmce%26nua_registration_message_editor%3Dtmce; wp-settings-time-13596=1714486481; _ga_R855W6FKQ7=GS1.1.1714500399.5.0.1714500399.0.0.0

Origin: https://scldevlp.wpenginepowered.com

Pragma: no-cache

Priority:u=1, i

Referer: https://scldevlp.wpenginepowered.com/wp-admin/upload.php?page=wpmc_dashboard

Sec-Ch-Ua: "Chromium";v="124", "Google Chrome";v="124", "Not-A.Brand";v="99"

Sec-Ch-Ua-Mobile: ?0

Sec-Ch-Ua-Platform: "macOS"

Sec-Fetch-Dest: empty

Sec-Fetch-Mode: cors

Sec-Fetch-Site: same-origin

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36

X-Wp-Nonce: 2f52d127f4

Does anything here point to what the issue is?

The HAR file for the request is here (which you can open in Chrome Dev Tools yourself) – you’ll find the 502 at line 409952 if viewing it in a text editor.