Untitled

The following is a step by step guide to customizing your Firenzie logo image by replacing the logo text with your own organization or company's name and logo.

In order to utilize the Fireworks Source PNG included with the Firenzie template release, you will need Adobe Fireworks. The 30-day free trial of this software as well as more information is available here at the Adobe website.

Customizing Your Logo

One of the first steps of customizing your new Firenzie template will undoubtedly be altering the logo text to reflect the name of your company / organization. RocketTheme makes this process a simple one by including both the Source PNG for the template, as well as font(s) used.

The most effective way to customize the logo is to use the included Source PNG file. When opened in Adobe Fireworks, this file contains all of the Layers in the design allowing you to tweak and change any of the image elements of the template design. The following steps will help you quickly get your new logo ready to go:

• Step 1
  
  First, open the main Source PNG file in Adobe Fireworks (firenzie_source.png). On the right side, you will notice a taskbar named Layers. Inside this column, a list of elements within the source will appear, dividied into folders. The first is Web Layers which controls the green slices on the page that are used to export the images. Click the eye which is immediately left to the folder name Web Layers to make it invisible. This allows use to edit the logo.
  
  
• Step 2
  
  Next, double click on the logo which should be position in top-left. This will activate the text tool so you can edit the element. Highlight the entire text box with your cursor and type your text instead(such as your company name.)
  
  
• 
  
• 
• 
  
• 
  
• We do the same for the text underneath, double click on this text which should be situated below the logo.. This will activate the text tool so you can edit the element. Highlight the entire text box with your cursor and type your text instead(such as your company slogan.)
  
  
• Step 3
  
  Since the new logo text is larger than the slice, we much make the slice larger. Left click and drag on the right corner to the new dimensions. However, you will notice that the slice masthead-bg now overlaps the logo, simple left click and move to the right so it is no longer overlapping. We now must reactive the web layers/slices to be able to export the logo out of Fireworks. Back in the right taskbar, click the empty, white cell next to the web layers folder where the eye was visible before. This will activate the eye icon and the green slices on the source screen.
  
• 
  
• Step 4
• 
  
  Right click on the green slice that is situated above your new logo. A popup menu should appear with numerous options. The value we want to deal with is "Export Selected Slice...". As the name suggests, this option will export/save this slice only out of the entire source window. You will be sent to a another window where you need to save the slice onto your local computer.
  
  

Uploading your Logo

Once you have successfully edited then exported your new logo, you will need to upload it to your server. This process is best done via a FTP client such as Filezilla

1. Open your FTP client on your local computer.
2. Login to your web server where Firenzie is installed.
3. Navigate to the /templates/rt_firenzie/images/style# directory.
4. Upload logo.png to this directory (You may need to browse on the local panel in the FTP client to find where you have exported your logo).
5. Clear your browser cache before viewing such as using the keyboard commands on Windows, Ctrl+F5.

Ensure that you are uploading the correct logo to avoid confusion if it does not change. Also take into account hosting permissions. Sometimes, hosters which are not designed for Joomla may have permissions not suited for the setup, thus, the upload will not be complete. In this case, contact your hosting provider.

Blogged with Flock

Jommla Security

1. Kurulu Joomla! eklentilerini kontrol edin, güvenlik riski taşıyanları kaldırın.
2. Gereksiz modül, bileşen ve mambot türü eklentileri kaldırın.
3. Dizin, dosya ve klasörlerinizin CHMOD ayarları kontrol edin ve güvenli olacak şekilde değiştirin.
4. Mümkün olduğunca kullanıcı tarafından yüklemeleri (upload) kapatın veya sınırlandırın. yüklemelerin özel bir klasörde toparlanmasını sağlayın. Tüm yüklemelerin güvenlik uygulamalarıya taranabilmesini sağlayın. (Bunun için virtual private server veya dedicated server gerekecektir!)
5. Maddi imkanınız el veriyorsa dedicated server kiralayın veya kendi sunucunuzu güvenilir bir data center da barındırın!
6. Unix tabanlı bir sunucu tercih edin.
7. Apache ve PHP yapılandırmalarını güveliği sağlayacak şekilde düzenleyin.

Joomla! 1.0.13 kurulu bir siteye index atmak suretiyle saldırı gerçekleştiriliyorsa buna olanak sağlayan 3. parti bir eklenti kullanıyorsunuzdur!

Sunucu kayıtlarını (log) kontrol edin, saldırının yapıldığı tarih ve saatte siteye erişim sağlayan IP leri tespit ederek yasal işlem başlatın

Blogged with Flock

UTF-8 issues in Joomla 1.0.x series - a guid

