WordPress database error: [Can't create/write to file '/tmp/#sql-temptable-4db-152498-4c.MAI' (Errcode: 28 "No space left on device")]SELECT p.* FROM wp_mdb_forum_posts AS p LEFT JOIN wp_mdb_forum_posts AS q ON( q.Id = p.ParentId AND p.Id = q.AcceptedAnswerId ) WHERE p.PostTypeId = 2 AND p.ParentId = 118605 GROUP BY p.Id ORDER BY CASE WHEN q.Id IS NOT NULL THEN 1 ELSE 0 END DESC, p.UpvoteCount DESC, p.CreationDate ASC
Topic: MDBTextarea not updating when isValid and isValidated props change
Hello,
I encountered a bug with the MDBTextarea component. The MDBTextarea component does not show the validation message when the validation props change.
I am using server side validation with MDBTextarea like so:
<MDBTextarea
:label="title"
v-model="data.content"
:invalid-feedback="getValidationMsg('content')"
:is-valid="isValid('content')"
:is-validated="validated"
/>
This works fine for the MDBInput component, but not for the MDBTextarea component.
I looked in the source code and found that the isInputValidated
and isInputValid
refs are never updated, when the props.isValidated
and props.isValid
have changed.
In MDBInput component these refs get updated through watchers like so:
watch(
() => props.isValidated,
(value) => (isInputValidated.value = value)
);
watch(
() => props.isValid,
(value) => (isInputValid.value = value)
);
Expected behavior
The MDBTextarea component to show validation messages when the validation props change.
Actual behavior
The MDBTextarea component does not show validation messages when the validation props change.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Answered
- User: Pro
- Premium support: Yes
- Technology: MDB Vue
- MDB Version: MDB5 1.11.0
- Device: n/a
- Browser: n/a
- OS: n/a
- Provided sample code: No
- Provided link: No
Mikołaj Smoleński staff commented 3 years ago
Thanks for posting an issue. We're going to fix it as soon as possible.
Keep coding, Mikołaj from MDB
Mikołaj Smoleński staff commented 3 years ago
@ it should be fixed with upcoming today 1.12.0 version of our UI KIT.
Keep coding, Mikołaj from MDB