File Managers - Replacing Files breaks paths
Permalink
Kudos on the File Managers ability to assign many categories to one file. Super helpful. However, there's one problem I can't seem to find my way around ... perhaps someone knows the answer for this ...
When I upload a file and then get a path to the File Managers, a path is generate automatically. Now, let's say I'm using that same file in 12 different places in a large site (not unusual for my clients).
When I use the file manager to do a "Replace" of that file, the path gets changed. In order to update that image in those 12 different locations, I have to edit each of 12 pages to update the path.
Is this really the only way to update or replace an image with File Managers? Is there some other way to use the File Manager so that when I update an image I don't have to replace the path everywhere that image exists in a site?
When I upload a file and then get a path to the File Managers, a path is generate automatically. Now, let's say I'm using that same file in 12 different places in a large site (not unusual for my clients).
When I use the file manager to do a "Replace" of that file, the path gets changed. In order to update that image in those 12 different locations, I have to edit each of 12 pages to update the path.
Is this really the only way to update or replace an image with File Managers? Is there some other way to use the File Manager so that when I update an image I don't have to replace the path everywhere that image exists in a site?
Thanks for the quick reply, and the introduction to Stacks. Stacks do work great for my question and great for any content that needs to be re-used in multiple places. In another system I worked on we called these "Content Objects".
you are able to place multiple instances of any stack with an image in it and then add css to each "stack display" block through the block design dialogue like "max-width: 100px;" so you should be able to manipulate the size on each page as well.
EDIT: as long as it's just an image in the stack. otherwise everything else will be scrunched as well!
EDIT: as long as it's just an image in the stack. otherwise everything else will be scrunched as well!
@enlil, I have never been able to get that to work properly. What do you put in the Design->CSS to limit the width of the images in that block?
Can you check it out when you have a moment.
Can you check it out when you have a moment.
For this example I used an image that is 600x325.
I created a stack called test image. In that stack I placed an image block. In the image block I simply selected the image and clicked save, leaving all other options alone.
Approve stack changes and return to page for placement.
I placed the "test image" stack twice in the page. Then in the design options for each of those "stack display" blocks on that page I entered into the CSS area: " max-width: 100px; ".
used "400px" for the second image see attachment
EDIT: screenshot x2 shows output...
I created a stack called test image. In that stack I placed an image block. In the image block I simply selected the image and clicked save, leaving all other options alone.
Approve stack changes and return to page for placement.
I placed the "test image" stack twice in the page. Then in the design options for each of those "stack display" blocks on that page I entered into the CSS area: " max-width: 100px; ".
used "400px" for the second image see attachment
EDIT: screenshot x2 shows output...
That's what I have been doing and it never works for me. Perhaps I've over-ridden the image block and broken something. I'll check it out. Thanks.
interestingly enough, i just tried this in Greek Yogurt theme and it doesn't work?! I'm taking some pokes at it but haven't found anything that works as of yet.
It does work for me in a flex1200 based responsive theme I'm building.
It does work for me in a flex1200 based responsive theme I'm building.
This seems like it's something CSS with Greek Yogurt. What themes have you tested on?
Lots of themes but never Greek Yogurt. It has issues of it's own and I learned never to base anything off of it.
http://www.concrete5.org/developers/bugs/5-6-1-2/greek-yogurt-throw...
I think it has something to do with CSS targeting ID's ahead of classes.
http://www.concrete5.org/developers/bugs/5-6-1-2/greek-yogurt-throw...
I think it has something to do with CSS targeting ID's ahead of classes.
Now if each of the 12 photos needs to be a different size then the Stack thing won't work because the image in the Stack can only be one specific size at one time. This will be the case until someone invents a Quantum Image Block.