Yes, but the reason I did it this way rather than leave it the way Dream does it, is because Dream's version works fine on smaller forums with only a few thousand members on it. But when you get into the tens of thousands of users and they all have at least one PM, then what happens with Dream's version, is that it starts taking thirty plus seconds for the query to complete as Dream's version does not have any form of pagination, thus rendering this hack unusable (I have actually replicated this issue on a Big Board).

That is why it is the way it is in this version.

I may look into doing it via username (no promises), but it would definitely need to have pagination incorporated to prevent making the hack useless. It would be in addition to to via PM totals, not instead of them. But like I said, no promises.

It means that the To array in the individual PM is not being retrieved from the database, and as a consequence it is not being displaced. It has been this way since v3.8.001 of this hack, so it is not the hack doing this.

Also, I have found that this happens with forums that are really old (i.e. they were installed with a vBulletin version below v3.5), as the structure of PMs changed around vBulletin v3.5, so older PMs created in version 3.0.x or below may not show the To and CC and BCC fields correctly with this hack.

I figured your design layout had to do with size of board issues. It would be awesome to have a paginated version that lists user names though. I hope you consider it.

This modification is very useful if members are are abusing or spaming a forum and if used in that context there is no raisng issue of violation of members rights.

thanks for the update

Great hack. This should solve those pesky 'he said, she said' arguments.

Installed.

See the above, but I will tell you only this until you have clicked Mark as Installed: You have not uploaded the files to the correct locations.

OK, now that you have clicked Mark As Installed, the first thing I noticed is that read_pms.php is not in your admincp folder. As print_cp_header() is an AdminCP function, if read_pms.php is not in the admincp folder, then you will have this issue - see the vBulletin API for more info.

nice job...