-1 Old path support is built into Roller so that the huge number of resources that were uploaded before this change would not go 404. We definitely do not want to remove that.
The ability to edit the original path is a very useful feature that allows you to set a URL for a resource and avoid using the ugly one that Roller generates. Rather than remove it, I would rather see default to "true." It's trivial to support and if you don't like it, you can turn it off. - Dave On Mon, Jul 21, 2014 at 11:38 PM, Glen Mazza <[email protected]> wrote: > Hi team, a property in our roller.properties I think we can get rid of now: > > # Allow users to edit the original path setting of media files > mediafile.originalPathEdit.enabled=false > > Its only use is in MediaFileEdit.jsp: > > <!-- original path from base URL of ctx/resources/ --> > <s:if test="getBooleanProp('mediafile.originalPathEdit.enabled')"> > <tr> > <td class="originalPathLabel"> > <label for="originalPath"><s:text > name="mediaFileEdit.originalPath" > /></label> > </td> > <td> > <div id="fileControldiv" class="miscControl"> > <s:textfield name="bean.originalPath" size="30" > maxlength="100" tabindex="3" /> > <br /> > </div> > </td> > </tr> > </s:if> > > This was related to the switch from simple file uploads to the new Media > File functionality which occurred from 4.0 to 5.0. An "original path" URL > was retained to allow the older-type URLs to remain within blog entries, > instead of requiring them to switch to the new cryptic URLs used by Roller. > Roller will still read the old URLs to identify an image if necessary, but > I think by this stage, we don't need to allow people to change the old URLs > -- let them switch to the new URLs used by Roller if they have a problem > viewing any image? > > Thanks, > Glen >
