SEO: Show warning when meta title exceeds 55 characters and meta description exceeds 155 characters #21
SEO: Show warning when meta title exceeds 55 characters and meta description exceeds 155 characters #21iRohitSingh wants to merge 2 commits intomainfrom
Conversation
iRohitSingh
commented
Feb 25, 2025
iRohitSingh
commented
…ription exceeds 155 characters
|
|
davisagli
left a comment
davisagli
left a comment
There was a problem hiding this comment.
Setting max_length on the field is a hard limit (trying to save a longer value will be blocked with an error). In the related issues, @tisto asked for a warning only. (That is, we should inform the user that the value is longer than ideal, but not prevent saving it.)
There isn't any existing framework for adding warnings like this from the backend, and kitconcept.seo doesn't have a corresponding frontend package, so I don't see how we can do this easily. /cc @sneridagh
|
@davisagli is correct. I did not ask for a hard limit but rather a "warning" that shows up. @danalvrz showed me a prototype of this some time ago. Maybe we can introduce some infrastructure to Plone/Volto to allow us to define warnings. |
|
@tisto @davisagli I did some research, and it seems is a rather asked feature to support from form libraries. However, anything standard, as far as I can see. From here, anything that we do has to be hardcoded into the widgets themselves. We could achieve it in a per widget basis, for every widget we would have to add the support and hardcode the warning. If we try to come up with a spec, I guess it won't be simple... Having them in a generic way would take time. |
|
@sneridagh what if we use a custom widget at first and then generalize the thing once we gain some experience with it? |
|
@tisto we can do that, for sure. Next question is where to put it, I guess in VLT... @iRohitSingh can you take care of that also? Then use a widget hint in the field definition that the new widget can catch up and apply the patched widget. |
|
@sneridagh I am ok with putting this in VLT. In the long run it should go into Plone core I guess... |
|
Closing, superseded by #27 |
4 participants
