Search results

By default XenForo prevents disabled/rejected users from being able to actually touch most parts of the site, often before any user-group permissions are check.

XF2 has a design flaw where it aggressively invalidates every CSS cache for each template imported from an add-on, and then for every template a template modification matches. For an active forum updating or installing a large add-on; this results in the css being invalidated very frequently...

This isn't fully implemented in the XF2 version yet, most of the ground work is done for the next version but AFAIK @NixFifty hasn't finished it off yet.

This might be an ElasticSearch v6 issue, as I think some of the mapping information for Tickets has changed. And ElasticSearch v6 is much less forgiving of that.

The last time this happened, some users where on the wrong language somehow and weren't picking up the expected phrasing.

It looked similar :D

this also affects converted threads to tickets

@NixFifty also missing these phrases; nft_disable_font_awesome nft_all_pages nft_no_categories

Yeaaah. Extending the profile tabs stuff is messy. Should be fixed in an Elastic Search Essentials update.

Looks like the phrase "nf_tickets_sub_categories" is missing:

On the 1st post of the 2nd page of a multi-page ticket, there is an off-by-1 error which causes the navbar to not show up . In _getDefaultViewParams 'totalMessages' => $ticket['reply_count'], Should be: 'totalMessages' => $ticket['reply_count'] + 1,

Currently when looking at permissions (ticket permissions or per category) there is no UI feedback on which groups have permissions. Under node permissions, the row is highlighted/selected if a group has permissions

I will likely be interested in this as well.