Serendipity Forums

Stupid question, but I just realized that the checksum.inc.php is always empty in a git checkout. I'm guessing this is intended and the file is somehow generated during release preparation.

Anyway, this results in a “Unable to compare checksums! (No checksums.inc.php in main directory)” warning when clicking “Verify Installation Integrity” in the (new) backend. Can I generate the checksums manually after installing to properly test this?

YL

yellowled wrote:Stupid question, but I just realized that the checksum.inc.php is always empty in a git checkout. I'm guessing this is intended and the file is somehow generated during release preparation.

Yes.

yellowled wrote:Anyway, this results in a “Unable to compare checksums! (No checksums.inc.php in main directory)” warning when clicking “Verify Installation Integrity” in the (new) backend. Can I generate the checksums manually after installing to properly test this?

(*)
This does not make sence! What do you want to check with it?

Normally /bundled-libs/serendipity_generateFTPChecksums.php generates the checksums of the current file system and compares them with already by release delivered checksum file on demand.

If you run this now, cache the checksums, put them as an array into the checksum file and compare it again, it will tell you everything is fine.

A quicker way to get an example checksum file, is to copy the one from 1.7.

(*) see also http://board.s9y.org/viewtopic.php?f=11&t=19271

Timbalu wrote:This does not make sence! What do you want to check with it?

Simply put, as of now, I can only see the integrity check's results with this particular warning. I can't even check out the integrity check's results would look like if the checksums were present.

YL