Thanks for the hints at the April monthly meeting about how to handle images. Unfortunately, I encountered a snag following the suggestion of the "guy in the blue shirt".
The problem is that Configuration/Media/IMCE/Directories doesn't let you specify anything higher than , which turns out to be equivalent to the site name. For example, given the following directory structure "/sites/nimbleliving/files/...", IMCE defines the to be "/sites/nimbleliving".
The plan was to create another directory such as ".../sites/images" which would be a sibling of ".../sites/nimbleliving". We'd then store our images in ".../sites/images" on both the server and our local site. When we copied the restored the real database onto our local site, voila, all of the links would still work. But, alas, IMCE Wysiwyg Bridge can't see that high in the directory.
Does anyone know a solution that is within reach of a newbie? Is there a way to convince IMCE Wysiwyg Bridge to have a broader perspective?
Our fallback plan is to contact our hosting company and ask what it would take for us to convert our live site into a multi-site so that both our live site and local site would use the same path.
The fallback to my fallback is to lug my iMac to next month's meeting in the hopes that someone has an epiphany while looking at the UI.
Thanks.
Debbie
Comments
Insert module
I just thought I'd add that I tried uploading an Image using the Insert module but it has the same limitation. You can't insert an image in an area outside of the sites/site-name directory.
By the way, someone mentioned in the meeting about uploading images at the end of a process. I need to clarify. My site is dynamic - I upload images every time I add content, which would be every day if I had the time. In reality, it probably averages about every other day. I probably upload an average of 4 images each day though there have been days when I've uploaded a few dozen.
I used to transfer the images via FTP. That got old fast but now I'm wondering if my only option will be to punt by ditching IMCE, FTPing the files each day and just hand-coding the html. The major downside of this approach is that I was hoping to work with a partner on this web-site and there's no way that she'd be able to do this.
Debbie
I think the "guy in the blue
I think the "guy in the blue shirt" is Dustin Currie. :D
Jay Lee
https://jay.lee.bio
Make sure your files directories match
Check that the settings for public files directories[/admin/config/media/file-system] match on both sites. If they're both looking in a different place, there's the problem. You can move your files directory anywhere, and the simplest place for your situation might be in the webroot, although if you change it now, all your content will still have the old paths until it gets re-saved. Another alternative would be to set the files directory on your local instance to match what's on live, but since this is a database setting, it'll get overwritten whenever you sync your database down to your local...unless you define your files directory in a conf variable in your settings.php. Try something like this in settings.php...
$conf['file_public_path'] = 'files';
//make sure this directory exists if trying this method
OR
$conf['file_public_path'] = 'sites/default/files';
If it doesn't fix all the problems right off the bat, test it with some new content, and the older paths may remain persistent in the DB.