wpsnoop: fix FloodWarningsAPI plugin conflicts, errors & issues

When the plugin FloodWarningsAPI conflicts or throws a PHP error we hope wpsnoop can help you to fix the issue quickly.

Discover which shortcodes wp-options PHP functions database tables and files are created by FloodWarningsAPI, plus learn which plugins and/or themes could be in conflict with FloodWarningsAPI.

Troubleshooting theme and plugin conflicts is easier when you know what FloodWarningsAPI leaves behind after uninstalling it from a WordPress installation, there is a list down below for your convenience.

Expert advice is recommended if you are not technically proficient with PHP, MySQL etc. View support options for FloodWarningsAPI

Database Issues

ShortCode Issues

Function Issues

File System Issues

Get professional support for FloodWarningsAPI here

When you need professional help with WordPress: get help here

What does FloodWarningsAPI version 1.0 add to WordPress? Answers Here.

This is an automatically generated report - it is possible for FloodWarningsAPI to perform differently in your installation, previous versions before 1.0 may have created a different set of shortcodes, used different function names or could have created entirely different database tables to store settings and operate. This is not an exhaustive list but shows how version 1.0 of FloodWarningsAPI behaves when installed and removed on a clean installation of WordPress.

We have not tested individual shortcodes, features or settings of this plugin but instead have concentrated on the potential for obvious errors and conflicts which can occur, if you need help with the plugin in your local installation you can get WordPress help and support for FloodWarningsAPI by clicking here.

Our testing covered the free version of this plugin there may or may not be a paid version or premium version available for purchase that unlocks additional features and could behave in a slightly or very different manner.

Summary of WordPress plugin analysis: FloodWarningsAPI

Plugin Slug: floodwarningsapi Internal ID: 28163 Addon Type: Plugin Version: 1.0 Price: Free Source: WordPress.org Files: 6 (28.34kB) Short Codes: [ / ] 0 Database Tables: 0 Function Count: 9 Code Review: Search Provit

Do you need help with FloodWarningsAPI? Get professional plugin support here in no time at all

Which new files does FloodWarningsAPI add to WordPress?

This section will populate with a table showing an icon, size and filepath.

The plugin FloodWarningsAPI added 6 new files when it was installed with WP-CLI in our WordPress test environment.

Type & Path	Size	Conflicts
wp-content/plugins/floodwarningsapi/	28.34kB	No known conflicts with other themes or plugins.
wp-content/plugins/floodwarningsapi/1.0/	14.17kB	No known conflicts with other themes or plugins.
wp-content/plugins/floodwarningsapi/1.0/fw_api.php	12.63kB	No known conflicts with other themes or plugins.
wp-content/plugins/floodwarningsapi/1.0/readme.txt	1.55kB	No known conflicts with other themes or plugins.
wp-content/plugins/floodwarningsapi/fw_api.php	12.63kB	No known conflicts with other themes or plugins.
wp-content/plugins/floodwarningsapi/readme.txt	1.55kB	No known conflicts with other themes or plugins.

Which new shortcodes does FloodWarningsAPI add to WordPress?

The plugin FloodWarningsAPI did not add any shortcodes when it was installed with WP-CLI in our WordPress test environment.

Which new database tables are created by the WordPress plugin FloodWarningsAPI?

FloodWarningsAPI did not create any new database tables when it was installed. It is possible that the plugin creates new database tables after an initial setup or configuration or after some period of use.

Which new options are added to the wp-options table by FloodWarningsAPI?

When FloodWarningsAPI was activated and loaded for the first time it created 4 new options in the wp_options table. Any known conflicts will be shown in red.

Option Name		Known Conflicts
fw_api_key_shoothill		The fw_api_key_shoothill option doesn't have any known conflicts with other themes or plugins.
(empty string)
fw_latitude_fieldname		The fw_latitude_fieldname option doesn't have any known conflicts with other themes or plugins.
(empty string)
fw_longitude_fieldname		The fw_longitude_fieldname option doesn't have any known conflicts with other themes or plugins.
(empty string)
fw_radius		The fw_radius option doesn't have any known conflicts with other themes or plugins.
5

During use FloodWarningsAPI may or may not create more options depending on how the plugin is configured and depending on which other themes and plugins are active in your specific hosting environment.

After disabling and deleting FloodWarningsAPI there were 5 options still present in the wp-options table:

fw_api_key_shoothill
fw_latitude_fieldname
fw_longitude_fieldname
fw_radius
recently_activated

Contact FloodWarningsAPI experts for help

What new PHP functions does FloodWarningsAPI declare when it is active?

Installing FloodWarningsAPI added 9 new functions to Wordpress at run-time. These functions are internal and generally aren't meant to be used except by developpers who wish to interface with the plugin to enhance or alter its behavior.

Function	Conflicts	Common Errors
create_post_types	2 conflicts	Fatal error: Cannot redeclare create_post_types()
display_flood_warnings	0 conflicts	Fatal error: Cannot redeclare display_flood_warnings()
fw_install_plugin	0 conflicts	Fatal error: Cannot redeclare fw_install_plugin()
fw_options	0 conflicts	Fatal error: Cannot redeclare fw_options()
fw_options_menu	0 conflicts	Fatal error: Cannot redeclare fw_options_menu()
fw_uninstall_plugin	0 conflicts	Fatal error: Cannot redeclare fw_uninstall_plugin()
get_warnings	0 conflicts	Fatal error: Cannot redeclare get_warnings()
jmtg_fw_hourly_event	0 conflicts	Fatal error: Cannot redeclare jmtg_fw_hourly_event()
wp_exist_post	0 conflicts	Fatal error: Cannot redeclare wp_exist_post()

Using FloodWarningsAPI from the command line with WP-CLI

The following commands are provided for convenience and should only be used if you understand how WP-CLI works. These commands refer to a single WordPress instance and may need to be modified if you are working with a Multisite installation.

How to install FloodWarningsAPI from the command line with WP-CLI

Navigate to the root of your WordPress installation and type the following command:

wp plugin install floodwarningsapi

How to activate FloodWarningsAPI from the command line with WP-CLI

To immediately activate FloodWarningsAPI after WP-CLI downloads the latest version you can use the following command:

wp plugin install floodwarningsapi --activate

How to reinstall FloodWarningsAPI from the command line with WP-CLI

To force a reinstallation of FloodWarningsAPI which overwrites the current plugin without asking for confirmation you can use the following command:

wp plugin install floodwarningsapi --force

How to update FloodWarningsAPI to the latest version from the command line with WP-CLI

wp plugin update floodwarningsapi

How to delete FloodWarningsAPI from the command line with WP-CLI

wp plugin delete floodwarningsapi

Where can you download earlier versions of FloodWarningsAPI?

Whenever possible you should use the latest version of plugins and themes, however if you have recently updated and discovered that you need to install an earlier version you may be able to download other versions of FloodWarningsAPI from the WordPress repository by visiting this link.

Please note that installing earlier versions of a theme or plugin is not generally a recommended course of action for most users and could re-introduce security, stability or other issues in FloodWarningsAPI

About our testing enviroment

Tests were conducted using Apache 2.4.29, PHP 7.2 on Ubuntu 18.04, MySQL 5.7.33 and WordPress 5.9

It is very possible that different versions of PHP such as PHP 8.0, PHP 7.4, or PHP 7.3 could behave differently with FloodWarningsAPI. Different versions of WordPress could implement the features of this plugin in slightly different ways as well.