The README clearly indicates that you have to patch the SM source. Did you do that?
I did read the README. However, as I read, I found that I didn't meet any of the conditions:
3a)If you are running SM version 1.4.2 then... 3b)If you are running SM version 1.4.1 or less then: 4a)If you are running SM version 1.4.2 then: 4b)If you are running SM version 1.4.1 or less then:
It wasn't until I got to step 4c that I saw the part about the diff files. At first I didn't want to use those, so I went right to step 5. Since re-reading step 4c I realized I do have some more work to do.
Yes, the README appears to be written at the time when 1.4.2 was the latest release w/out thinking ahead. ;) It should be re-worded. I would prefer if Brad would rewrite it so that the information about the patch comes before you've trudged through all that manual (and probably out of date) hacking information. Patch files are the preferred way to manage such changes. (in fact, there is so much to read here that I think it would be best to extract this into a separate INSTALL file)
Also, please take note that I just removed the internal_link hook from SM1.5.1, per my long-standing threat. The plugin already requires a patch to the same code, so it should merely be modified to add the hook back. My change should hit anonymous CVS in a day or so.
Cheers,
Paul
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
--
squirrelmail-users mailing list
Posting Guidelines: http://squirrelmail.org/wiki/wiki.php?MailingListPostingGuidelines
List Address: [EMAIL PROTECTED]
List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user
List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995
List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
