Moodle plugins directory: Auto Attendance Block | Moodle.org
Auto Attendance Block
Blocks ::: block_autoattend
Maintained by Fumikazu Iseki
Part of set Auto attendance.
This autoattend block is modification of the Attendance block by Mr. Dmitry Pupinin (v1.0.8, 2007).
In addition to the original manual mode, automatic attendance mode (from the access log of Moodle) and semi-automatic attendance mode (user clicks a link) are also possible.
Latest release:
981 sites
318 downloads
60 fans
Current versions available: 1
These Auto Attendance block and module are modification of the Attendance block/module of Mr. Dmitry Pupinin (v1.0.8, 2007).
In addition to the manual attendance mode to take attendance manually the original, automatic attendance mode (from the access log of Moodle) and semi-automatic attendance mode (user clicks a link) are also possible.
I strongly recommend a combination of Auto Attendance block (autoattend) and Auto Attendance module (autoattendmod).
Useful links
Contributors
Fumikazu Iseki (Lead maintainer)
Please login to view contributors details and/or to contact them
Has anyone successfully this Block & Module with Moodle 2.6?
I am experimenting with the Auto Attendance Block & Module in Moodle 2.6.2+ (Build: 20140320). In particular, I'm now testing the ' Semi Auto' method. When a student clicks on the Attendance Activity and tries to submit a keyword, the following error appears:
///////////////////
Error writing to database
More information about this error
Debug info: Data too long for column 'ipaddress' at row 1
UPDATE lmdl_autoattend_students SET attsid = ?,studentid = ?,status = ?,called = ?,calledby = ?,calledtime = ?,ipaddress = ? WHERE id=?
[array (
0 => '38',
1 => '11',
2 => 'P',
3 => 'S',
4 => -2,
5 => 1395893274,
6 => 'fe80:0:0:0:288:65ff:fe3d:8d2c',
7 => '39',
)]
Error code: dmlwriteexception
Stack trace:
line 446 of /lib/dml/moodle_database.php: dml_write_exception thrown
line 1186 of /lib/dml/mysqli_native_moodle_database.php: call to moodle_database->query_end()
line 1218 of /lib/dml/mysqli_native_moodle_database.php: call to mysqli_native_moodle_database->update_record_raw()
line 120 of /blocks/autoattend/semiautoattend.php: call to mysqli_native_moodle_database->update_record()
///////////////////
You use IPv6 address.
The current autoattend does not support IPv6.
I will fix it as soon as possible.
Thanks.
I released 2.1.13.
In this version, I Increase the field size of the IP address (for IPv6).
This is a temporary version.
If you use IPv4, you do not need to update to 2.1.13
And, if you use IPv6, you can not use "Allowed IPs" function.
Thanks.
(Developper mode is turned on)
Thaks for your bug report!!
I think that this is a bug which appears only at the installation.
And after autoattend was installed, I think that it does not appear.
I corrected this bug at subversion repository, now.
Thanks.
ありがとうございます.
すみません.将来早退にも対応しようかと思い,途中で代えてしまいました.
言語ファイルで以下の項目を直接編集するか,管理メニューの言語カスタマイゼーションでローカル定義すればそのまま動くはずです.
$string['Eacronym'] = '早';
$string['Eacronymfull'] = '早退';
$string['noofdaysexcused'] = '早退数';
私は忌引きなどの場合は,取り合えず出席として,コメントに忌引きなどの情報を入れてます.
どっちが良いのでしょう?
本学では、「レポート」ページの「ID番号」を表示するように変更しています。
ダウンロードデータには「idnumber」が追加されましたが、今後ページにも追加の予定は有りますでしょうか?
Thanks for the great module.
In our university, we have modified to display the "ID number" in "Report" page.
"Idnumber" has been added to the download data, or will you have any plans of also added to the page in the future?
ご使用有難うございます.
現在はフィードバックが少ないので,殆ど自分で使用する機能のみ追加をしています.(^^;
ご希望があれば,可能な限り対応いたします(非常に工数がかかりそうな場合は夏休みまで無理ですが).
レポートページでのID番号の表示についても,期日はお約束できませんが対応したいと思います(すみません).
また,ご希望・バグレポート等ありましたらよろしくお願いいたします.
急ぎの場合は subversion のリポジトリを使用してみてください.
http://www.nsl.tuis.ac.jp/svn/php/autoattend/trunk/
Please use https://translate.google.com/ ..sorry..
I changed the time zone of moodle to UTC+1 and the time zone in php.ini to Europe/Paris and now it looks like it is ok.
But there is still 2 problems:
- the session of today remains unstarted (red icon), when it should be opened (yellow icon)
- yesterday session remains opened (yellow icon) when it should be closed (green icon)
Is it a bug or am i doing something wrong? (printscreen available)
Note: I did not activate the use_timeoffset flag as it modifies the actual dates by a few days...