DEPRECATION WARNING

This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.

newloginlog

Author:Kasper Skårhøj
Created:2002-11-01T00:32:00
Changed by:Alex Kellner
Changed:2009-03-05T16:55:54
Author:Alex Kellner
Email:Alexander.Kellner@einpraegsam.net
Info 3:
Info 4:

newloginlog

Extension Key: newloginlog

Copyright 2005-2008, Alex Kellner, <Alexander.Kellner@einpraegsam.net>

This document is published under the Open Content License

available from http://www.opencontent.org/opl.shtml

The content of this document is related to TYPO3

- a GNU/GPL CMS/Framework available from www.typo3.com

Table of Contents

newloginlog 1

Introduction 2

What does it do? 2

What does it need to work? 2

Screenshots 3

Entries of login in the backend 3

Debug output (if enabled) 3

Users manual 4

Extension Manager configuration 5

Example settings 5

Explanation 6

Todo 7

Changelog 8

Version max. 0.1.x alpha 8

Additional links 9

Introduction

What does it do?

If you want to log the time (and maybe the IP address) when your feuser are logging in, you can use newloginlog.

This small extension works with newloginbox or with the follower felogin.

There are a few configuration possibilities in the extension manager.

What does it need to work?

  • newloginbox OR
  • felogin

Screenshots

Entries of login in the backend

img-1

img-2

Debug output (if enabled)

img-3

Users manual

  • Import and install newloginbox from TER OR
  • Install felogin from sysextensions
  • Import newloginlog from TER
  • Make your settings in the extension manager (see below)
  • Don't forget to click update in the extension manager after you made your settings!
  • Done!

Extension Manager configuration

Example settings

img-4

Explanation

Title

a

Title

b

Explanation

c

Default value

d

Data type

pid

a

pid

b

PID were to save: Define a PID where the logged values should be displayed in backend

c

0

d

text

pidInRootline

a

pidInRootline

b

pidInRootline: Define a PID in which the login log should work (0 let the global check works overall, -1 disables global check, 23 in PID 23 and child pages)

c

0

d

text

ip

a

ip

b

Allow IP log: Enable or disable saving of IP addresses

c

1

d

boolean

debug

a

debug

b

Debug mode: Disables db log and shows you the values which should be logged after login

c

0

d

boolean

Todo

Are there any other values which should be stored in the database?

Is there something to improve? Write me!

Changelog

Version max. 0.1.x alpha

First release to TER on 05.03.2009 version 0.1.0 alpha

Initial release