Skip to content
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

Invalid default scenarios: Follow up to #528 #540

Merged

Conversation

ikedas
Copy link
Member

@ikedas ikedas commented Jan 28, 2019

Please comment on #528.

…be specified by corresponding robot/site parameters, instead of creating file or link named "*.default".

Defaults by older manner will be detected and written in sympa.conf/robot.conf during upgrading process.
…fined) was used instead of the value itself.

Fixed by removing a code replacing value "default". Exception is the case of scenarios: For compatibility, special value "default" will stand for default scenario name.
@ikedas ikedas mentioned this pull request Jan 28, 2019
@ikedas ikedas changed the title Invalid default scenarios addition: Follow up to #528 Invalid default scenarios: Follow up to #528 Jan 28, 2019
@dverdin
Copy link
Contributor

dverdin commented Jan 29, 2019

Very good complement to #528 . I agree.

@ikedas ikedas merged commit 9d8a9da into sympa-community:sympa-6.2 Jan 30, 2019
@ikedas ikedas deleted the invalid_default_scenarios-addition branch February 1, 2019 02:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants