Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Any reason why this was not converted to config?
I mean we definitely should not introduce a UI for this, but I don't get why this is environment-specific. If for some reason you want the value to be lower I guess you would want to deploy that, no?
it seems to me that this value would change per server..eg in my dev server i want to have it to 0...on my live at 180 or more
i am fine though reverting this and turning to config, i just want to get rid of the variable_get call there http://drupal.org/node/1775842#comment-7297152
Comments
Comment #1
ParisLiakos CreditAttribution: ParisLiakos commentedComment #2
ParisLiakos CreditAttribution: ParisLiakos commentedupgrade path will be added here #1921822: Take account of drupal_hash_salt during migration path from 7.x
Comment #3
Crell CreditAttribution: Crell commentedTagging, because I didn't even see this...
Comment #4
Crell CreditAttribution: Crell commentedAnd it looks like a nice and straightforward conversion.
Comment #5
alexpottCommitted bb1817e and pushed to 8.x. Thanks!
Comment #6
tstoecklerAny reason why this was not converted to config?
I mean we definitely should not introduce a UI for this, but I don't get why this is environment-specific. If for some reason you want the value to be lower I guess you would want to deploy that, no?
Comment #7
alexpottI had assumed that this was used before the config system is available
Comment #8
ParisLiakos CreditAttribution: ParisLiakos commentedit seems to me that this value would change per server..eg in my dev server i want to have it to 0...on my live at 180 or more
i am fine though reverting this and turning to config, i just want to get rid of the variable_get call there
http://drupal.org/node/1775842#comment-7297152