Flipdish Ordering System

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.

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "update_new_values".

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "update_to_new_options".

Tested up to: 6.7 < 6.8. The "Tested up to" value in your plugin is not set to the current version of WordPress. This means your plugin will not show up in searches, as we require plugins to be compatible and documented as tested up to the most recent version of WordPress.

Classes declared by a theme/plugin should start with the theme/plugin prefix. Found: "System_Info".

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "on_flipdish_ordering_update".

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "update_apple_pay_files".

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

Functions declared in the global namespace by a theme/plugin should start with the theme/plugin prefix. Found: "front_end_web_ordering_scripts".

wp_redirect() found. Using wp_safe_redirect(), along with the &quot;allowed_redirect_hosts&quot; 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.