Potential Evolution 1.0 bug -- settings mismatch for File Browser / File manager

I’m getting a peculiar error with the first 1.0 install we’ve done at my office. When moving previous installs from a local environment to a live server, we discovered that a filepath setting in assets/cache/siteCache.idx.php would carry over from the local install, causing an error with the Image and file browsers. We could fix this by editing the value of $c[’rb_base_dir’]. This bug appears to be fixed in 1.0, but we are now getting similar errors which are dependent on the value of $c[’filemanager_path’], about 20 lines below rb_base_dir. It’s proving rather tricky, as the file manager says that most of the logical options for that path are invalid. Has anyone else run into this?

I should mention that "filemanager_path" is set automatically through the site configuration dialog option "File Base Path:", which directly edits "rb_base_dir"

When editing the Configuration to correct the paths in the Interface and Features tab and the File Manager tab, on saving the configuration the cache should be re-written. You should never have to directly edit the cache file.

I want a tiny button near the path input.
"Detect path"
Moving from local environment will be much easier.

Quote from: Paprikas at Aug 29, 2009, 01:03 PM

I want a tiny button near the path input.
"Detect path"
Moving from local environment will be much easier.

JIRA that ... good idea (especially if accompanied by a patch!).

I’ve also thought that the upgrade mode should take care of this; if it can change the default manager theme it should be able to update the paths.

Quote from: sottwell at Aug 29, 2009, 02:50 PM

I’ve also thought that the upgrade mode should take care of this; if it can change the default manager theme it should be able to update the paths.

But I think this cannot be automatic, as there are situations where those paths should not be changed. It would be best to make it an installation option triggered by a missing directory specification or some kind of interaction when the manager is loaded immediately after upgrade (though the installation option would ensure it is done before the cache is cleared, making it possible to upgrade more smoothly especially if your site is live during upgrade).

Quote from: sottwell at Aug 29, 2009, 03:19 AM

When editing the Configuration to correct the paths in the Interface and Features tab and the File Manager tab, on saving the configuration the cache should be re-written. You should never have to directly edit the cache file.

We’ve had to edit the cache file directly because setting the correct path through Configuration either didn’t set or didn’t correctly set the other paths I’ve mentioned. That’s the current problem -- we can set the appropriate path through Configuration, but the value used by FCKeditor is invalid.