Hi Randall McCallum,

I am sorry for the inconvenience caused. It seems like I have make a mistake in giving you the path of the file :
DIR:./media/com_easysocial/apps/user/discuss/story.js

By the way, on the previous ticket you have request for http://personalosx.com/ and now you request support for http://www.chamberanswers.com/ .Please remember to assign your domain to your license to obtain for support in the future. You can do so by accessing your license area at http://stackideas.com/dashboard

Hi there,
I had exactly the same issue and was able to solve it using the story.js file you posted.
But.
I have the same problem when I try to post anything in a group. Could it be that the same problem exists in one of the story.js files for the group apps?
Events work fine, by the way.
I am running a development environment on Xampp, so I can';t give you access to it, I'm afraid.

Thanks!

Found it. The file /media/com_easysocial/apps/group/easydiscuss/story.js is to blame. It's missing three lines of code at line 27.
if (save.currentPanel != 'easydiscuss') {
return;
}
If you overwrite the story.js file with the one you posted it works again.

I just realized that this is a bug in the Group discuss application for Easysocial, which is a seperate product.

Hey Martien,

Thanks for reported, I believe these known issue already solved in these following discuss app latest version.

http://stackideas.com/apps/item/3320-easydiscuss-group
http://stackideas.com/apps/item/6-easydiscuss

Can you try download it and update in your Easysocial application listing page from backend and see is it still persists about that issue what you mentioned at above?

Yes, bug has been fixed in v 1.04 of the groupdiscuss app.
Amazing how quickly you updated the app, as I only downloaded v 1.03 on may 10th...

Thanks for the quick reply, even in the weekend

You are most welcome Martien, glad that your issues are resolved now.

P/S: Please remember to insert your domains for your licenses at http://stackideas.com/dashboard as we are now enforcing this policy on our support board.