Textpattern CMS support forum

You are not logged in. Register | Login | Help

#1 2009-05-24 21:46:07

Gocom
Plugin Author
Registered: 2006-07-14
Posts: 4,524
Website

rah_unlog_me // Remove your own hits from visitor logs

Adds additional filtering options for visitor logs. Features:

  • Automatically filter out hits made by site admins.
  • Exclude selected list IPs from logs (bots, search engines).
  • Integrates nicely to Textpattern’s native Preferences panel. Very easy to use.

More info and downloads

Last edited by Gocom (2011-12-06 10:02:16)

Offline

#2 2009-05-24 21:51:03

Els
Admin
From: The Netherlands
Registered: 2004-06-06
Posts: 7,453
Website

Re: rah_unlog_me // Remove your own hits from visitor logs

Super, thanks Jukka! I also like it that it shows my own IP. Another very useful plugin :)


<txp:Els /> ;)
Tag Reference | Unexpected behaviour? Check the tag trace | Still no clue? Check the names of your custom fields

Offline

#3 2009-05-24 22:07:23

bg
Member
From: Pekin Illinois USA
Registered: 2005-02-20
Posts: 22
Website

Re: rah_unlog_me // Remove your own hits from visitor logs

I love it! Works like a charm. Thank you, Jukka.


— Bob

Offline

#4 2009-05-24 22:23:00

Gocom
Plugin Author
Registered: 2006-07-14
Posts: 4,524
Website

Re: rah_unlog_me // Remove your own hits from visitor logs

Els wrote:

Super, thanks Jukka! I also like it that it shows my own IP. Another very useful plugin :)

bg wrote:

I love it! Works like a charm. Thank you, Jukka.

Thanks :P

Offline

#5 2009-10-27 18:57:07

colak
Admin
From: Cyprus
Registered: 2004-11-20
Posts: 6,078
Website

Re: rah_unlog_me // Remove your own hits from visitor logs

Hi Jukka,

Today my server’s MySQL went wild prohibiting any connection to the db (error was too many connections). The site has since come back but this plugin returns an error A problem occured while loading the plugin: rah_unlog_me -> User_Warning: Can't open file: 'txp_log.MYI' (errno: 145) delete from txp_log where ip='xx.xx.xx.xx' on line 85

sorted: had to repair the table:)

Last edited by colak (2009-10-27 19:00:13)


Yiannis
——————————
neme.org | hblack.net | LABS | NeMe @ github

Offline

#6 2009-10-28 06:53:10

mapu
Member
From: Munich, Germany
Registered: 2004-03-16
Posts: 141

Re: rah_unlog_me // Remove your own hits from visitor logs

An option to exclude via cookie would also be great, if not better!

Offline

#7 2010-06-01 20:53:18

Gocom
Plugin Author
Registered: 2006-07-14
Posts: 4,524
Website

Re: rah_unlog_me // Remove your own hits from visitor logs

mapu wrote:

An option to exclude via cookie would also be great, if not better!

Hi Marcus. Sorry for the late reply. Currrently the plugin has an option to exclude via a cookie, altho with a small twist. As you probably know it has the option to exclude all user that log in to Textpattern, but the cleaning of the logs is done only on the admin side when the user logs in. This is to reduce database activity and to not use any code on the public pages which could potentially slow the pages.

I’m wondering if you are asking if I could move the unlog code to the public side and exclude the hits altogether from those that has TXP’s login cookie? Or are you asking a possible seperated cookie that could be used to exclude even public visitors? Both methods would be active on the public side tho.

And as a following question; Should it store the IPs that have the cookie set for future use. So the ones that once had the cookie would never come back to the logs.

Someone else can answer the questions too. All opinions are appreciated.

Offline

#8 2010-06-02 05:17:00

mapu
Member
From: Munich, Germany
Registered: 2004-03-16
Posts: 141

Re: rah_unlog_me // Remove your own hits from visitor logs

Gocom wrote:

Hi Marcus. Sorry for the late reply. Currrently the plugin has an option to exclude via a cookie, altho with a small twist. As you probably know it has the option to exclude all user that log in to Textpattern, but the cleaning of the logs is done only on the admin side when the user logs in. This is to reduce database activity and to not use any code on the public pages which could potentially slow the pages.

I’m wondering if you are asking if I could move the unlog code to the public side and exclude the hits altogether from those that has TXP’s login cookie? Or are you asking a possible seperated cookie that could be used to exclude even public visitors? Both methods would be active on the public side tho.

And as a following question; Should it store the IPs that have the cookie set for future use. So the ones that once had the cookie would never come back to the logs.

I haven’t taken a look at the plugin for a while. But if it’s currently like you described it’s perfect for my own purposes. I can only speak for myself but for me it’s enough if only admins or registered users get the cookie set. IP storage is not a solution, at least not in Germany where ISPs are serving dynamic IP addresses that change with every new connection to the internet.

Thanks for your effort!

Offline

#9 2011-03-13 20:47:30

Gocom
Plugin Author
Registered: 2006-07-14
Posts: 4,524
Website

Re: rah_unlog_me // Remove your own hits from visitor logs

Released version 1.0 of rah_unlog_me. Changes are pretty — something — atleast visually. The plugin no longer has its own admin pane. Instead, now the plugin integrates with TXP’s own native preferences pane and stores the preferences in the database’s main preferences table. Don’t worry, the plugin includes automatic migration script.

Changelog:

  • Integrated plugin’s preferences to Textpattern’s native preferences pane.
  • Better excluding/removing script. No longer searches IPs from the logs if it doesn’t need to; takes no action when logs are off, and removes the additional IPs from logs only when accessing the logs pane.
  • Language string support.
  • Now requires TXP 4.0.7 or newer.

More info and downloads

Offline

#10 2011-03-14 17:20:52

Gocom
Plugin Author
Registered: 2006-07-14
Posts: 4,524
Website

Re: rah_unlog_me // Remove your own hits from visitor logs

Released version 1.1. Changes:

  • Fixed typo in the uninstaller. Renamed step from “delete” to “deleted”.
  • Added forgotten flags.
  • Added missing privileges for the plugins pane’s options link.
  • Fixed typo in docs. Changed required TXP version from 4.0.7 to 4.2.0.

More info and downloads

Offline

Board footer

Powered by FluxBB