Date: 7/11/2006 1:35 am · Subject: Image Management
One of the biggest issues we have with the current WebGUI is image
management. We have a number of stock images that we use throughout
our site, and occasionally we want to update them. We don't want to
have to change every single one of them though, we'd prefer just to be
able to change the stock image - any pages using that image should then
use the new image accordingly. For example: you have a number of webpages with your company logo on them. Your company changes name and you need to update the images. You don't want to have to edit every single page on your website to do so - you just want to change the image object. The problem is that the editor doesn't respect the webgui objects and instead of linking to the image object, it bypasses it and goes straight to where the image is stored on the hard disk. (ie. in /uploads/xxx/xxx/xxx.jpg). What
this then means is that if the collateral image changes, then none of
the articles that use that image update at all. The option:
"enableStreamingUploads" : "1"
This will apparently make it so that if the webgui url is referenced (ie. /path/to/image.jpg) then it will return the image instead of redirecting to: /uploads/xx/yy/xxyy32399333/image.jpg Which seems half way - but the tinymce editor still puts in /uploads/xx/yy/xxyy32399333/image.jpg when you use the 'Add Collateral Image' option even with this turned on.
If there was some way to get this to use the object url (ie. /path/to/image.jpg) instead then combined with the previous option would solve the problem. It would then mean users would have the flexibility of being able to add collateral items into articles using the editor, while also providing the ability for those collateral images to be updated at a later date (and all pages using those images would change). Jesse
|
