Jump to content


[Tracking Code] Undocumented change of tracking code?


6 replies to this topic

#1 Guest_tom929384600_*

  • Guests

Posted 26 December 2008 - 06:49 AM

Hi guys!

I just wondered. I added the tracking code to a new/next website of me and noticed that the tracking code of the server admin 3.1.7.11 is total different then the tracking code i am using since 3.1.7.2 !

The code i am using on the old site is looking like:

But the lates server admin tells me to use now this code:


Besides the fact i havnt read anything about a tracking code change on the changelog (where this should be mentioned so old users can react):

- why is it changed?
- do i need to edit/echange the old codes?
- what about the new livezilla_tracking div?
- what about the new "nse" part of the code?


Greetings and merry xmas ... !
Keep it going .. Livezilla rocks!

Waiting for answers ;)

#2 Derek Punzova

    Support Team Member

  • Moderators
  • 6181 posts

Posted 27 December 2008 - 10:45 AM

Quote

i havnt read anything about a tracking code change on the changelog (where this should be mentioned so old users can react):

Quote

LiveZilla 3.1.7.10

* LiveZilla Scripts are HTML 4.01 valid now (Doctype can be choosen)

Quote

LiveZilla 3.1.7.9

* LiveZilla Visitor Monitoring Script is XHTML valid now


Hope this helps ;)
- If you like to suggest a new feature, please click here.
Kind Regards,
Derek

#3 Guest_tom929384600_*

  • Guests

Posted 27 December 2008 - 06:39 PM

Hi Derek!

ok ok ... maybe i havn´t noticed it :)

But could you answer this questions please:

- do i need to edit/echange the old codes?
- what about the new livezilla_tracking div?
- what about the new "nse" part of the code?

BTW: as i mentioned b4 xmas in live chat:
The changelog should be more detailed and there should be hints included - like this example:

Quote

LiveZilla Visitor Monitoring Script is XHTML valid now
- The code - of course - wont change on your server by upgrading your livezilla.
- We recommend to generate the new tracking code with the server admin and to use it instead of the old codes.
- To continue using the old codes is not recommended but shouldnt make any problems.


Greetings
Tom

#4 Guest_tom929384600_*

  • Guests

Posted 04 January 2009 - 06:21 PM

Derek?

Would you please answer my questions? This would be very kind. Thanks! ;)

#5 Patrick Keil

    Administrator

  • Administrators
  • 3788 posts
  • LocationSingen, Germany

Posted 06 January 2009 - 09:35 AM

Quote

- do i need to edit/echange the old codes?
I would recommend that, yes.

Quote

- what about the new livezilla_tracking div?
- what about the new "nse" part of the code?
Well, its open source - if you are interested in it just see for yourself.

#6 Guest_tom929384600_*

  • Guests

Posted 19 January 2009 - 04:27 AM

pkeil said:

Quote

- what about the new livezilla_tracking div?
- what about the new "nse" part of the code?
Well, its open source - if you are interested in it just see for yourself.

This does NOT brings me much further. :(
A brief explanation would have been much more constructive and helpful.

#7 Guest_tom929384600_*

  • Guests

Posted 22 January 2009 - 11:08 PM

Quote

SNE : Stateful Network Equipment library
A library for designing complete steateful network equipment (contains linux kernel patch + user space deamon)
In operational networks, the availability of some critical elements like gateways, firewalls and proxies must be guaranteed. Some important issues like the replication of these network elements, the reduce of unavailability time and the need of detecting failure of an element must be studied. The aim of the SNE library is to support issues related to the implementation of high available network elements, with specially focus on Linux systems and firewalls. The SNE library ( Stateful Network Equipment) is an add-on to current High Availability (HA) protocols. This library is based on the replication of the connection tracking table system for designing stateful network equipments.

This one?

Still does not know why to include a div in my code ... this will probably bust my site as the livezilla code is implemented on a very small and tight area of the site where another div wouldnt fit i think.
yould you explain this changes? Thank you!





2 user(s) are reading this topic

0 members, 2 guests, 0 anonymous users