For quiet some time I am running a wikidot (v1) on my server.
I recently dated my version up from rev 266 to 463 (and did updates two times before this).
A new post-update-created Wiki gives now an error in the following situation:
I upload an Image (or some other file, but let us think in an jpg file).
The upload works.
I try to direcly access the file in the "files" menu, giving me the list of attatched files => Error!:
Notice: Class PrivateFileFlowController not loaded. in /var/www/wikidot_r463/lib/ozone/php/core/autoload.inc.php on line 64
Fatal error: Class 'PrivateFileFlowController' not found in /var/www/wikidot_r463/web/private_file_filter.php on line 30
Checking this in a pre-update-existing Wiki, I now get the same error if I try to access the file by the "files" menu.
BUT: I do not get an error if I upload a file and use/embedd it with the image command in the page content. The image correctly appears in the page. (For old embedded images and for newly uploaded ones!)
Hmm, back to the post-update-created Wiki, trying the image command:
No! This works not inside the post-update-created Wiki. Using the image command here does not provide the above error, but the image is simply not shown.
Something is rotten in the state of Denmark ;-)
This error is much too deep in PHP for me. So I need some help.
The versions beyond 463 did change very much (at least at the time I did the update).
So I got (in this forum) the recommendation for rev 463.
Hopefully, there is any solution that does not require an update to the latest revision (?!)
(I did take a look in the web/private_file_filter.php. It does not very much. It e.g. includes the php/setup.php. There it does not much but invoking a require_once on some other files, e.g. php/utils/GlobalProperties.php. Probably it is a configuration problem, caused by the update? That I do not provide a new configuration item, that was not necessary before… Against this theory would stand that I manually reconfigure the conf/wikidot.ini based on the new template with the settings from my old version during each update procedure. So the configuration should? not cause the problem… I could post the config, if necessary.)