We have moved to Github. Please open tickets there.

Opened 23 months ago

Closed 21 months ago

Last modified 20 months ago

#3662 closed Defect (fixed)

changing the favicon requires overriding the page/elements/head view

Reported by: cash Owned by:
Priority: normal Milestone: Elgg 1.8.0
Component: Core Version: Github Master
Severity: minor Keywords:
Cc: brett@… Difficulty:

Description

This seems like a big deal to me

Change History (11)

comment:1 Changed 23 months ago by ewinslow

Yes, that seems silly. Perhaps would be good to have a elgg_register_meta function that adds arbitrary <meta> tags to the head?

Incidentally, this would be another good use case for the "page entity" concept -- since we could then register a "description" tag pretty easily.

comment:2 Changed 21 months ago by brettp

@Evan - Can you refresh my memory about the "page entity" concept?

This would actually work really well with the menu system's model, if it we hadn't pigeon-holed it only for menus...

comment:3 Changed 21 months ago by ewinslow

page_entity was my idea for those pages whose main content is from a single entity in the system. page_owner is for contextual information (so we know to display a certain icon/menus in the sidebar or something). page_entity is also like that -- perhaps useful for displaying sidebar modules that have information/actions related to the entity currently on display (e.g. a blogpost).

It's not critical to this ticket by any means.

elgg_register_meta seems like a good idea to me -- allows us to do things like elgg_register_meta('description', $entity->excerpt) or whatever.

comment:4 Changed 21 months ago by brettp

Well, I agree elgg_register_meta() is a good idea and went ahead and added it.

That said, the shortcut icon uses <link rel="SHORTCUT ICON"> instead of a meta tag.

comment:5 Changed 21 months ago by Brett Profitt

  • Resolution set to fixed
  • Status changed from new to closed

Fixes #3662. Pulled out shortcut_icon to its own view for easier overriding.

Changeset: 647cadfb03e7a1a837c483d437de690231404fcd

comment:6 Changed 21 months ago by ewinslow

elgg_register_link? :)

comment:7 Changed 21 months ago by brettp

JS and CSS are already there, so I did think about that. Right now I moved it out into its own view since I think it's probably the only non-JS or CSS use of link most people would use. Know of any more that might benefit from more rel = "whatever" registration functions?

comment:8 Changed 21 months ago by brettp

I suppose we could just abstract out the elgg_register_external_file($type = "SHORTCUT ICON") then use the type as the rel param. Any consequences here?

comment:9 Changed 21 months ago by ewinslow

elgg_register_link could also take over the RSS/Atom/JSON/FOAF alternate view registration that happens automatically.

I'll just say that I'd prefer the semantics to be more 1-1. any $type parameter should probably set the [type] attribute on whatever is being registered. Confusing for $type to set [rel].

comment:10 Changed 20 months ago by cash

Discussion on this died out...do we want a new ticket on a general way to add links to support favicon, RSS, etc. in a more general way?

comment:11 Changed 20 months ago by brettp

Yeup. #3851

Note: See TracTickets for help on using tickets.