Is there a security risk in creating users (pragmatically) with a null password?
We tested sign in with no password and it doesnt allow leaving password empty. We tested basic auth with JSON:API and the user doesnt get authenticated (403 is returned). What else could be at risk?
Hallo I am trying to check for a field content of a term to trigger a selection criteria in Page Manager but got stuck at retrieving the term from the context. Any hint?
I have a content type called "Resources" and this has 2 taxonomy terms "Main folder" and "Subfolder". When I create content for the Resources content type, I choose a main folder and subfolder combination. I have a view created based on this content type and the view has "Main folder" and "Subfolder" fields exposed for filtering.
When I select the main folder option, I want to populate the subfolder with the corresponding options from the backend. For example, if my data on the backend is as below:
Hello everybody! :) I'm getting straight to the point.
So, my goal is to extend menu links so that they can not only have other (manually created) menu links as children but also (upon frontend rendering) have an additional list of automatically created child links. As an example, a menu link could have an additional reference field to a taxonomy term and then all taxonomy terms beneath that term would get rendered as menu link children in the frontend, possibly even nested.
In the user profile page, I have 2 taxonomy terms - class and group. When creating every user, a class and group will be selected. So the user details will be like : "User A, class - Respondents,group - Generic". There is a message board tied to default comment. So when the users comment on the messag eboard, it should mention: "Submitted by User A, Respondents, Generic". Right now, "Submitted by" shows only the user name. Is there a way to attach the 2 associated fields to this?