Is there a workaround to apply utf-8 in Joomla 1.0.x series?
Yes. Here is a quick guideline to getting Joomla 1.0.x to work with utf-8
- use MySQL version 4.1.2 or newer (older versions don't support utf-8).
- create an empty database manually before installing Joomla. Set the character set to utf8 when creating with some collation (utf8_general_ci is the default and should be OK).
- convert the language files to utf-8 (all language files including for editors, components etc.). Make sure NOT to save with the utf-8 BOM header option.
- Install Joomla using the pre-existing database. After installation check that the database has utf8 encoding for all text fields (just in case Joomla created a new database and is not working on the pre-created one).
- set 'charset=utf-8' in the _ISO define in the language file
- You should uncomment one line of code in the includes/database.php file at about line 102 (second line below)

Code:

$this->_table_prefix = $table_prefix;
//@mysql_query("SET NAMES 'utf8'", $this->_resource);    // THIS IS THE LINE TO UNCOMMENT
$this->_ticker = 0;
$this->_log = array();

Please note that the above does not make Joomla 1.0.x fully utf-8 compatible. All string functions will still be using singlebyte character functions. This works well in most cases (no guarantees). There will be some instances of garbage characters especially with diacritic Latin characters and logical error in searches and filtering features.

Blogged with Flock

Joomla International (Turkish)

Joomlayı kurdunuz ancak bazı karakter sorunlarınız var. Ne yapmalısınız?

1-Öncelikle Joomlanın dilini Türkçe yapmalısınız. Bunun için Site Genel Ayarları ndan Yerel sekmesine gelin:

Dil: Türkçe

Ülke Yereli: tr_TR olmalıdır. Tabi bunun için sürümünüz içinde Türkçe dil dosyası bulunmalıdır.

Bu ayar sonucunda sitenize eklediğiniz tüm bileşenlerde default dil olarak Türkçeyi arayacaktır. Eğer bileşenin Türkçe dil dosyası yoksa ingilizce çalışacaktır.

2- Temanızın index.php dosyasının en üstünde;

<?xml version="1.0" encoding="iso-8859-1"?>  satırını
<?xml version="1.0" encoding="iso-8859-9"?>  ile değiştirin.

3- Türkçe Dil dosyası içindeki turkish.php dosyasının üst satırlarında

<?php header ("Content-Type: text/html; charset=ISO-8859-9"); ?>   satırının olduğundan emin olun.

4-Bileşen, tema veya modüller kurulduktan sonra karakter hataları veriyorsa;
Kurmadan önce zipleri açıp; xml dosyasının en üst satırında:

<?xml version="1.0" encoding="iso-8859-9"?>  olduğundan emin olun.

5- Veritabanı işlemlerinde de her zaman latin_5_turkish_ci  seti kullanmaya dikkat edin.Böylece büyük- küçük harf hassasiyeti olmayan karşılaştırma seti kullanmış olacaksınız.

Blogged with Flock

Internationalization Tips For Your Joomla Website -Part One-

Characters not dispaying correctly?

     

The most probable reason for this is that you have an encoding mismatch in your site. This should be checked and possibly corrected before you start changing server default charsets, languages or database collations which usually never need to be touched.

An Encoding Mismatch means that your browser is not using the correct codepage to display special characters (extended ASCII) and they show up as something unexpected.

Alternately you may currently have the correct encoding in your browser but at some time in the past there was an encoding mismatch while data was inserted via a browser. This too will create unexpected results of special characters.

How to check this?

• Find out what the correct encoding is for the language you are using in your site. As an example let's take Czech which uses iso-8859-2
• Open a page of your site in your browser and ensure that the browser is set to automatically detect encodings
• The browser should have detected iso-8859-2 which is also known as "Central European" encoding

If you got this far and and the browser is selecting encoding as expected but there are still bad characters then there are two possible problems:
1. If the corruption is in text that is part of content - this might have been inserted during some mismatch in the past. Try to insert some new text and see if it is OK.
2. If the corruption occurs in User Interface labels, then perhaps the language file you are using is for utf-8 use only. You should change the language file with one that was prepared for singlebyte encodings such as iso-8859-2.

If your browser did not select the correct encoding automatically then please check the following:

• In your browser click on the menu item that displays the source of the currently displayed page. In the code near the top in the header tags you should find the following line for Czech encoding:

Code:

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2" />

• If you see a different charset value then you need to check your language file define for encoding as this is taken from there. You should open the language file (<lang>.php) in an editor and search for '_ISO'. You should see

Code:

DEFINE('_ISO','charset=iso-8859-2');

• If the language file define is correct but something else shows up the page source code - then there is a problem with the template that you are u

  The most probable reason for this is that you have an encoding mismatch in your site. This should be checked and possibly corrected before you start changing server default charsets, languages or database collations which usually never need to be touched.
  
  An Encoding Mismatch means that your browser is not using the correct codepage to display special characters (extended ASCII) and they show up as something unexpected.
  
  Alternately you may currently have the correct encoding in your browser but at some time in the past there was an encoding mismatch while data was inserted via a browser. This too will create unexpected results of special characters.
  
  How to check this?
  
  

  • Find out what the correct encoding is for the language you are using in your site. As an example let's take Czech which uses iso-8859-2
  • Open a page of your site in your browser and ensure that the browser is set to automatically detect encodings
  • The browser should have detected iso-8859-2 which is also known as "Central European" encoding

  
  If you got this far and and the browser is selecting encoding as expected but there are still bad characters then there are two possible problems:
  1. If the corruption is in text that is part of content - this might have been inserted during some mismatch in the past. Try to insert some new text and see if it is OK.
  2. If the corruption occurs in User Interface labels, then perhaps the language file you are using is for utf-8 use only. You should change the language file with one that was prepared for singlebyte encodings such as iso-8859-2.
  
  If your browser did not select the correct encoding automatically then please check the following:
  

  • In your browser click on the menu item that displays the source of the currently displayed page. In the code near the top in the header tags you should find the following line for Czech encoding:

  Code:

  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-2" />

  • If you see a different charset value then you need to check your language file define for encoding as this is taken from there. You should open the language file (<lang>.php) in an editor and search for '_ISO'. You should see

  Code:

  DEFINE('_ISO','charset=iso-8859-2');

  • If the language file define is correct but something else shows up the page source code - then there is a problem with the template that you are using. A different, standard, template should be tried
  • Remember that if you wish to use Czech (for example) in your content while still keeping the original English language file for the site User Interface - then you should change the _ISO define in the language file from iso-8859-1 to iso-8859-2
  • For utf-8 related issues please see a separate sticky thread in this board

  
  ===================================
  
  If you are still having problems - don't start slashing your wrists - just place a post in this board with as much details as possible. Mainly please detail:
  

  • What language do you wish to display
  • What encoding does the browser select
  • Where are the problematic characters? In content or in User Interface labels?
  • What do you see in the charset value of the page source?
  • What is set in the language file define for '_ISO'?

  
  sing. A different, standard, template should be tried
• Remember that if you wish to use Czech (for example) in your content while still keeping the original English language file for the site User Interface - then you should change the _ISO define in the language file from iso-8859-1 to iso-8859-2
• For utf-8 related issues please see a separate sticky thread in this board

===================================

If you are still having problems - don't start slashing your wrists - just place a post in this board with as much details as possible. Mainly please detail:

• What language do you wish to display
• What encoding does the browser select
• Where are the problematic characters? In content or in User Interface labels?
• What do you see in the charset value of the page source?
• What is set in the language file define for '_ISO'?

Blogged with Flock

Google Analytics Tracking Module

Google Analytics Tracking Module
Google Analytics Tracking Module is a simple module for Joomla! 1.0.x. and Joomla! 1.5 (legacy mode) used for inserting Google Analytics tracking code to the Joomla site as a module.

This module makes it possible to add the tracking code before the closing body tag in template, which is recommended by Google. Module tracks all pages of Joomla cms including 3rd party components.

Module track also Virtuemart transactions. Supported payment methods are at the moment: Paypal, Cash on delivery, credit card and purchase order.

Features

• The use of ssl is optional
• subdomain tracking is optional
• user tracking with __utmSetVar is optional
• VirtueMart E-commerce Tracking
• Setting Joomla! registration as a Google Analytics goal is optional

Free Joomla! templates -
 Estime Templates - Modules for Joomla! CMS

FAQs about Google Analytics Tracking Module

No parameters in the module settings After installation I only have one big block for setting parameters and not the options, like UA tracking code ets." Please check, that you have write permission to your module. Why this is module and not bot? Bots are called within head calls, also bots are usually dependent on Joomla functions. Bots are therefore not downloaded for each page call. You can add module positions inside you templates, wherever you want. This makes it possible to add tracking code to every single page of Joomla, since modules are called from template, and template is downloaded for all the pages, yes, even for 3dp components such as virtuemart, docman, simpleboard etc. Common problems You don't have position called debug inside your template. The recommeded position for tracking module is debug position. This is usually at the end of the template. To check, if you actually have position you are trying to use, go to your admin panel. Select Site » template manager » module positions. If you don't have position called debug, it's ok, just select the position you have, like left or right. How to be sure, that the module is installed correctly? After installing and configuring the module, go to your site with your favourite browser. Choose View » Source (Page source) from your browser. Check, that you have the following code somewhere inside your html source. If you do, installation was succesful, if you don't, check the common problems list. I don't have position called debug It's a recommendation to publish the module before closing body tag, it's not a must! You can publish the module where ever you want to as long as you have that module position inside your template. As a Joomla cms administrator, you probably know, that you can list the module positions inside your template in the backend of Joomla by choosing Site > Preview > Inline with positions. Those are the positions your template holds. You shouldn't publish any modules to other places than the ones, you actually have inside template. All templates doesn't have all the default places, such as top, footer, debug, left, right, user3, user1 etc. You can add as many positions as you like by yourself with the Joomla backend by choosing Site > template manager > module positions. Type your position name in the list. You add the position to template by choosing site > template manager - site templates: select your template and choose edit html. You can add the positions like 'mynewposition' by adding the following code, where you want the module to appear.

Blogged with Flock