Skip Navigation

[Résolu] CT Description input is not a Multiline and other issues with

Ce fil est résolu. Voici une description du problème et la solution proposée.

Problem:
The Content Template Description is almost not to spot, and it's not a multiline as expected.

Solution:
Update to the latest Toolset Views version

This support ticket is created Il y a 5 années et 9 mois. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Aucun de nos assistants n'est disponible aujourd'hui sur le forum Jeu d'outils. Veuillez créer un ticket, et nous nous le traiterons dès notre prochaine connexion. Merci de votre compréhension.

Sun Mon Tue Wed Thu Fri Sat
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Ce sujet contient 12 réponses, a 2 voix.

Dernière mise à jour par julieP Il y a 5 années et 7 mois.

Assisté par: Beda.

Auteur
Publications
#1206175

Hi Beda
Thank you!

I've also noticed that where a description has been entered on a Content template or a View (in the field below the title & slug fields - see image), the text appears to be non editable. The text turns to a link on hover and that's when the text is editable.

It's a bit confusing and the size of the field in edit mode is far too small for most scenarios - can it be reverted to how it was in the previous version please??

#1206271

I cannot revert this, but I see the issue and what you mean.

I have asked permission to escalate this as a usability issue, it could, however, be that I will have to ask you to submit this as a feature request.
Please await my updates here, and please apologise for my apologies if the current setup is not perfect.

I will be here with news hopefully tomorrow.

#1206346

Hi Beda

This is actually a change from what it was before the latest updates so hardly a contender for a feature request!

I've since noticed that this might only be happening in templates/views that contained text in that field prior to the updates. Does that help?

#1206777

I could escalate this as a usability issue, also because this happens on all kind of CT or View or Archives, as far I saw, and my colleagues all agreed that in this case, "intended to be like that does not mean it's correct".

Hence we created an internal task for our Developers to review this and make it more user-friendly.

Do you have any particular wish or idea of how it should be, or where you just happy with how it was?
I can share this with the developers, so we can consider it.
(I know you are a very active user, so I am sure you have also very founded experience/ideas on the matter)

Thanks a lot for investing the time in feedbacking to us, Julie.

#1206902

Hi Beda

That would be great - thank you!

I was actually quite happy with how that field functioned before the upgrade (i.e. full width multiple line field with white background that we just clicked into to edit) and it did the job required.

I've found this field especially valuable with larger, more complex sites; it can get quite complicated with the use of Content Templates, Views, Post Forms and post edit links and therefore harder to locate specific content if there's an issue or if something needs changing.

I suspect maybe the change wasn't intentional (??) so hopefully it will be easy to reinstate the previous format!!

#1206908

I fear the change was intentional, it is part of the new static top edit bar, which I remember being presented in our internal training as well, my mind somehow did not realize what we were about to release and I did not think about it further.

I have mentioned your thoughts about the previous version being just what you need (and I agree with you) to the Developers.

I also hope a fast change will happen.

#1206910

BTW - I notice now there is a little "pencil" next to the Description (as well next to the Title)
That, if hovered, produces the link, and if clicked, the description can be edited.

I think the only reason this is so confusing is that the SLUG field is persisting as an input?
If all were marked with pencils, maybe it would be much more obvious to click?

I added screenshots.

This pencil is missing in the CT - but it's there in Views and Archives.
I think adding the pencil to all the fields is what is required instead of reverting back to what was?
Oh, and of course, make it MultiLine again, this is very annoying in a single line format (where you cannot hit enter to break lines either)

Agreed?
We keep the pencil on all edit fields but make it multiple lines?

#1207043

new static top edit bar

static in what way?? If you mean "sticky header" then only the title is sticky/static, the slug & description are not.

I think the only reason this is so confusing is that the SLUG field is persisting as an input?

Not IMHO! The slug field is in the style of a CRED field and we all know they are editable even without a pencil.

If all were marked with pencils, maybe it would be much more obvious to click?

Personally I prefer the three items to have a white background - they stand out that way and already look editable; with no difference in background, they don't look editable. Adding the pencil is a bonus.

I added screenshots.

???

Again, there was nothing wrong with the set up before the upgrade. I think you're over-egging the pudding.

#1207410

Ok, I apologise my wording was confusing - yes I meant the sticky header, those changes were made within the same process, to improve the experience of editing/creating those elements.

Related to the ScreenShots, it seems we have a problem in the forum, screenshots are not added when uploaded (I am talking to colleagues and admins to adjust that if possible)

About the actual core issue of this ticket, I already got feedback from the Developers.

1. The missing Pencil on CT edit screens is a BUG and we will fix it (put the pencil there)
2. The implementation including a single line and a pencil-on-hover was done following design instructions.
However, the developers agreed to reconsider using a Textarea instead of a single line text input. This will not happen immediately, though, and I cannot grant or state an ETA on it yet.

Please let me know if you want to be notified when the change is/are implemented, or if you prefer to follow the release changelog and/or blog?
In that case we should close the ticket here, otherwise, I can keep it escalated to developers and notify you when adequate about the update.

I apologise that I cannot change the situation to how it was before, these decisions are not within my hands.

#1207615

to improve the experience of editing/creating those elements

how anyone involved in the decision-making process can believe this experience is now improved is beyond me but what do I know; I only use it day in day out. "If it ain't broke, don't fix it".

Don't worry about keeping me informed of progress; I'll monitor it myself. Thanks for your help.

#1209837

I apologise for the disappointment.

Currently, to change (also a new) features in Toolset, this form would be the best way to reach out to the Plugin's Product Management and (as in this specific case) ask for a total rollback:
https://toolset.com/home/contact-us/suggest-a-new-feature-for-toolset/

This form can be used in general to suggest new features, but also such changes (in this case a rollback) to the Product Management.

#1231369

This was addressed in Views 2.8

#1232199

Hi Beda

Thanks for the update - suspect you didn't see this https://toolset.com/forums/topic/ct-description-field-one-for-beda/