Uncheck the first box here: http://b2evolution.net/man/antispam-settings-misc

The original issue that started this thread also occurs if a fully qualified URL path link is published to Twitter -- in a given b2evolution deployment instance. It does not matter if the URL is first shortened with bit.ly -- for instance.

It seems that the mere referral from Twitter is enough to cause the issue because if the bit.ly URL is typed at the command line to a browser, it will open the fully qualified URL path appropriately.

Notwithstanding, in this particular b2evolution deployment instance, deselecting the "Block spam referrers" box is not an option as there are extremely many Yahoo proxy spam referrals.

@nanahuatl wrote earlier:

It seems that the mere referral from Twitter is enough to cause the issue because if the bit.ly URL is typed at the command line to a browser, it will open the fully qualified URL path appropriately.

Then check your blacklist against the original referer URL.

@nanahuatl wrote earlier:

Notwithstanding, in this particular b2evolution deployment instance, deselecting the "Block spam referrers" box is not an option as there are extremely many Yahoo proxy spam referrals.

And, what happens if you actually don't block those spam referrers? What do they do?

(just trying to better understand why you still use that feature which I personally don't.)

I still hope you will answer the questions above, but no matter what here is the fix:

https://github.com/b2evolution/b2evolution/commit/f55747486ecc6a552005ba5215d377c1bfeee35a

(It requires edits to 3 different files)