Problem with private message in Pligg_Beta_9.6

[riza22]

Am unable to get the private messages module to work with Pligg_Beta_9.6
Platform :
Apache/2.0.55 (Win32) mod_autoindex_color mod_ssl/2.0.55 OpenSSL/0.9.8a PHP/5.0.5
Browsers:
Internet Explorer 6, Opera 9

Problem with private message module
------------------------------------------------
Installation : smooth ( lightbox version 0.1 also installed )
Shows : Shows Inbox link and Send Message link OK
Problem : On clicking Send Message the page just scrolls down with white area with a small red cross at left lower end
Issue : Cannot send private message

Any solution will be gratefully acknowledged.
If possible can some kind hearted soul tell me if this is working ok with _9.5 [ and if so, is there any real useful difference between the two or when final version will be released, eda ]

Thanks and best regards

[P1mpPanther]

Ahh, the good ol' red cross (and not the one that donates blood)

Thickbox Issue

Search the forums, "its in there"

[riza22]

Hi Thanks !
BUT the thread you linked is about thickbox issue.
And I am YET unable to find any thread that says about problems with private message in Pligg_Beta_9.6

Regards

[abcdefgary]

the private messaging system in pligg relies on thickbox... and the red cross you see is an issue with thickbox

[P1mpPanther]

thickbox is not initializing properly - the link i gave you has the fix

[riza22]

Are you sure it is not lightbox ?
Private Message asks only to install lightbox

Regards

[P1mpPanther]

try it and see if it works

[Iceburg]

I tried and it didn't work. =(

[P1mpPanther]

hmm, not sure then. when i had the same problem i used the code in the post and everything worked fine.

maybe a thickbox/lightbox conflict? there is a modified thickbox on the forum that works with lightbox if you have issues.

just a thought...

[AshDigg]

For the record, messaging uses 'lightbox'. Thickbox (does pretty much the same thing) is used in the 'image upload' module. Regardless, the fix in the post up above is correct.

Iceburg's problem was custom template related and we've got it fixed now.