mysource-3.8.1/
mysource-3.8.2/
mysource-3.8.3/
current -> mysource-3.8.3/
Our Apache alias point to current/data etc…
I am still hoping that there is a way to get the file repository to always use the symlink ‘current’, making any upgrade procedure easier but currently it doesn’t seem to work.
In that regard I am open to suggestions. I’m on Solaris. I recently noticed ‘pwd’ gives different results depending on the shell used, so it may be due to something along those lines. (Plug: Other related post)
Anyway to the main point of the post.
I still get:
[512:mysource warning][R] ([system root]/core/lib/file_versioning/file_versioning.inc:207) - File Belongs to different Repository [FVER0008]
Mostly for designs.
The system_move_update.php is a great script but unfortunately it does require the old system root. And this is where I’m not positive I’ve got an old consistent one. Running system_parse_designs.php gives warning that my design belong to a different repository.
I’m planning to do an `grep` and check what the values of the dir= variable is. So my main question is:
1/ What is the value I should see? This question make more sense in the plural: what values? Is it different depending on the asset type and public/private/file_repository?
2/ Where are those files supposed to be? As in: if my design is live-public read, is it supposed to be in data/file_repository, data/public, data/private? Multiple occurences?
3/ Same question for a std binary (image or pdf)?
Thanks in advance.
Cheers.
PS: this post may be better in ‘Developers’, i’m not sure.
I recently had the same problem with error messages about repositories.
The problem was that the system root had a symbolic link in the path. Somehow the files got either one of the two paths as the repository path.
It might be some problems with this running with symlinks.
So when I did a run with the script system_move_update.php I had to run it for one of each path. In other words I had to run it twice to get the repository path to be changed.
I recently had the same problem with error messages about repositories.
The problem was that the system root had a symbolic link in the path. Somehow the files got either one of the two paths as the repository path.
It might be some problems with this running with symlinks.
So when I did a run with the script system_move_update.php I had to run it for one of each path. In other words I had to run it twice to get the repository path to be changed.
I already reported a bug regarding symlinks and the dir= (#1420). Basically if the Matrix folder is symlinked, it seems that the data/private gets the symlink path, but when the asset becomes live/public it gets copied to data/public and the dir= there is actual real path.
When you say you ran the script for each path, do you mean that now your dir= is consistent across both data/private and data/public? Is your matrix folder symlinked (I guess you have multiple clients so: Are any of your matrix folders)?
My current problem is that given what happens with bug #1420, I don’t know what the correct value in those dir= should be set to.
