PDF.js Viewer

Global variables defined by a theme/plugin should start with the theme/plugin prefix. Found: "$allowed_domains".

parse_url() is discouraged because of inconsistency in the output across PHP versions; use wp_parse_url() instead.

Processing form data without nonce verification.

Use of heredoc syntax (<<<) is not allowed; use standard strings or inline HTML instead

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'str_replace'.

$_GET[&#039;url&#039;] not unslashed before sanitization. Use wp_unslash() or similar

PHP file should prevent direct access. Add a check like: if ( ! defined( 'ABSPATH' ) ) exit;

load_plugin_textdomain() has been discouraged since WordPress version 4.6. When your plugin is hosted on WordPress.org, you no longer need to manually include this function call for translations under your plugin slug. WordPress will automatically load the translations for you as needed.

Use of a direct database call is discouraged.

Direct database call without caching detected. Consider using wp_cache_get() / wp_cache_set() or wp_cache_delete().

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: &quot;include_pdfjs_media_button_js_file&quot;.

Detected usage of a non-sanitized input variable: $_GET[&#039;v&#039;]

Detected usage of a possibly undefined superglobal array index: $_SERVER[&#039;REQUEST_METHOD&#039;]. Check that the array index exists before using it.

Application files are not permitted.

Plugin name "PDF.js Viewer" is different from the name declared in plugin header "PDFjs Viewer - Embed PDFs".

Unexpected markdown file "DEVELOPER.md" detected in plugin root. Only specific markdown files are expected in production plugins.