Hello. After upgrading to 4.7 legitimate content from long time members with thousands of posts is sometimes flagged for mod approval. This has never happened before the last upgrade. The posts in question might include picture upload or an external hyperlink.

How can I find out what setting is causing this and fix it? 

Thank you.

Here is an example 

The picture itself if it's remotely linked is a URL.  The software is displaying the picture, but if you're pasting an external image, it is still an external hyperlink.  (It has http/https.)

Thank you Randy.

I would really appreciate if someone can help me understand what changed with the last upgrade to trigger such system behavior and how to fix it.

This never happened before the last upgrade.

Thank you.

Edited July 10, 20222 yr by virap

Actually nothing has changed there. If anything, that would have been something corrected if it hasnt been flagging them before. Are you saying you indeed have them set up as Randy mentioned?

Thank you Marc. I am not sure I understood this. Can you please explain what exact setting you are referring here?

  Quote

Are you saying you indeed have them set up as Randy mentioned?

I do have 3 word filters set up to detect urls and flag them for manual review. But all 3 rules are set up to apply to account with less than 10 posts. The accounts being flagged have thousands of posts. Here is one of these word filters

Yep, that's reproducible - works fine on 4.6.12.1 (live site); same filter on 4.7.0 (test site) results in it being held.

Edited July 11, 20222 yr by Nathan Explosion

Thanks Nathan. Taking a look now

Removing prior content - that may not be the only change involved here.

Edited July 11, 20222 yr by Nathan Explosion

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

Thank you very much Nathan and Marc.

 

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

Marc, any updates on this issue? I saw a maintenance release today, but I don't think this was included in the release.

This is still an open issue at present

@Marc Stridgen Was this included in today's upgrade? 

This has not quite made this release. 

 

This has not quite made this release. 

Thank you.