• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

XF 1.2 Users unable to send PM

Renegade

Well-known member
#1
Some new users are not able to send PMs. When they hit the Start Convo button they get an error that "Your content cannot be submitted. Please try again later".

Any suggestions on how to troubleshoot it?
 

Renegade

Well-known member
#3
Yeah there is
Error Info
ErrorException: Fatal Error: Call to a member function exists() on a non-object -/home/xyz/public_html/news/wp-includes/pluggable.php:730
Generated By: Unknown Account, Jan 16, 2014
Stack Trace
#0 [internal function]: XenForo_Application::handleFatalError()
#1 {main}
Request State
array(3) {
["url"] => string(42) "http://www.site.com/news/xmlrpc.php"
["_GET"] => array(0) {
}
["_POST"] => array(0) {
}
}
 

Renegade

Well-known member
#5
Its not coz users are still not able to send PM with that disabled. And that wordpress bridge operates from the WP side, nothing changed on XF side.
 

Jake Bunce

XenForo moderator
Staff member
#6
Some new users are not able to send PMs. When they hit the Start Convo button they get an error that "Your content cannot be submitted. Please try again later".

Any suggestions on how to troubleshoot it?
Is this a XF error page? I don't see that specific error message anywhere in the software. Did you try disabling your addons to see if that affects it?
 

Jeremy

Well-known member
#7
The error message you posted clearly states that an error exists within a Wordpress functions file. That is most likely the root cause of your issue.
 

Renegade

Well-known member
#8
The error message you posted clearly states that an error exists within a Wordpress functions file. That is most likely the root cause of your issue.
Yes but that error message does not relate to the PM posting issue. I have seen user screenshots and there is nothing in the error log that corresponds to that timestamp.
 

Attachments

Mike

XenForo developer
Staff member
#9
That error indicates it tripped an anti-spam rule/option you have defined. (1.3 has a log that would help you determine which.)