Changeset 1582888
- Timestamp:
- 01/26/2017 07:27:09 PM (9 years ago)
- Location:
- wp-link-status
- Files:
-
- 2 edited
-
tags/1.0.4/readme.txt (modified) (3 diffs)
-
trunk/readme.txt (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
wp-link-status/tags/1.0.4/readme.txt
r1582882 r1582888 29 29 > In the same way, we have detected a conflict with **All In One WP Security & Firewall** plugin and its Brute Force module, so it is necessary to deactivate these options before play this plugin. 30 30 > 31 > Another issue detected with the **WP Secure** plugin, you need to deactivate this plugin in order to run the scan properly. 31 > Another issue also detected with the **WP Secure** plugin, you need to deactivate this plugin in order to run the scan properly. 32 > 33 > **- Hosting restrictions** 34 > 35 > Some users have reported issues for **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 problem, so this plugin have nothing to do to solve it. 32 36 > 33 37 > **- WordPress MultiSite** … … 39 43 > This plugin just creates one file called wp-link-status-salt.php directly into the wp-content directory, so that directory must be writable by the web server (recommended 755 permissions). The CHMOD is used to ensure the right permissions 0644 to the file (not the directory) according the WordPress permissions scheme: 40 44 > 41 > https://codex.wordpress.org/Changing_File_Permissions 42 > 43 > **- Hosting restrictions** 44 > 45 > Some users have reported issues for **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 problem, so this plugin have nothing to do to solve it. 45 > https://wordpress.org/support/topic/salt-file/#post-8250977 46 46 > 47 47 > **- Support and documentation** 48 48 > 49 > **Pro version** provides extended search filters and the possibility to edit the post content links directly from the search results without using the WP editor, including bulk actions mode for most operations. 50 > 51 > You can read a detailed **user guide documentation** from the plugin page that describes also the Pro version features. 49 > **Pro version** provides extended search filters and the possibility to edit the post content links directly from the search results without using the WP editor, including bulk actions mode for most operations: 52 50 > 53 51 > http://seedplugins.com/wp-link-status/ 52 > 53 > You can read a detailed **user guide documentation** from the plugin page that describes also the Pro version features: 54 > 55 > http://seedplugins.com/wp-link-status/user-guide-wpls/ 54 56 55 57 == Installation == … … 92 94 = This plugin works for ACF or Advanced Custom Fields as well? = 93 95 94 Yes, at the end ACF works the same way that normal custom fields .96 Yes, at the end ACF works the same way that normal custom fields, as long as the ACF value for a custom field does not use special data structures (like arrays serialized values, per example). 95 97 96 98 You can add the custom field name in the "Content options" tab of the scan, selecting if it is an expected full URL or a content with links. -
wp-link-status/trunk/readme.txt
r1582882 r1582888 29 29 > In the same way, we have detected a conflict with **All In One WP Security & Firewall** plugin and its Brute Force module, so it is necessary to deactivate these options before play this plugin. 30 30 > 31 > Another issue detected with the **WP Secure** plugin, you need to deactivate this plugin in order to run the scan properly. 31 > Another issue also detected with the **WP Secure** plugin, you need to deactivate this plugin in order to run the scan properly. 32 > 33 > **- Hosting restrictions** 34 > 35 > Some users have reported issues for **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 problem, so this plugin have nothing to do to solve it. 32 36 > 33 37 > **- WordPress MultiSite** … … 39 43 > This plugin just creates one file called wp-link-status-salt.php directly into the wp-content directory, so that directory must be writable by the web server (recommended 755 permissions). The CHMOD is used to ensure the right permissions 0644 to the file (not the directory) according the WordPress permissions scheme: 40 44 > 41 > https://codex.wordpress.org/Changing_File_Permissions 42 > 43 > **- Hosting restrictions** 44 > 45 > Some users have reported issues for **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 problem, so this plugin have nothing to do to solve it. 45 > https://wordpress.org/support/topic/salt-file/#post-8250977 46 46 > 47 47 > **- Support and documentation** 48 48 > 49 > **Pro version** provides extended search filters and the possibility to edit the post content links directly from the search results without using the WP editor, including bulk actions mode for most operations. 50 > 51 > You can read a detailed **user guide documentation** from the plugin page that describes also the Pro version features. 49 > **Pro version** provides extended search filters and the possibility to edit the post content links directly from the search results without using the WP editor, including bulk actions mode for most operations: 52 50 > 53 51 > http://seedplugins.com/wp-link-status/ 52 > 53 > You can read a detailed **user guide documentation** from the plugin page that describes also the Pro version features: 54 > 55 > http://seedplugins.com/wp-link-status/user-guide-wpls/ 54 56 55 57 == Installation == … … 92 94 = This plugin works for ACF or Advanced Custom Fields as well? = 93 95 94 Yes, at the end ACF works the same way that normal custom fields .96 Yes, at the end ACF works the same way that normal custom fields, as long as the ACF value for a custom field does not use special data structures (like arrays serialized values, per example). 95 97 96 98 You can add the custom field name in the "Content options" tab of the scan, selecting if it is an expected full URL or a content with links.
Note: See TracChangeset
for help on using the changeset viewer.