"Failed to access plexWatch database. Please check your settings." after latest plexWatch installed

[fysmd]

I just pulled ther latests plexWatch from github (now 0.3.1) and after it ran first time I now get this error in plexWatchWeb.

from settings page (when broken):
Version Information
plexWatch/Web Version: v1.5.4.2
plexWatch Version: v

Reverting plexWatch and DB to 0.2.9 (1d30ab3) version seems to fix it.

.. or should this be reported as a plexWatch issue instead?

[keithah]

I have the same issue. Any ideas?

[fysmd]

revert plexwatch to 0.2.9 and plexwatchweb works again.
You'll need to find a backup of your plexwatch DB if you dont want to loose data though.

[winstano]

I was having this too, but did a chmod -R 777 on the root of my PlexWatch folder (on OSX it was /opt/plexWatch) and it's working again now

[skingry]

Making the directory where the plexWatch.db file is located writable by the user the web server is running as (www-data for Debian variants) fixes this as well... no need to 'chmod -R 777' everything.

[Ackis]

Why is write access to the entire directory needed?

[Arcanemagus]

SQLite creates two temporary files when accessing a database to store changes... even if none are made. If it is unable to create these temporary files it fails to open the database.

I had hoped to remove this requirement by using the native sqlite3() functions in PHP and setting the connection to read only, but it still creates the files. As PDO is, on average, 2x faster at database operations PWW currently uses that even though it doesn't have an explicit read only mode.