Joomla 1.5: Using my own favicon via template?!?

Well, there am I trying to convince joomla 1.5 to use my template’s favicon instead of the default jommla flower Original favicon of Joomla a.k.a. The Flower. But no matter what it wouldn’t let me replace it by my own. What I’ve done so far:

  • create the .ico file with Gimp, 32×32 (tried 16×16 also), 4 bpp 16-slot palette
  • placed it in ../templates/my_template/favicon.ico
  • reloaded page in browser

But still no favicon is shown in neither Opera nor Firefox under Windows.

Update: It seams I somehow used wrong colour palette, layer or whatever optioins. After I uploaded a png file to FavIcon and used the result it at least shows in Firefox. Opera seams to chuck up on the HTML header created by Joomla:


<head>
  [...]
 <title>Welcome to the Frontpage</title>

  [...]
  <link href="/joomla/templates/div_template/favicon.ico" rel="shortcut icon" type="image/x-icon" />
  [... repeated multiple times somehow ...]
  <link rel="stylesheet" href="http://localhost/joomla/templates/div_template/css/template_css.css" type="text/css"/>
  <link rel="shortcut icon" href="http://localhost/joomla/images/favicon.ico" />
  <link href="/joomla/css/template.css" rel="stylesheet" type="text/css" />
</head>

As far as my understanding goes Opera doesn’t mistaken as to overwrite the earlier favicon.ico link with the later and hence (as Opera does) show the correct, i.e. intended favicon for a glimpse of a second and than show none as the /joomla/images/ one is not there. If I place a copy in that directory on the server Opera also shows the icon — I asume the wrong one though!

Well, anyway, now I know where the rub is…

Update 2008/05/08: I should have digged into templating a bit further and not just take it “as is”. Now in the html header of .../templates/my_template/index.php I just leave out the line where it points to the joomla template but rather only have one “shortcut icon” href as below:

<head>
	<jdoc:include type="head" />

	<link rel="stylesheet" href="<?php echo $this->baseurl ?>/templates/system/css/system.css" type="text/css" />
	<link rel="stylesheet" href="<?php echo $this->baseurl ?>/templates/system/css/general.css" type="text/css" />

	<link rel="stylesheet" href="<?php echo $this->baseurl ?>/templates/<?php echo $this->template ?>/css/layout.css" type="text/css" />
	<link rel="stylesheet" href="<?php echo $this->baseurl ?>/templates/<?php echo $this->template ?>/css/typography.css" type="text/css" />
	<link rel="stylesheet" href="<?php echo $this->baseurl ?>/templates/<?php echo $this->template ?>/css/browserhacks.css" type="text/css" />
	<link rel="shortcut icon" href="<?php echo $this->baseurl ?>/templates/<?php echo $this->template ?>/icon/favicon.ico" />
</head>

Learning CMS — Finding the Right System for Small Business Needs

For a small business pharmacy shop looking to presenting themselves with a small website I’m aiming at a web CM system that integrates the following:

  • Content should be edited via a highly configurable, yet minimal rich text editor so there is no difference to writing text in Word with even less function offered (only predefined CSS-Styles for title, paragraph, etc.). No need of code view.
  • Possibility to save as draft or direct publishing and therefore some sort of (email) notification system.
  • Get access to that editor via the website’s “frontend” (FE), i.e. in-line editing — showing a pen marker at the position that could be edited right in place by the logged-in user, similar to the wiki stuff — so there is no backend for the ordinary user.
  • For the administrator (web designer, … someone more technically minded) there should be some sort of backend for user management, reviewing drafts to be published, configuring the rich text editor (could be done “externally” on the system file level).
  • News handling: Basically able to set date to publish and expire per entry/article. So writing of news articles ahead of time becomes possible. Something like tt_news (see also manual) from typo3, could be far less complex.
  • Define roles per user, or more accurately define per document who can do what with it.
  • Separate content from formatting. Use e.g. CSS for formatting and store pure content in database with “meta” formats like header of css class xy.
  • Multi language support per document.
  • Versioning of articles.
  • Easy to use with public hosting services (I don’t want to have some old, noisy fan sitting in my living room; and buying a new hardware just for 2.0 MB of website? No way)

So this would be something in between of typo3 and a simple blogging system like wordpress or serendipity, I guess.

Read the rest of this entry »

Follow

Get every new post delivered to your Inbox.