PressForward error: unable to access the relationships database
I have been trying to use the PressForward plugin on my course site (dhpraxisfall16.commons.gc.cuny.edu) and each time I access the feed reader and click on an item in "all content" , I get the following error: "PressForward was unable to access the relationships database." The item does appear, however, after you click through the error. The same thing happens at each stage of the process (nominating an item, commenting on an item, opening an item in the nominations panel, sending the item to draft). The thing is that the item continues to move and you can get it to go to "draft."
I talked to Aram about it, and he seems to think that it might be that the Commons is preventing PressForward from spawning a new table to house the feed reader's content. I'm not sure if that could be the case, though because the item still shows up even after displaying the error.
Figuring out what is going on would be helpful because the PressForward outreach group is coming to do a workshop on using PressForward on September 23rd. They will probably use a stand alone sandbox instance to do the first training. However, chances are that because PF is on the Commons, we may have a sudden increase in use and want to head off any error messages before then.
Updated by Lisa Rhody about 6 years ago
I'm not sure if this is related or not, but when I publish any post now on the site, it is not appearing in the list of most recent posts on the first page. I have 6 posts on my site, but only the posts published before adding PressForward appear. I'm not sure if those things are related or not: https://dhpraxisfall16.commons.gc.cuny.edu/.
Updated by Boone Gorges about 6 years ago
- Status changed from New to Testing Required
- Target version set to 1.9.28
Thanks for the detailed report and for your patience, Lisa.
I tracked the issue down to a bug in the way that PressForward attempts to install its database tables, which makes it incompatible with WordPress Multisite.
I've submitted a PR to the PF repo with a fix: https://github.com/PressForward/pressforward/pull/831
I've ported the fix to the Commons and deployed it as a hotfix to the live site, so that you can test https://github.com/cuny-academic-commons/cac/commit/4f0c8726f76abee0e43e12e8e8ba005069dcc303