Open jacobsenj opened 3 years ago
I wasn't sure about Sebkln\\ContentSlug\\Evaluation\\FragmentEvaluation
in the eval key. Maybe it could be removed after the change to the slug type, too.
Thank you for your report. I'll look into Workspaces.
Please note: I did not apply your patch to test the exact behaviour. But you adjusted the TCA close to a former state of this extension. As you can see from the commit message, using the TCA type slug
made the fragment field mandatory. This may not be an issue for your project, but I want to keep this field optional.
When I finished the fragment hook for page links, I can revisit the TCA of the fragment field.
As you can see from the commit message, using the TCA type
slug
made the fragment field mandatory. This may not be an issue for your project, but I want to keep this field optional.
Thanks for pointing this out. Indeed, it would add a default-[a-z0-9]{10} value if the content element header would be empty, so i changed it to allow to stay empty if the header is empty using postModifiers in the tca configuration for the field. In my special use case it will make sense to have a slug for each content element where the header field is filled. By having it this way editors are not forced to set the slug initially after adding a content element.
Like you statet in issue #3 about language versions, there's an issue with the content slug and workspaces (versions of records), too.
I changed the tca of the field to use the slug type in TYPO3 core and added a prefix class with a local composer patch:
Now I'm totally allowed to stay on the defined content slug in the workspace version of the record:
Maybe this is of interest for you, too.
Cheers Jens