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

feature/enable-disable-profiles #3175

Merged

Conversation

jrouzierinverse
Copy link
Member

Description

Allow profiles to enabled/disabled

Impacts

Captive Portal/ ProfileFactory

Issue

Fixes #3170

NEWS file entries

Enhancements

  • Allow profiles to be enabled/disabled

@jrouzierinverse jrouzierinverse added this to the PacketFence-8.1 milestone Apr 23, 2018
@jrouzierinverse
Copy link
Member Author

@fdurand
Copy link
Member

fdurand commented May 26, 2018

it miss status parameter in the checkup.

checkbox_value => 'enabled',
unchecked_value => 'disabled',
tags => { after_element => \&help,
help => 'If profile is disabled it will not be presented to the user' },
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really true, a connection profile is instantiate in multiples cases.
So something like that: If profile is disabled it will not be used.

@jrouzierinverse
Copy link
Member Author

Updated

@fdurand
Copy link
Member

fdurand commented Jun 1, 2018

Can you rebase ?

@jrouzierinverse jrouzierinverse force-pushed the feature/enable-disable-profiles branch from 90682e0 to e370013 Compare June 1, 2018 16:31
@jrouzierinverse
Copy link
Member Author

Done

@fdurand fdurand merged commit d9f1fb8 into inverse-inc:devel Jun 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants