Update from 4.7 to 5.3
| Project: | Filemanager |
| Version: | 4.7.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I'm in the process of updating a site from 4.7 to 5.3 and am having trouble managing the file system. I belatedly realized that File Manager had been deployed in the 4.7 version.
What problems should I be looking for in the upgrade process? I understand that file management is changed considerably as I had all sorts of problems with the image assist module in the update process. I got all those working but am now having problems with a range of file types (pdf primarily that were attached on the old site.)
I can reach these files as administrator but not as a simple authenticated user. I guess what I'm really wondering is if I need this module to get at some permissions that were required on the 4.7 site that I don't have access to now because I don't have this module.
#1
If you used the Filemanager and Attachment modules, and the files in question are managed by these modules, then yes, you need to upgrade these modules. Nothing else will need to be done (assuming everything else is normal). Just pop them in there, and run the upgrade script. And make sure you don't have the core Upload module enabled.
#2
Thanks for the quick response...
I don't see an Attachment module in the old deployment. And core Upload is enabled in both the old and new deployments. So what kind of trouble am I looking for...
Just so you have a sense of the scope - - I didn't build the original site. A lot of things were tried and not used. My role has been to move from a prebeta 4.7 release that was taken into the production environment to a stable 5.3 release. We have about 4500 nodes (many with files and/or images attached). There are about 24,000 users - tripling in the six months I have been working on the project.
#3
Well, not knowing the site, I don't know what the problem could be. There's few projects that use Filemanager. Filemanager is just an API, and doesn't provide any end-use functionality at all. Attachment is the primary user of it, though at one point Acid-free used it.
If you don't have anything that uses Filemanager on the system, then you don't need it. And thus likely your problem is with the core Uploads module. You should be able to figure that out by looking at the settings for Filemanager and seeing where it puts files, if that's not where your files are, then clearly you're not even using it. If both Upload and Filemanager are set to the same place, then you've got a tangle that you might need to work out. If that's the case, I hope you know php... ;)
#4
I came to close the thread and tell you that indeed it proved to be settings within the image assist file after all - authenticated users needed to be able to access original files - imagine that *grin*
But now you raise the specter of acid-base which is where I am plunging in today. One of the main drivers of the upgrade was to allow much easier use of video on the site. We only had a hundred or so but supporting and managing it was proving difficult. Somehow Acid-base was being used to manage this. I'm closing the thread but you may hear from me again in that vein.
As to PHP/MySQL I can and I'm working to change that but I'm more of a CSS guy...