wpsnoop: fix SecSign plugin conflicts, errors & issues
When the plugin SecSign 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 SecSign, plus learn which plugins and/or themes could be in conflict with SecSign.
Troubleshooting theme and plugin conflicts is easier when you know what SecSign 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 SecSign
When you need professional help with WordPress: get help here
What does SecSign version 1.8.0 add to WordPress? Answers Here.
This is an automatically generated report - it is possible for SecSign to perform differently in your installation, previous versions before 1.8.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.8.0 of SecSign 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 SecSign 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: SecSign
Which new files does SecSign add to WordPress?
This section will populate with a table showing an icon, size and filepath.
| Type & Path | Size | Conflicts |
|---|---|---|
| wp-content/plugins/secsign/ | 511.52kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/images/ | 98.41kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/images/accesspass_bg.png | 34.67kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/images/checkbox.png | 3.38kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/images/icons.png | 5.03kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/images/index.php | 30.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/images/preload.gif | 6.66kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/images/secsign_icon20.png | 660.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/images/secsign16x16.png | 3.86kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/images/secsignhelp.png | 32.50kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/images/secsignidlogo.png | 11.63kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/index.php | 30.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/jsApi/ | 266.73kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/jsApi/index.php | 30.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/jsApi/phpApi/ | 251.05kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/jsApi/phpApi/curl-ca-bundle.crt | 230.53kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/jsApi/phpApi/index.php | 30.00B | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/jsApi/phpApi/SecSignIDApi.php | 20.49kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/jsApi/SecSignIDApi.js | 12.29kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/jsApi/signin-bridge.php | 3.36kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/readme.txt | 19.01kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/secsignfunctions.js | 19.79kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/secsignid_layout.css | 10.07kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/secsignid_login_admin.php | 28.74kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/secsignid_login_db.php | 11.19kB | No known conflicts with other themes or plugins. |
| wp-content/plugins/secsign/secsignid_login.php | 57.56kB | No known conflicts with other themes or plugins. |
Which new shortcodes does SecSign add to WordPress?
Which new database tables are created by the WordPress plugin SecSign?
| Table name | Known Plugin or Theme conflicts |
|---|---|
| wp_secsign | The wp_secsign table doesn't have any known conflicts with other themes or plugins. |
| Table name | Status |
|---|---|
| wp_secsign | Orphan/Zombie |
Click the table name above for more information on what the orphan table could mean to your WordPress installation and some tips on how to deal with it.
Which new options are added to the wp-options table by SecSign?
| Option Name | Known Conflicts | |
|---|---|---|
| widget_wp_secsignidlogin | The widget_wp_secsignidlogin option doesn't have any known conflicts with other themes or plugins. | |
During use SecSign 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.
What new PHP functions does SecSign declare when it is active?
Using SecSign 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 SecSign from the command line with WP-CLI
Navigate to the root of your WordPress installation and type the following command:
How to activate SecSign from the command line with WP-CLI
To immediately activate SecSign after WP-CLI downloads the latest version you can use the following command:
How to reinstall SecSign from the command line with WP-CLI
To force a reinstallation of SecSign which overwrites the current plugin without asking for confirmation you can use the following command:
How to update SecSign to the latest version from the command line with WP-CLI
How to delete SecSign from the command line with WP-CLI
Where can you download earlier versions of SecSign?
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 SecSign 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 SecSign
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 SecSign. Different versions of WordPress could implement the features of this plugin in slightly different ways as well.