-
February 19, 2019 10:46 AM
Regular MemberPage editor: Reorder title field before categories field. In XF2.x, add "Required" hint/placeholder and "No prefix" label
Please consider switching the order of "Title" and "Categories" in VaultWiki 4.1. I think it makes more sense to position Title first, as this field is always required. In XF2.x, perhaps also add a "Required" hint, either under the Title label or as a textbox field placeholder, e.g.:
A few times, members on my public site with VaultWiki 4.0 / XF1.5 have either gotten confused and tried entering a title into the category input. Other times they've assumed that all fields below the main textarea are required.Code:<xf:formrow hint="{{ phrase('required') }}" ... or <input placeholder="{{ phrase('required') }}" ...
N.B. XenForo already uses phrase('required') as a hint for custom user profile fields where an admin has toggled "Field is required" to true, under the general options tab.
---
For the Prefix select form (when present), what are your thoughts with adjusting the "" (blank) label to instead say "(No prefix)" ? With this change, it would more clearly explain to the user what the field is for and also match XenForo 2.x with their thread prefix selection, phrase('(no_prefix)'). Otherwise, adding a custom empty phrase would at least give admins an opportunity for filling in placeholder text if they wanted to.
(image source: XenForo)
Issue Details
Issue Number
5656
Issue Type
Feature
Project
VaultWiki 4.x Series
Category Editing Pages
Status Implemented
Priority 5 - Minor Bugs / Small Tweaks
Suggested Version 4.1.0 Alpha 2
Implemented Version 4.1.0 RC 3
Milestone (none)
Software DependencyAny
License TypePaid
Votes for this feature
0
Votes against this feature
0
Assigned Users
(none)
Tags
-
May 3, 2019 11:28 AM
Regular MemberWhat I'm suggesting is something like this:
Attachment 1667
In the above attachment, the title (prefix) row is the first row after the editor. I added the class "formRow--input" (rowtype="input") in order to fix the label positioning. Additionally, the containing div for the prefix select element and title field was wrapped in an inputGroup div.
The browser HTML for this mock up is:
Obviously the above HTML is no good as-is, since it lacks phrases, variables, loops etc etc. Nevertheless, it gives you an idea for what might need to change in the relevant templates.Code:<dl class="formRow formRow--input"> <dt> <div class="formRow-labelWrapper"> <label class="formRow-label">Title</label> </div> </dt> <dd> <div class="vw-editor-prefix-title inputGroup inputGroup--joined"> <select name="prefixid" class="input input--inline"> <option value="0" selected="selected">(No prefix)</option> <option value="1">Special</option> </select> <input type="text" class="input input--inline" name="edittitle" value="" maxlength="125" placeholder="Title (required)"> </div> </dd> </dl>
-
May 7, 2019 4:55 AM
-
March 21, 2020 1:11 AM
Please Wait
This site uses cookies to help personalize content, to tailor your experience, and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
By continuing to use this site, you are consenting to our use of cookies.