Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By rajaito on
First let me apologize if this is a repeat topic. I have spent hours google searching and reading through tons of posts filled with techy jargon trying to get this figured out. If someone has already answered this question, please point me in the right direction. Please be patient with me, I am still a Drupal noob, but I am ready and willing to learn.
Modules being used: uploads, imagecache, imagecache profile, date with views (for events), and e-commerce
I started my site out set to public. Then I upgraded from Drupal 6.10 to 6.12 and also upgraded to the most current imagecache module. When I did this, all my profile photos disappeared! I posted a support request here: http://drupal.org/node/482630, but I have gotten no answers.
After days of research, I finally decided to press the files button to private. Yay my profile pics came back! But wait, where did all the other images go in my events and ec store? Aye!!!! So it seems, now imagecache profiles wants files set to private and everything else wants the site set to public.
I am at a loss as what to do. I have spent the last 9 weeks working on this site. I was almost ready to make it public when this happened.
I cant seem to find a simple answer for getting the site back all to public or private. Any suggestions would be great.
Sad as it sounds, but I am at a loss and I have thought about giving up on Drupal and going over to a lame install of word press. Please, please save me.
Comments
This does not help you, I
This does not help you, I know ... & sorry about your troubles.
... but hadn't you made any recent site backups prior to that upgrade?
Actually, it's normally advisable to make a backup before upgrades to be prepared for such unexpected turns, rare as they may be. In that case, you would simply go back & start again from there, but probably do a thing or 2 differently.
=-=
The reason you read a lot of techy jargon in threads about this issue is because there is no "setting" to fix it. you would manually have to go through the database and inspect every path as far as I can tell.
at this point a backup, as the previous commentor suggested is your best way to move forward
_
I'm afraid the other posters are quite correct-- there is no simple answer for fixing this and a backup is your best bet. Fwiw, in the future, when you see things like "Changing the download method will modify all download paths and may cause unexpected problems on an existing site." on drupal admin screens tread lightly and always make a backup.
sigh... I was afraid of that.
sigh... I was afraid of that. I did make a backup not that long ago using the backup module but I have no idea how to roll it back and I cant remember if it was right before or right after the upgrade to 6.12 (I supposed the backup should have been before the upgrade...)
Although, please keep in mind as I said earlier it was the upgrades that caused the problem. I only switched that private/public button for the first time after days of trying so many other things.
When I think about it, I might be willing to go through the database and change paths, if it were something that was pretty straight forward to look for. I don't actully have a lot of content on the site yet. Most of the time I have spent has been finding and installing the right modules and getting them to play nice together. Heck, I'd even be willing to strip the site of all its content at this point and start over, considering the amount of time I have worked on just getting the framework together. Is this a reasonable thought?
I dread the thought of starting over for a third time.
oh and by the way, I really
oh and by the way, I really appreciate your comments and help with this.
I don't actully have a lot of
When I made some community site with Drupal 5 & discovering some of the modules I had used where no longer supported for D6 + finding a theme which offered me more options, I had to make a decision whether to update & do away with content of the no longer supported modules, etc or simply try to do everything from scratch.
I chose the latter option, however the experience gained from customizing the different components made working much faster possible.
I also manually transferred the content, which was not yet much ... It was a big decision which I think has paid off in the long run.
It helped a lot to look at things posivitely. :)
A possible fix
It's a full solution, but this:
http://drupal.org/node/258099
should answer some questions.