Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
I had it setup to pre-populate these fields with the site defaults, but that lead to another problem...
1) Site admin sets some global defaults
2) User edits their profile, not related to OpenURL, but, unbeknownst to them, the current global values are set for this user.
3) Site admin changes global defaults
4) User mentioned above still has old defaults and OpenURL doesn't work :-(
The way it is now, the user values will remain blank unless they are intentionally changed, this way a blank value can fall back to the global defaults.
Does that make sense?
Maybe, rather than pre-populating them with the defaults, the suggested defaults could be added to the descriptive text under the input box?
Comments
Comment #1
rjerome commentedShouldn't be a problem. Look for it in the next release, due out within the next week.
Ron.
Comment #2
jaydatema commentedThanks—will look for it.
Comment #3
jaydatema commentedThanks, the dev version works well. What do you think about prepopulating the OpenURL SiteID with the site name?
Comment #4
rjerome commentedI had it setup to pre-populate these fields with the site defaults, but that lead to another problem...
1) Site admin sets some global defaults
2) User edits their profile, not related to OpenURL, but, unbeknownst to them, the current global values are set for this user.
3) Site admin changes global defaults
4) User mentioned above still has old defaults and OpenURL doesn't work :-(
The way it is now, the user values will remain blank unless they are intentionally changed, this way a blank value can fall back to the global defaults.
Does that make sense?
Maybe, rather than pre-populating them with the defaults, the suggested defaults could be added to the descriptive text under the input box?
Ron.
Comment #5
rjerome commented