Using XOOPS 2.2

We are having a problem with the PM feature. Everything regarding PM works fine except for the "reply" function.

With debug off when you click on reply to a PM all you get is a blank popup.

With debug ON, when you click on reply to a PM I get the following message:




I am no coder and have searched for hours yesterday and today both on here and goog to no avail. I did not find any search results for this problem nor browsing for it here or elsewhere.

Help with this will be greatly appreciated.

No thoughts on what is causing this. Anyone?

FWIW, I uninstalled the PM module, uploaded a fresh copy of the entire PM module and still get the same error message when trying to reply.

Any help at all is greatly appreciated. Please let me know if I need to give more info.

Thanks!

Perhaps the problem is with line 140 in readpmsg.php where it states:



Thoughts?

Exactly which version of 2.2 are you using. There were a lot of pm module bug fixes. Have you upgraded to 2.2.4 with all the current bug and security fixes.

Looks like for some reason the module is not able to parse the UID of the user you are trying to reply to.

Thanks for a reply!

jdseymour, we are using 2.2.3a

FWIW, we just installed a fresh version of XOOPS on another box / different domain. That is also version 2.2.3a. for the sole purpose of testing / trying to fix this PM reply problem we are having.

The pm reply works perfect on that test setup.

As I said earlier, I am no coder but am trying everything that seems like it might fix this.

So, tonight I uninstalled the PM module, deleted it. Then I downloaded the pm module from the other box (the one that pm reply is working on) and uploaded it to the site that is having the problem, installed it and guess what? PM reply still does not work!

This leads me to believe that another script outside of the PM module is where the problem is. The million dollar answer is which script.

I know that PM module relies on mainfile.php, does anyone know of other files connected to this module that might cause the problem?

Thanks!! For any help :)

I gave up and installed an early backup of site, PM reply fixed