As confusing unexperienced administrators is not a bug, here the suggestion then.
Rename the XenForo ACP "Server" error log to not contain the word "Server". In fact, it does not store server errors but php errors, so the name is not only confusing for inexperienced users, but also technically...
Maybe a mood point, but from our experience the XenForo ACP error log should not be named "Server error log". We frequently have to explain to clients that it does not, as the name advertises, log/contain all server errors.
Noticed this on a client website today. On the add-on list, add-ons that have their titles first letter a [ will show a weird formatting, where the bracket ends up at the end of the title in mirrored form:
Not sure if this is something that can be solved with CSS or is just a downside of...
A few bugs/issues with the markdown conversion. I know some of them depend on the spec one uses, but from a user perspective, I'd probably expect all of them to work.
Single bullet point items are not converted to lists.
Numeric listings are not converted to...
Having a limited set of reactions doesn't seem to be timely anymore. Modern platforms such as discord or slack use a full emoji set as reactions, including all unicode emojis, and any custom emojis. Sometimes, the given 5, 10 or 15 reactions are just not enough. Content varies, and so do...
Most modern platforms allow their users to upload and user their own emojis for use across the platform, such as Twitch channel emotes, discord server emotes, telegram & line sticker packs, etc.
This suggestion basically consists out of two (and a half) parts:
The capability for users to...
As title. I guess this might've been done on purpose rather than being a code bug, but I think it's a usability bug either way. No user can be expected to understand that autocomplete only starts working after he opened the emoji menu at least once, and no popular program behaves like that either.
Using the browsers input field suggestions in conjunction with the field-adder will result in the new field being pre-populated with the previously selected value. Emptying the field will then generate an additional new field.
It appears to be impossible to use the new style property value grouping for theme-specific style properties without an attached add-on, as you're otherwise unable to ship the phrase for the group name.
Dropping existing items into the toolbar results in them being quietly dropped instead of being added. There should be some kind of feedback for the user as to why the item was not added has he might've expected. I found it highly confusing and it took me a good portion of time to figure out...
Since the update to 2.1.0 Beta, the addon.cache seems to not update properly anymore.
I currently have the following add-ons enabled:
Dumping the add-on cache doesn't show the UIX add-on:
New BB code button manager page is missing an "add dropdown" button or similar. Adding seems to be only accessible by directly typing the route into the address bar at the moment, or I'm missing the actual spot where it's located.
I've noticed that, while some places (BB Code areas entirely, I assume) use the custom BB Code font, other areas (such as thread titles) do not. I think this behavior creates a discrepancy where emoji style can vary greatly (such as in the case of flags). Makes me wonder if it wouldn't be better...
Opening the emoji menu on a mobile device results in a number of rendering phases, all in all taking sometimes several seconds to load, where first the pop-up will load, then the HTML structure inside of it, then the native emoji font and then the custom emoji font. All in all this seems a bit...