Search options (Page 2 of 7)

Name Tags are an easy way to identify exactly who your visitors are.

It works by associating information your site manages (username, e-mail, account ID, etc..) with the session ID Reinvigorate uses to track visitors on your site/blog.

It's extremely simple to setup, even if your site uses its own proprietary user account system. 1-2 extra lines of code and we take care of the rest.

Reinvigorate uses two global JavaScript variables which let you customize your visitors Name Tags, re_name_tag and re_context_tag. The re_context_tag variable is optional and may be left out. It's provided in case you want to associate additional information with your visitors (ie- Username/Email, Username/Website, etc..). If you use re_context_tag, e-mail and website addresses should be respectively prefixed with mailto: or http://

Name Tag Code

You will need to write server-side code to output a visitor identifier, something like the code below. This code must be placed above the function call to re_("...");

var re_name_tag = "Username/Identifier";

For example, the following pseudo PHP code shows how one might use re_name_tag. The code is based on two assumptions. First, the PHP variable $is_logged_in is set to true if a user is logged in. Second, the variable $username contains a users username.

var re_name_tag = "<?php
echo $is_logged_in ? $username : "";
?>";

After installing code like above, Reinvigorate will automatically detect the change and display name tags on any applicable report.

Please be sure to index your tables properly - you had a query running
that was way more innefficient than it had to be - it went from checking
over 2000 entries each time to under 25:

mysql> explain SELECT * FROM 20050910_punbb_messages WHERE owner=65 AND
status=0 ORDER BY posted DESC LIMIT 0,10;
+----+-------------+-------------------------+------+---------------+----
--+---------+------+------+-----------------------------+
| id | select_type | table                   | type | possible_keys | key
| key_len | ref  | rows | Extra                       |
+----+-------------+-------------------------+------+---------------+----
--+---------+------+------+-----------------------------+
|  1 | SIMPLE      | 20050910_punbb_messages | ALL  | NULL          |
NULL |    NULL | NULL | 2002 | Using where; Using filesort |
+----+-------------+-------------------------+------+---------------+----
--+---------+------+------+-----------------------------+
1 row in set (0.02 sec)

mysql> create index owner on 20050910_punbb_messages(owner(10));
ERROR 1089 (HY000): Incorrect sub part key; the used key part isn't a
string, the used length is longer than the key part, or the storage
engine doesn't support unique sub keys
mysql> create index owner on 20050910_punbb_messages(owner);
Query OK, 2002 rows affected (5.08 sec)
Records: 2002  Duplicates: 0  Warnings: 0

mysql> create index status on 20050910_punbb_messages(status(10));
ERROR 1089 (HY000): Incorrect sub part key; the used key part isn't a
string, the used length is longer than the key part, or the storage
engine doesn't support unique sub keys
mysql> create index status on 20050910_punbb_messages(status);
Query OK, 2002 rows affected (8.08 sec)
Records: 2002  Duplicates: 0  Warnings: 0

mysql> explain SELECT * FROM 20050910_punbb_messages WHERE owner=65 AND
status=0 ORDER BY posted DESC LIMIT 0,10;
+----+-------------+-------------------------+------+---------------+----
---+---------+-------+------+-----------------------------+
| id | select_type | table                   | type | possible_keys | key
| key_len | ref   | rows | Extra                       |
+----+-------------+-------------------------+------+---------------+----
---+---------+-------+------+-----------------------------+
|  1 | SIMPLE      | 20050910_punbb_messages | ref  | owner,status  |
owner |       4 | const |   21 | Using where; Using filesort |
+----+-------------+-------------------------+------+---------------+----
---+---------+-------+------+-----------------------------+
1 row in set (0.01 sec)

---

That dropped the load on your database server quite a bit!