Hello,

i just stumbled onto this module but am having a few problems getting started. I hope it is something I am doing wrong but I apologize if it is noob thing or something easy.

I am trying to use files: in the site logo box under themes. I noticed that the Input Format paged said that it had to be in quotes so I have in the box (the middle one where you type the location) "files:logo.png". The problem is that it gets changed and I have this as my img src, src="/sitename/&quote;files:logo.png&guote;". I thought that it may be the option for automatically setting internal to attributes but it does the same thing either way.

This is the only module that I have downloaded so far and I have only activated a few of the core ones so I'm not thinking it would be a conflict in modules. If you could point me in the right direction I'd greatly appreciate it as this looks like a very nice feature that I would love to use.

Thanks,

-matholum

Comments

vm’s picture

vm commented
Title: Probkem using files: for site logo » Prolkem using files: for site logo
Category: bug » support
Status: Active » Fixed

not sure what this module has to do with your issue.

in administer -> themes -> configure
you don't use quotes or an input format to upload a logo in the admin ui.

As a test to ensure that this module isn't "conflicting" disable it. If you still have the same issue it means it has nothing to do with this module and you should likely create a forum thread in the post installation forum explaining in more detail what you are trying to do, where you are trying to do it.

vm’s picture

vm commented
Title: Prolkem using files: for site logo » Problem using files: for site logo
matholum’s picture

matholum commented

Well, I would think it would use it. Otherwise I would still have to go a full path the the files directory. I thought that this enables me to skip that part of it...

matholum’s picture

matholum commented

Also, I wouldn't disable this module as it is what I am trying to use. If I disabled it then I would know for sure that files: would not work...

matholum’s picture

matholum commented
Status: Fixed » Active
vm’s picture

vm commented

my reading of the readme.txt included in the module folder and the project page tells me this is supposed to be used directly in a content, therefore directly in a node and not in administer -> themes -> configure -> path to custom logo. Filters and input formats only work on nodes/content creation. A logo isn't a piece of content nor a node. My assertions above come from the quoted part of the readme.txt below.

quoted from the readme.txt file:

The motivation for this filter was to provide a robust way of linking to
internal URLs from within content

Also of note: administer -> themes -> configure -> path to custom logo is expecting only a path and not any HTML at all. Therefore using the img tag in this area isn't going to work as expected. Which is also why an input format can't be chosen for this field.

Could you please point out some form of documentation that states this can be used in setting the logo for a theme in the admin ui? outside of content/node creation?

I'd also take the time to consider that it is likely best to put your logo in your theme folder replacing the logo that is included in the theme itself which keeps your entire theme modular.

Hopefully the above better explains how this module was intended to be used. Feel free to mark this issue as fixed.

matholum’s picture

matholum commented
Status: Active » Closed (fixed)

I think I get it... I tried looking it up some more too. I think that is the main part. I was thinking that the text box would be affected just like content creating but for some reason it isn't.

The img tag I was talking about was the actual source when looking at the page to see what it was doing, not what I was typing in. It would be nice to enter the files: there but I think the better option is to just have it as the default of the theme and always do it that way. Although theoretically if you wanted to use, say Garland, and have your own logo you'd have to type the entire path in. That is where it'd be nice to type files:logo.png instead of /sites/example.com.path/files/logo.png. (yes, I am using a multisite which is why I wanted the feature).

Anyway, if for some reason it doesn't do text boxes to then that stinks. Maybe in the future that'd be a good option but if not oh well...

Thanks for the help,

-Matholum

vm’s picture

vm commented
Status: Closed (fixed) » Fixed

it's a set it and forget it field for the most part that I'd bet few people actually use even when using a multisite as a logo is part of a theme. Personally, I'd prefer core remove the field from the admin ui altogether as its really unnecessary at this point.

Custom themes, even those where one manipulates a core theme like garland, should be copied and created separate from the core theme.

WRT to issue status the proper thing to do is mark issues fixed. After two weeks they shift to closed only their own.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.