roller-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "user" <>
Subject RE: Re: What is the legal way to add new images into the custom theme and articles?
Date Sun, 12 Jan 2014 21:34:14 GMT

Thank you Glenn for your quick and descriptive answer. As I have understand from your answer
the legal way of referencing to "Media Files" content from articles and from custom themes
is to use link (URL) shown on "Media File Editor" window, isn't it?
If so, I have got two questions:
1) The link is looks like "cb06345c-1202-4c46-bbbe-a95c9f1fb004" and this is almost unreadable
by user. So if I have several images included in the editable article I can become confused
during editing by what each link actually means. Is there any way to address images by the
value of "Name" field which is present in "Media File Editor" or any other user-friendly view?
2) What is the actual dedication of "$url.resource" method which is described in the template
guide as "String URL of uploaded file resource in weblog"?

> Пн. 13 янв. 2014 00:29:25 пользователь Glen Mazza (
> Greetings, the theme management files (including images) are kept 
> separately from Media files.    (Our Media File implementation is actually 
> much newer than the themes.)    Normally, you would just place the new 
> images in your theme's images folder, like here for fauxcoly: 

> and reference them as fauxcoly does, and rebuild Roller.    We have many 
> other themes listed in the Links to non-Apache resources here: 
> <>

> that may be able to provide other ways to reference images into your 
> custom template.
> You can link to media files from your templates, but you would need to 
> use the Media Files URL given to you once you add the graphic into your 
> Media Files, as I do with my company's logo on my blog ( 
> - not part of the theme, but shows up due 
> to the image link.)    If you choose to go this route, you'll want to do 
> template modifications after you create your blog with your custom 
> template (using Roller's template modification screens all bloggers are 
> provided with), after getting the Media file URLs.
> It depends on what you want to do.    If this graphic is something that 
> will change from blogger to blogger, let each blogger use Media files to 
> incorporate what he wants; if this is a graphic that will be the same 
> for all bloggers using your theme, don't use Media Files but just 
> incorporate it into your theme's image folder.
> Glen
> On 01/12/2014 02:31 PM, user wrote:
> >
> > Hello fellows! First of all thanx to all developers and customizers of 
> > this well-designed open source web application.
> > What I'm trying to do is to add an image into my custom theme.
> > First of all I have created a copy of "fauxcoly" theme and then 
> > started to study it's content. In "Media Files" chapter of my weblog I 
> > saw the folder named "icons". In this folder I saw the file named 
> > "asf-logo.png". In "Templates" chapter in the template named 
> > "standard_footer" I obtained the following tag:
> > <img src='$url.resource("icons/asf-logo.png")' border="0" alt="Apache 
> > feather" />
> >
> > And on the rendered web page I see the link related to this tag:
> >
> >
> > So I decided to link my uploaded images from my custom theme either by 
> > "$url.resource" method or by direct link:
> >
> >
> > Then I add the image named "asf-logo.png" from Tomcat's "webapps" 
> > folder using "Media Files" chapter of admin UI. I preserved the 
> > current filename ("asf-logo.png") and assigned the folder "images" for 
> > it. So I have got two identical files: one in the directory named 
> > "icons" and another in the directory names "images". Then I'm trying 
> > to access new uploaded file by the url:
> >
> >
> > And get 404 error, although the initial url works OK:
> >
> >
> > Accessing file by the model object "$url" don't work either.
> > What I do wrong? Why is so different behavior for user uploaded files 
> > and files copied automatically from default theme?
> > Tested on 5.0.1 and 5.0.3 under Tomcat 7.0.27 under OpenJDK 1.7.0_25
View raw message