-
Notifications
You must be signed in to change notification settings - Fork 1
Fix issue with demo content taxonomy names #97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Having it meant the entity reference field didn't work.
This reverts a commit I made to rename the demo content taxonomy names: dae0f9f This was done because people testing were confused about the duplicate parties when enabling the demo content and the UK parties module. I can't find the original issue, maybe it was in Slack? Either way, I think we need a way for user to distinguish between demo taxonomy terms and those generated by the UK parties module. But more fundamentally, I wonder why are brackets a problem in taxonomy term names in this instance. |
@finnlewis Ah I wasn't aware. Basically, entity references fields usally have stuff in the form Mabye square brackets would work? |
Handiest might be to change the names to |
@markconroy That's sensible. I'll make the change soon. |
I did try and do some validation in the form validation hook but could not get the full text from the input :/. It would be good to revisit that at some point as well. |
@markconroy @finnlewis @dedavidson Switched to using the dashes. @finnlewis this should fix your problem. |
Testing, thanks @chriswales95 ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works better now, thanks @chriswales95 !
Should close #91.
What this PR does: