WPIntell

Source evidence

Fatal Error – after update plugin to v1.1.0

Post Access Controller · support · 2016-06-12T09:25:00+00:00

Post Access Controller plugin evidence original source source API
complaintsentiment
highseverity
1.0relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

6 / 32 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.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
oliseh23 unresolved
Hello, I have updated the plugin to Version 1.1.0. I have tried to activate the plugin in wordpress, but I have received a fatal error and the following error message: Parse error: syntax error, unexpected ‘[‘ in /mnt/web3/a3/12/51482912/htdocs/wordpress/wp-content/plugins/post-access-controller/classes/db.php on line 97 What does it mean and how this error can be fixed? I need the plugin because a lot of my News are restricted to users and currently all users can see the News. https://wordpress.org/plugins/post-access-controller/ Hi, just getting back from vacation, this appears to be a result of the php version that you’re running being something before 5.3. I should be able to resolve that pretty quickly to use a syntax that works for previous versions, i’ll try to do it today but for sure in the next couple days. This should be resolved now. I’m going to work on getting a PHP 5.2 image setup for my testing to confirm but wanted to get 1.1.1 out there with this change in place quickly.

Comments

2 shown
arsdehnel 2016-06-14T11:30:00+00:00

Hi, just getting back from vacation, this appears to be a result of the php version that you’re running being something before 5.3. I should be able to resolve that pretty quickly to use a syntax that works for previous versions, i’ll try to do it today but for sure in the next couple days.

arsdehnel 2016-06-15T01:28:00+00:00

This should be resolved now. I’m going to work on getting a PHP 5.2 image setup for my testing to confirm but wanted to get 1.1.1 out there with this change in place quickly.