I think it will be convenient for the #467582: Change the settings page to add a field with the date of the file request.

Comments

andypost’s picture

Great idea but it could works only for file based verifications.

dave reid’s picture

Status: Active » Postponed (maintainer needs more info)

Date of the file request? Could you please elaborate as to what you mean?

andypost’s picture

Status: Postponed (maintainer needs more info) » Needs work

The main purpose is to aggregate statistics about using validation by search engines.

The idea is add new field (for ex. requested) as unix timestamp and update it when file requested from outside in site_verify_output() function.

But maybe better to provide a trigger|hook or just menu_alter() in custom module.

Opposite opinion - using web-server logs to count this statistics

elc’s picture

Version: 7.x-1.x-dev » 2.0.0-alpha2
Issue summary: View changes

This could be achieved by adding an event which allowing another module to track accesses, and as a side effect alter the file contents (usefulness?). It would be harmless to have and fire an event to allow someone to do this.

Does not make sense when it comes to the metatag version as it will be fired every time the front page is loaded, regardless of the intent of the requester. The User-Agent could be checked, but this is more for log analysis than this module. Event should only fire for the file based verification modes.

elc’s picture

Version: 2.0.0-alpha2 » 2.1.x-dev
Status: Needs work » Closed (won't fix)

This feature doesn't belong in the module - the correct location to see if a file verification has been accessed is the the web server logs.

Reliably recording every access to the files would require any and all caching to be disabled the served verification files. I would like to enable as much caching as possible even for serving these files as this would be a very easy thing to cache.

It is then also impossible to determine when a verification service is checking the metatag; it's attempting to read bot minds, and again caching affected.

Setting as close, won't fix.