- πͺπΈSpain alejico
It does not make sense to remove the option because there are already menus that have these options and now it gives validation error. For me it is a mistake. If you remove the option you have to leave the field as optional...
The change in #2693725 allowed users to enter <nolink> in place of a url in link fields, so placeholders could be created in menus or such.
The problem is that it this value can be entered into required link fields where you are trying to require users to enter a link. And not only does the field allow them to enter <nolink>, it specifically tells them in the field help text how to use it to bypass the requirement for entering a value.
If a link field is required, either <nolink> should not be allowed as a value, or there should be a setting to disable it in the field settings. At a minimum, the help text should not instruct users how to enter that value in required fields.
Active
11.0 π₯
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
It does not make sense to remove the option because there are already menus that have these options and now it gives validation error. For me it is a mistake. If you remove the option you have to leave the field as optional...