WordPress.org
Get WordPress

Plugin Directory

Changeset 1582851


Ignore:
Timestamp:
01/26/2017 06:44:26 PM (9 years ago)
Author:
seedplugins
Message:

Updated the plugin description with new advices.

Location:
wp-link-status
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • wp-link-status/tags/1.0.4/readme.txt

    r1582826 r1582851  
    2323> **Troubleshooting**
    2424>
    25 > **Firewall plugins**
     25> **- Firewall plugins**
    2626>
    2727> If you are using the **Wordfence** plugin, in order to work properly you need to deactivate their Firewall module (even temporarily). Go to the Wordfence menu Firewall, and from the Firewall Status pick Disabled and click the save button. After the scan is complete, you can activate the firewall again.
    … …  
    3131> Another issue detected with the **WP Secure** plugin, you need to deactivate this plugin in order to run the scan properly.
    3232>
    33 > **WordPress Multisite**
     33> **- WordPress Multisite**
    3434>
    3535> This plugin does **not support network activation for WordPress Multisite**, so in case of multisite installs it needs to be activated per each blog individually. Also it is recommended to run only one scan per blog at the same time to prevent server performance issues.
     36>
     37> **- Hosting restrictions**
     38>
     39> Some users have reported issues with **GoDaddy hosting** due restrictions for sites with HTTPS enabled and the cURL module (an internal server module used to make HTTP requests to check the links) for some hosting configurations. It seems that GoDaddy applies limits for this module via proxy or similar. This is a hosting-level so this plugin have nothing to do about it.
    3640
    3741You can read a detailed user guide and the documentation from the plugin page:

  • wp-link-status/trunk/readme.txt

    r1582826 r1582851  
    2323> **Troubleshooting**
    2424>
    25 > **Firewall plugins**
     25> **- Firewall plugins**
    2626>
    2727> If you are using the **Wordfence** plugin, in order to work properly you need to deactivate their Firewall module (even temporarily). Go to the Wordfence menu Firewall, and from the Firewall Status pick Disabled and click the save button. After the scan is complete, you can activate the firewall again.
    … …  
    3131> Another issue detected with the **WP Secure** plugin, you need to deactivate this plugin in order to run the scan properly.
    3232>
    33 > **WordPress Multisite**
     33> **- WordPress Multisite**
    3434>
    3535> This plugin does **not support network activation for WordPress Multisite**, so in case of multisite installs it needs to be activated per each blog individually. Also it is recommended to run only one scan per blog at the same time to prevent server performance issues.
     36>
     37> **- Hosting restrictions**
     38>
     39> Some users have reported issues with **GoDaddy hosting** due restrictions for sites with HTTPS enabled and the cURL module (an internal server module used to make HTTP requests to check the links) for some hosting configurations. It seems that GoDaddy applies limits for this module via proxy or similar. This is a hosting-level so this plugin have nothing to do about it.
    3640
    3741You can read a detailed user guide and the documentation from the plugin page:
Note: See TracChangeset for help on using the changeset viewer.