CUNY Academic Commons

Ray, could you have a look to see if you could reproduce?

Hi -
Shawn experienced this issue again. See attached screenshot.

I could not duplicate the problem.

However, I do see one potential issue. If Shawn had a ton of browser cookies when attempting to post the group announcement, this could have led to the error. (This is similar to a bug I reported to BuddyPress, which was fixed awhile ago.)

Our custom email announcement code has a similar problem. I've added a commit to fix this, but am unsure if this will address this issue 100%.

If someone encounters this problem again, can the person to do the following?

In Firefox:
1. Before posting the announcement, open up the Web Console (the easiest way to do this is by right-clicking on the page and selecting "Inspect Element")
2. Next, click on the "Network" Tab.
3. Click on the "Post Update" button to attempt to post the announcement. An entry will be listed in the "Network" tab. Click on it.
4. This will open a side window with a bunch of information. Click on the "Params" tab and list the information.

I've attached an animated GIF detailing this process in Firefox as well:

I can write up a similar tutorial for Chrome if needed.

Given the number of punts here, and the lack of further reports, I'm going to mark this one resolved. Please reopen if there are still problems.

I got a private report from another user about this. The user provided me with details about the content of the announcement, and I was able to reproduce the issue. It turns out that including too many links trips the bp_core_check_for_moderation() flag (first time I have ever seen this function!!)

I'm going to disable the max_links check for the Commons, as I think we trust our users not to be link farmers.

It turns out not to be easy to disable the max_links check alone for a given type of activity, so I've disabled all automated moderation for group announcements https://github.com/cuny-academic-commons/cac/commit/d52bd5213bae2f1c807349dc5fd232ad1d616193 It's not a very good feature of BP anyway.

This is deployed as a hotfix, as it was easiest to debug there.