WPIntell

Source evidence

Error after installing new version

Autolinks Manager – SEO Auto Linker · support · 2024-06-18T06:16:00+00:00

complaintsentiment
mediumseverity
0.92relevance
6replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

3 / 16 rows with source links

18.8% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

13 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
gabrielsampol unresolved
Since I update the plugin I can no longer access the wp-admin and all other admin pages that show an error 500 – Internal server error. I also get an email from WordPress telling that there is a plugin causing trouble. I copy the relevant part below. Although it is in Spanish it is understandable. What can I do? WordPress versión 5.9.9 Tema actual: Newsup (versión 4.0.0.36) Plugin actual: Autolinks Manager (versión 1.10.08) PHP versión 7.2.34 Detalles del error ================== Se ha producido un error del tipo E_PARSE en la línea 914 del archivo C:\inetpub\vhosts\sendaestelar.com\httpdocs\wp-content\plugins\daext-autolinks-manager\admin\class-daextam-admin.php. Mensaje de error: syntax error, unexpected ‘)’ The page I need help with: [ log in to see the link] Hello gabrielsampol, Thank you for all the details. There are no syntax errors at line line 914. You can inspect the exact line at the link below or check it with a PHP IDE or error checker. https://plugins.trac.wordpress.org/browser/daext-autolinks-manager/trunk/admin/class-daextam-admin.php#L914 To solve proceed as follows: Delete the daext-autolinks-manager folder from the /wp-content/plugins/ location using your favorite FTP program. After that I recommend you to test the plugin in a staging website in the same server and verify which conditions are causing the problem. E.g. Has the file been modified? Has the file not been downloaded correctly from the WordPress repository? Etc. Thanks for the answer. I followed your advice and deleted the daext-autlolinks-manager folder. After that I could navigate to the wordpress admin pages and did a new installation of the plugin. It went OK, without errors, but when I try to activate it I get an error 500 and it does not activate. So the situation now is that my site is working normally, except that I can’t active the daext-autlolinks-manager plugin. I can only tell that the issue arised after I updated the plugin. I had been using it before without issues. This reply was modified 1 year, 11 months ago by gabrielsampol . This reply was modified 1 year, 11 months ago by gabrielsampol . Isn’t there an extra comma at the end of line 913? ‘ https://daext.com/doc/autolinks-manager/’ ;, Hello gabrielsampol, I’ve investigated the issue. You can solve by upgrading to PHP 7.3 or later releases. The comma at the end line of line 913 is considered an error in old PHP versions. (7.2 and older versions) The same problem has been reported with other plugins in the past: https://wordpress.org/support/topic/parse-error-syntax-error-unexpected-thats-not-really-unexpected/ Updated to PHP 7.3.33 and the error persists. Hello gabrielsampol, I recommend proceeding as follows: 1. Remove lines from 908 to 914 to solve the problem. 2. Upgrade to the latest PHP version and test the plugin in a staging environment. So you can download and use new plugin releases that will come in the future without modifying each time the file. If the problem persists after upgrading to PHP > 8.0 contact the hosting provider and report the PHP parsing problem. This reply was modified 1 year, 11 months ago by DAEXT .

Comments

6 shown
DAEXT 2024-06-18T07:35:00+00:00

Hello gabrielsampol, Thank you for all the details. There are no syntax errors at line line 914. You can inspect the exact line at the link below or check it with a PHP IDE or error checker. https://plugins.trac.wordpress.org/browser/daext-autolinks-manager/trunk/admin/class-daextam-admin.php#L914 To solve proceed as follows: Delete the daext-autolinks-manager folder from the /wp-content/plugins/ location using your favorite FTP program. After that I recommend you to test the plugin in a staging website in the same server and verify which conditions are causing the problem. E.g. Has the file been modified? Has the file not been downloaded correctly from the WordPress repository? Etc.

gabrielsampol 2024-06-18T08:57:00+00:00

Thanks for the answer. I followed your advice and deleted the daext-autlolinks-manager folder. After that I could navigate to the wordpress admin pages and did a new installation of the plugin. It went OK, without errors, but when I try to activate it I get an error 500 and it does not activate. So the situation now is that my site is working normally, except that I can’t active the daext-autlolinks-manager plugin. I can only tell that the issue arised after I updated the plugin. I had been using it before without issues. This reply was modified 1 year, 11 months ago by gabrielsampol . This reply was modified 1 year, 11 months ago by gabrielsampol .

gabrielsampol 2024-06-18T09:01:00+00:00

Isn’t there an extra comma at the end of line 913? ‘ https://daext.com/doc/autolinks-manager/’ ;,

DAEXT 2024-06-18T12:41:00+00:00

Hello gabrielsampol, I’ve investigated the issue. You can solve by upgrading to PHP 7.3 or later releases. The comma at the end line of line 913 is considered an error in old PHP versions. (7.2 and older versions) The same problem has been reported with other plugins in the past: https://wordpress.org/support/topic/parse-error-syntax-error-unexpected-thats-not-really-unexpected/

gabrielsampol 2024-06-18T15:23:00+00:00

Updated to PHP 7.3.33 and the error persists.

DAEXT 2024-06-18T16:49:00+00:00

Hello gabrielsampol, I recommend proceeding as follows: 1. Remove lines from 908 to 914 to solve the problem. 2. Upgrade to the latest PHP version and test the plugin in a staging environment. So you can download and use new plugin releases that will come in the future without modifying each time the file. If the problem persists after upgrading to PHP > 8.0 contact the hosting provider and report the PHP parsing problem. This reply was modified 1 year, 11 months ago by DAEXT .