Database Backup for WordPress

All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '"$table:$segment:$filename"'.

A function call to __() with texts containing placeholders was found, but was not accompanied by a "translators:" comment on the line above to clarify the meaning of the placeholders.

All output should be run through an escaping function (like esc_html_e() or esc_attr_e()), found '_e'.

Detected usage of a possibly undefined superglobal array index: $_GET['recipient']. Check that the array index exists before using it.

$_GET['backup'] not unslashed before sanitization. Use wp_unslash() or similar

Processing form data without nonce verification.

Processing form data without nonce verification.

Use placeholders and $wpdb->prepare(); found interpolated variable $table at "DESCRIBE $table"

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().

Unescaped parameter $table used in $wpdb->get_results()

The use of function ini_set() is discouraged

Detected usage of a non-sanitized input variable: $_POST[$post_key]

unlink() is discouraged. Use wp_delete_file() to delete a file.

date() is affected by runtime timezone changes which can cause date/time to be incorrectly displayed. Use gmdate() instead.

The plugin name includes a restricted term. Your chosen plugin name - "Database Backup for WordPress" - contains the restricted term "wordpress" which cannot be used at all in your plugin name.

wp_redirect() found. Using wp_safe_redirect(), along with the "allowed_redirect_hosts" filter if needed, can help avoid any chances of malicious redirects within code. It is also important to remember to call exit() after a redirect so that no other unwanted code is executed.

File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fclose().

File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fopen().

File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: fwrite().

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.

Attempting a database schema change is discouraged.

File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: chmod().

File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: mkdir().

File operations should use WP_Filesystem methods instead of direct PHP filesystem calls. Found: readfile().