Strict Standards: Declaration of action_plugin_jquery::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /membri/only4mods/lib/plugins/jquery/action.php on line 14

Strict Standards: Declaration of action_plugin_captcha::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /membri/only4mods/lib/plugins/captcha/action.php on line 137

Strict Standards: Declaration of action_plugin_wikistatistics::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /membri/only4mods/lib/plugins/wikistatistics/action.php on line 51

Strict Standards: Declaration of action_plugin_codehighlight::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /membri/only4mods/lib/plugins/codehighlight/action.php on line 225

Strict Standards: Declaration of action_plugin_ipban::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /membri/only4mods/lib/plugins/ipban/action.php on line 60
counterize_ii_mod:en:searchengine - Ema's plugins (WP, DW)

Unfortunately, some of the pages are now read-only, this because in the last few months some spammers decided to “contribute” to the wiki…
I'm trying to lock only the interested pages.


Strict Standards: Declaration of Doku_Renderer_metadata::table_open() should be compatible with Doku_Renderer::table_open($maxcols = NULL, $numrows = NULL, $pos = NULL) in /membri/only4mods/inc/parser/metadata.php on line 24

Strict Standards: Declaration of Doku_Renderer_metadata::table_close() should be compatible with Doku_Renderer::table_close($pos = NULL) in /membri/only4mods/inc/parser/metadata.php on line 24

Aggregation of search engines referers

Instead of the detailed “search string” used by the visitor to arrive to my blog, I would like to know how many visitors arrived to my blog using google (or maybe google.com, google.it, it.yahoo.com and so on) and how many using yahoo and so on.

Thoughts

For this reason some changes are necessary in “counterize_refererTable()” and “counterize_keywordTable() tables structure.

That solution should help save some1) db space.

The main problem is that such modification need big changes in table structure…

Not so big, only a switch of columns.

Ok, it is big, very big… For each host we can have more than one keyword, but for each keyword we can have more than on host…of course…So in the end we'll need an intermediate table that join keywords and hosts, something like “wp_counterize_keywordXhost”. And this could be complicated (expecially with my sql knowledge equal to 0.1 2)

Third and hopefully last change. It should be easier than expected: I can add a 'keywordID' column to 'wp_counterize' table. In this way I have the connection between hosts and keywords for each entry of the db. Problems can occur when the db is ”archived”: after that operation the connection will be lost, but the question is do I need to keep this information after have removed the raw data from the db? The answer is: probably not.

To do

Of course create an “install” function for migration from classic counterize II:

  1. in 'wp_counterize_keywords' add 'refererID' column DONE :!:
  2. add a table 'wp_counterize_keywordXhost' 3)
  3. in 'wp_counterize_referers' for each record if 'name' is a search engine:
    1. extract the host 4)
    2. if the host doesn't exist add a new record, otherwise update the 'count'
    3. search the 'keywordID' in 'wp_counterize_keywordXhost'
    4. in 'wp_counterize_keywordXhost' write the host 'refererID' and 'keywordID'
    5. update 'refererID' in 'wp_counterize' FIXME It cannot work… 5)
    6. drop the original record
  4. in 'wp_counterize_referers' remove 'keywordID' column

Update all the functions that query tables 'wp_counterize_keywords' and 'wp_counterize_referers'

1) some, for sure not “a lot”
2) in a scale from 0 to 10, of course
3) 3 columns: 'kxhID, 'refererID' and 'keywordID'
5) if referer is a search engine, refererID could be linked to more than one keyword, so at the end I cannot know which keyword bring the user to my blog, I should use the 'kxhID', but I don't want to add another column to 'wp_counterize', maybe I can try to use 'kxhID' in 'wp_counterize→refererID' and check if the referer is a search engine. I'll try

Tools personali