WordPress database error: [Can't create/write to file '/tmp/#sql-temptable-4db-59ed25-2f.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 = 115508 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: Issue disabling inputs using FormControl and mdb-form-control
Dave Moniz
premium priority asked 4 years ago
Expected behavior
Setting a FormControl to be disabled using the recommended method should work
Actual behavior
It doesn't. Additionally, doing it the way recommended in the MDB documentation ( [disabled]="true" ) throws a angular warning
Resources (screenshots, code snippets etc.)
HTML
<mdb-form-control>
<input mdbInput [mdbValidate]="true" id="firstname" name="firstname" formControlName="firstnameControl" type="text" class="form-control">
<label mdbLabel for="firstname" class="form-label">First name</label>
<mdb-error *ngIf="(firstnameControl?.invalid && (firstnameControl?.dirty || firstnameControl?.touched))">This must not be blank</mdb-error>
<mdb-success *ngIf="firstnameControl?.valid && (firstnameControl?.dirty || firstnameControl?.touched)"></mdb-success>
</mdb-form-control>
TS
this.formGroup = new FormGroup({
firstnameControl: new FormControl({
value: this.firstname, disabled: true }, {
validators: [Validators.required], updateOn: 'change'
})
});
using the code (above) does not result in a disabled field, additionally this does not disable the field: this.firstnameControl.disable();
Closed
This topic is closed.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Closed
- User: Free
- Premium support: No
- Technology: MDB Angular
- MDB Version: MDB5 1.0.0-beta5
- Device: PC
- Browser: Google Chrome
- OS: Arch Linux
- Provided sample code: No
- Provided link: No
Arkadiusz Idzikowski staff commented 4 years ago
@Dave Moniz We will take a closer look at this and add possibility to disable the control using Angular form control. For now, please use
[disabled]onmdbInput, Angular will always suggest to handle disabled state usingFormControloptions, but this warning should not be displayed in production build.