I consider the Drupal 7 version of this module done. I have been using it on a production site for about one month without any issues.

However, before making a full release, I want to see it tested by more people.

If you download and test the Drupal 7 version this module, please respond to this issue queue. You should of course report any bugs you find. But at this stage, I am also interested in feedback from people that did not experience any issues.

Comments

Anonymous’s picture

At admin/config/system/file_integrity I get this:

Notice: Use of undefined constant SCANDIR_SORT_NONE - assumed 'SCANDIR_SORT_NONE' in _file_integrity_scandir() (line 531 of /home/xxx/xxx/sites/all/modules/file_integrity/file_integrity.module).
Warning: scandir() expects parameter 2 to be long, string given in _file_integrity_scandir() (line 531 of /home/xxx/xxx/sites/all/modules/file_integrity/file_integrity.module).
Warning: Invalid argument supplied for foreach() in _file_integrity_scandir() (line 532 of /home/xxx/xxx/sites/all/modules/file_integrity/file_integrity.module).

And at batch?op=start&id=48 I get this:

Fingerprinting has encountered an error.
Please continue to the error page

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?id=48&op=do StatusText: OK ResponseText: Fatal error: Call to a member function claimItem() on a non-object in /home/xxx/xxx/includes/batch.inc on line 274

gisle’s picture

Status: Active » Needs work

Thanks for reporting this.

The problem is due to a constant passed to scandir that did not exist prior to PHP 5.4.0:

5.4.0: sorting_order constants were added. Any nonzero value caused descending order in previous versions. So for all PHP versions, use 0 for ascending order, and 1 for descending order. An option for SCANDIR_SORT_NONE behavior did not exist prior to PHP 5.4.0.

I presume your site uses an older PHP version?

PHP 5.4.0 is recommended, but not required for Drupal 7. Replacing the constant with 0 (ascending sorting order) should cure it.

  • gisle committed c99d7a5 on 7.x-1.x
    Issue #2505685 by gisle: Fixed it to work with PHP prior to 5.4.0
    
gisle’s picture

Status: Needs work » Needs review

Changes pushed. Please review.

Anonymous’s picture

Ah, you are correct, the server has php version 5.3.29. I really appreciate how quickly you fixed that! I'm going to test it now and update you. :-)

Anonymous’s picture

Seems to work fine now, thanks!

gisle’s picture

Status: Needs review » Closed (outdated)

I am no longer maintaining this, so there will not be a full release unless somebody else adopts it.

Instead, I use git to monitor file integrity.