Page titles don't show right Options

[Evil Agent]

Hi,


When I'm tracking pages and set the reports to show page titles, some pages don't show up correctly because of wrong encoding. For example:

CODE

Músicas de Anúncios

Shows up as:

CODE

Msicas de Anncios

I'm running v3.0

[Squirrel]

I'm suffering the same problem with version 3.1.1. I use both utf-8 in tracking site and publisher site but the page titles seem to appear in wrong characters.

Cannot believe that an open question is still fresh without any hint or answer after 3 months. Maybe the topic was raised in the wrong box, but it should be moved to Bug or took care by Stuffed Guys.

Hope this problem would be paid attention soon. Please help tell us - your customers - anything but not the silence.

[johann kuindji]

Hello.

In order to store page titles and keywords in utf-8 you need:

1. change the charset of database tables (ns_tracker_page_title, ns_tracker_keyword)
2. change the charset of default language (tracker/lang/xx/_system/xx.config.php)
3. probably you will need to change display charset in Personal settings.

All previously gathered titles and keywords will stay in their current charset.

[Squirrel]

1. change the charset of database tables (ns_tracker_page_title, ns_tracker_keyword)

How should we change the table's charset to?

[johann kuindji]

alter table `table_name` character set 'new_charset'

You can try also

alter table `table_name` convert to character set 'new_charset'.

I think you can use phpMyAdmin or something like that to perform such operations automatically.

[Squirrel]

alter table `table_name` character set 'new_charset'

You can try also

alter table `table_name` convert to character set 'new_charset'.

I think you can use phpMyAdmin or something like that to perform such operations automatically.

I mean which value should I change the current charset (latin1_swedish_ci) to? Is it utf8_unicode_ci?

[johann kuindji]

Yes, use utf8_unicode_ci.

[Squirrel]

It still does not work. I changed my table charset to utf8-unicode-ci, charset & iconv in my en.config to utf-8, and my page encoding to utf-8, but it still come up with $%^&*# characters.

Note that Google keyworks are showed properly, does it work because of the option automatically define the charset of search engine?

The annoying thing I just found out is no ability to search for visitors' names including utf-8 characters, even their names are showed properly in visitor path report.

Please help to give me some hint to deal with this weird situation. Million thanks!

[johann kuindji]

It still does not work. I changed my table charset to utf8-unicode-ci, charset & iconv in my en.config to utf-8, and my page encoding to utf-8, but it still come up with $%^&*# characters.

Note that already gathered keywords may appear broken even after converting the database to utf-8.

Note that Google keyworks are showed properly, does it work because of the option automatically define the charset of search engine?

This option surely should be enabled.
Also it may be necessary for some search engines to enable 'Always request charset' option on the search engine's properties page (go to Administration / Search engines, select an engine and click 'Search engine properties'). Although this option will increase server load.

The annoying thing I just found out is no ability to search for visitors' names including utf-8 characters, even their names are showed properly in visitor path report.

I guess you need to convert ns_tracker_client_visitor table to utf-8 as well.

[Squirrel]

If I make a fresh installation, can database use utf-8 charset as default?

[johann kuindji]

Yes.
But you still need to do all mentioned changes in tracker as you did before.

[Squirrel]

What if my database engine is still latin1?

Do I have to change its engine to utf-8?

Note that data in my table was utf-8 althought it was saved as non-utf-8 characters. When I convert, will my data be converted to utf-8 again (and it causes error in display)?

[johann kuindji]

The only that matters is if you set the tables charset (or fields).

Note that data in my table was utf-8 althought it was saved as non-utf-8 characters. When I convert, will my data be converted to utf-8 again (and it causes error in display)?

Most probably.