I would not recommend the close statement - technically you don't need it as PHP will clean up after you. The older "stable" version of cpmfetch (we are on the cusp of a new age with cpmfetch 2.0) had a nasty habit of trashing your database connection if it re-used it.
I suggested the close in the faint hope that eFiction would be smart enough to open a fresh connection. Unfortunately, it wasn't.
I would not suspect problems with PHP5 and cpmfetch. Not sure what the add on there does to it.
If you want to post links, I will check and see what efflication does for php blocks and what calic0cats module does.
In order to see a working version of cpmfetch in eFiction blocks, you can check my own site at
http://www.calic0cat.net - that one has efiction and Coppermine sharing a database, and cpmfetch and Coppermine are both in (separate) subdirectories of the eFiction directory. I also have it working on two test sites, one at
http://test.calic0cat.net/efiction/ with a shared database but with eFiction and Coppermine in side-by-side directories, and one at
http://test2.calic0cat.net/efiction/ with eFiction and Coppermine on separate databases and in side-by-side directories. It works just fine in all three cases. All working examples are eFiction 3.2 (both test sites) or 3.2.1 (live site only) with Coppermine Gallery 1.4.10 and cpmfetch 1.6.4. The MySQL version is 4.1.16 and PHP is 4.4.2 (with "extra web security"). All sites are (normally) bridged; however, I have disabled bridging on the test2 site in order to eliminate that as a source of the differing behaviour. Disabling the bridging made no difference; the cpmfetch blocks still work fine in eFiction.
*Edit* Important additional note: I've switched the
http://test2.calic0cat.net/efiction site over to PHP 5.2.1 without encountering any errors, which shoots my PHP 5 theory all to heck.
Otherwise, I only have the obvious question... does the table it says does not exist really exist ??
It looks to me as if, in lonebard's case (and that of another eFiction user experiencing the same issue), eFiction is looking in the Coppermine database instead of in the eFiction database. Why this issue crops up for them when it works fine for me, I don't know and I've run out of ideas to try.