WPIntell

Source evidence

PHP Fatal Error on Auto Update

PHP Browser Detection · support · 2016-07-13T01:09:00+00:00

PHP Browser Detection plugin evidence original source source API
complaintsentiment
highseverity
0.98relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

4 / 25 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

21 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
bwarnerwordpress unresolved
We have php-browser-detection installed on a client site of ours. We upgraded php-browser-detection to Version 3.8 on June 2nd. On July 2nd we received the following PHP Fatal Error: [Sun Jul 02 00:16:36.538579 2016] [:error] [pid 10313] [] PHP Fatal error: Uncaught exception ‘phpbrowscap\\Exception’ with message ‘error opening lockfile /home/release/www/www.clientsite.com/wp-content/plugins/php-browser-detection/cache/cache.lock’ in /home/release/www/www.clientsite.com/wp-content/plugins/php-browser-detection/lib/Browscap.php:527 This fatal error continued for some time causing our WordPress pages to fail to render properly. Some questions that I have: 1.) Has anyone else experienced something similar on their WordPress installations? 2.) Cache.lock is not a file that is included when downloading the latest version of your plugin. It seems like there is a permissions issue with the plugin in that it either expects this file to already be there or it cannot create it when it needs it. Can you provide any more details around this? 3.) The remedy for this was to create the cache.lock file manually and set write permissions on it. If thats the case though then this should be part of the installation instructions unless Im missing something. Thanks for any help you can give me. Sincerely, Brian https://wordpress.org/plugins/php-browser-detection/ This sounds like a standard permissions issue. However, it also could be that PHP is running out of RAM while writing to the file but based on your solution it seems more likely to be a problem with permissions. An update will be released soon, we’ll look out for this during testing.

Comments

1 shown
Mindshare Labs, Inc. 2016-11-08T20:59:00+00:00

This sounds like a standard permissions issue. However, it also could be that PHP is running out of RAM while writing to the file but based on your solution it seems more likely to be a problem with permissions. An update will be released soon, we’ll look out for this during testing.