Foroverse for XenForo 1.2.5

We have released a new update with one new feature.

• New: Foroverse can now reach forums whose host blocks its calls, such as forums on XenForo Cloud, through the XenForo API. At the next check-in the add-on creates its own API key, "Foroverse connection (created automatically)", in Setup > API keys. It is a guest key that can only reach the Foroverse add-on, and every call must also carry Foroverse's signature. While Foroverse uses it, the Health tab says XenForo API.

If you delete or switch off the key, the add-on doesn't create it again: Foroverse goes back to how it reached your forum before, and Health offers Recreate the key. The key is removed when you disconnect or uninstall. Nothing else changes.

A new XenForo Cloud forum connects in firewall mode first, then moves to the XenForo API by itself, usually within a few minutes.

We have released a new version containing two bug fixes:

• Fix: Two data registry keys were shortened to 25 characters, so refusal reasons are now properly recorded in the error logs. Reported by @Mr Lucky
  • foroverseCommunityRefusals
  • foroverseCommunityRejection
• Fix: Add-on files can now be properly deleted. Reported by @MaximilianKohler

We have released a new update with one bug fix.

• New: When the add-on refuses to link an account, it now writes the exact reason to your forum's server error log (Logs > Errors > Server error log). The entry names the account and where the link was refused, and says why: the account is banned, its user state isn't Valid, or the spam cleaner was used on it and it was never restored (with the date and who applied it). It also tells you what to change to allow linking.

Thanks to @Mr Lucky , whose test account turned out to have an old spam cleaner entry. That's what encouraged this.

We have released a new update with two bug fixes.

• Fix: Threads whose first post quotes a member no longer log the template error "Cannot call method isIgnoring on a non-object". The post now reaches Foroverse with its formatting, instead of as plain text. Found by @Mr Lucky
• Fix: XenForo 2.2: Setup > Foroverse no longer shows "The requested page could not be found", and Foroverse can reach the forum to connect it. Found by @MaximilianKohler