Yeah, a lot of us are seeing this error. I've found that the initial effort to post is actually going through, despite the error message. Needless to say, this isn't a good thing, because it's clear there is some sort of corruption or incorrect setting in the forum software. I think that it started for me after my most recent Chrome update, so perhaps it is connected to that. It would be good to get a list of how many are having the problem, and what OS and browser we are each using.To the Moderators;
Why is it as of late, that I've been getting this notice that says; "We've run into a problem." Then when I enter the post, it comes up TWICE! Is there a problem with the forum or something?
posting works but I get errors that make it seem like it doesnt work
PHP: <br />
<b>Fatal error</b>: Declaration of XF\Service\Conversation\Pusher::setInitialProperties(XF\Entity\ConversationMessage $message, $actionType, XF\Entity\User $sender) must be compatible with XF\Service\PusherTrait::setInitialProperties(...$properties) in <b>/home/utadmin/public_html/archboston/community/src/XF/Service/Conversation/Pusher.php</b> on line <b>30</b><br />
defaultAjaxError @ core-compiled.js?_v=6b7854e4:45
@SkyriseCities
Looks like most of us, if not everyone, are getting a false alarm "something went wrong" error message when we hit "post reply" or (at least in my case) send a private message. If you dismiss the message and refresh the page, your message in fact has been posted. The error message says to check the console log -- this is what I got the most recent time in mine:
PHP: <br /> <b>Fatal error</b>: Declaration of XF\Service\Conversation\Pusher::setInitialProperties(XF\Entity\ConversationMessage $message, $actionType, XF\Entity\User $sender) must be compatible with XF\Service\PusherTrait::setInitialProperties(...$properties) in <b>/home/utadmin/public_html/archboston/community/src/XF/Service/Conversation/Pusher.php</b> on line <b>30</b><br /> defaultAjaxError @ core-compiled.js?_v=6b7854e4:45