WordPress database error: [Can't create/write to file '/tmp/#sql-temptable-4db-5c9b03-12d.MAI' (Errcode: 28 "No space left on device")]
SELECT p.*, o.option_value, GROUP_CONCAT(DISTINCT CONCAT(m.meta_key, "::", m.meta_value) separator "::::") as seo_meta, t.slug, tr.language_code as language FROM wp_posts p JOIN wp_postmeta m ON p.ID = m.post_id JOIN wp_options o ON o.option_name = "siteurl" JOIN wp_term_relationships r ON r.object_id = p.ID JOIN wp_term_taxonomy x ON x.term_taxonomy_id = r.term_taxonomy_id JOIN wp_terms t ON t.term_id = x.term_id JOIN wp_icl_translations tr ON p.ID = tr.element_id WHERE post_type = "page" AND post_status = "publish" AND tr.language_code = 'en' AND t.slug IN ('jquery') AND x.taxonomy = "page_cat" AND tr.element_type = "post_page" AND meta_key IN ("_yoast_wpseo_title", "_yoast_wpseo_metadesc") GROUP BY p.ID

WordPress database error: [Can't create/write to file '/tmp/#sql-temptable-4db-5c9b03-12e.MAI' (Errcode: 28 "No space left on device")]
SHOW FULL COLUMNS FROM `wp_options`

Timepicker - Critical Feature Requests

WordPress database error: [Can't create/write to file '/tmp/#sql-temptable-4db-5c9b03-12f.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 = 105799 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: Timepicker - "Critical" Feature Requests

ECKD Service Gmbh pro premium priority asked 6 years ago

Requests (ordered by importance)

  1. "Clear" Button Text can be changed by @input (config or single prop). We need to support multiple languages and therefor need dynamic configuration of labels (like Datepicker Component).
  2. Position of Clear and Done Buttons can be changed by @input. Currently, they are in wrong order from our point of view (every "save" or "done" action is normally on the right while dismiss is on the left.) Currently, for both the above problems, we have to adjust position & button content with custom scss. This is extremly fragile & can break very easy if your timepicker class / html structure changes in the future.
  3. @Output for timeCleared (or emit timeChanged with empty value). Currently, no event is raised, and even registerOnChange / onChangeCb can't be used because it isn't called in close() function, which is called for the Clear action. Currently we have to use registerOnTouched as a workaround to notifiy clear.
  4. Add an (configurable) icon or button as a timepicker indicator at the end of the input (like Datepicker). Increases recognition of time picker inputs. Additional, you could provide an option to prevent input click from opening the timepicker (like the focus @input) and just open it from the icon / button.
  5. Behaviour & @Input for save selection and close picker after hour and minute selected. Could be an easy way to reduce clicks for power users.

Currently we have to do some workarounds / "dirty" hacks to use the timepicker. It would be nice if at least the labeling, button positioning & the @output events would work as described. Of course, if I missed something and there are already viable options to reach the expected behaviour I'd be happy about every hint.


Konrad Stępień staff commented 6 years ago

Hi @ECKD Service Gmbh,

Thank you for your suggestions!

Currently, I do refactor time picker component and I planned to use implement points 1, 2, 4 for this moment. Also, I will look at the other options and try to implement these elements as best as possible for customizing by user.

However, the implementation of this component will be planned in a few more releases, so you can tell what you have the biggest problems with and I will try to remedy it faster if possible.


ECKD Service Gmbh pro premium priority commented 6 years ago

Thank you for your answer, sounds great! Currently the biggest problems are the "Clear" label & the positions of the buttons. It would be great if this would be configurable because it's basically against our UX Design Guide. An @Output for timeCleared would also be great, but we have a workaround for now so this is less important.

We're looking forward to the future component :)


Konrad Stępień staff commented 6 years ago

Hi @ECKD Service Gmbh,

I will add these features for actual time picker maybe in next release.

Best regard, Konrad. :)


Konrad Stępień staff commented 6 years ago

Hi @ECKD Service Gmbh,

My suggestions:

Inputs:

  1. buttonClearLabel
  2. ampmClass (this is wrapper)
  3. footerClass

And for example if you want to display buttons (Done & clear) inline , just set [footerClass]="d-flex".

This solution is good for you?


ECKD Service Gmbh pro premium priority commented 6 years ago

Great work, with the new version we were able to remove every workaround we had to implement before, thank you very much!


Please insert min. 20 characters.

FREE CONSULTATION

Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.

Status

Resolved

Specification of the issue
  • User: Pro
  • Premium support: Yes
  • Technology: MDB Angular
  • MDB Version: 8.8.2
  • Device: All
  • Browser: All
  • OS: All
  • Provided sample code: No
  • Provided link: No