Describe the bug
Deleting a Portal Module from Portal Modules main page only removes the module from the current view. Also, unlinking a module that's in use doesn't allow the save button to be enabled to save the new configuration.
To Reproduce
Steps to reproduce the behavior:
- Navigate to Configuration > Advanced Access Configuration > Portal Modules
- Click on a module at the bottom of the page and click the trash can icon.
- Item is removed from view but a refresh of the page returns the module.
Expected behavior
When deleting a module from the Portal Modules page it deletes the module like it does when you navigate to the module itself and delete it there. Also when unlinking a module it allows the Save button to be enabled so it can be saved.
Additional context
From what I could tell, this seems to be what it's calling which only removes it from the current view.
When navigating to the portal module itself and deleting it looks like it uses this which actually calls the API to delete it.
Describe the bug
Deleting a Portal Module from Portal Modules main page only removes the module from the current view. Also, unlinking a module that's in use doesn't allow the save button to be enabled to save the new configuration.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
When deleting a module from the Portal Modules page it deletes the module like it does when you navigate to the module itself and delete it there. Also when unlinking a module it allows the Save button to be enabled so it can be saved.
Additional context
From what I could tell, this seems to be what it's calling which only removes it from the current view.
packetfence/html/pfappserver/root/src/views/Configuration/portalModules/_components/PortalModuleButton.vue
Line 84 in 231aac0
When navigating to the portal module itself and deleting it looks like it uses this which actually calls the API to delete it.
packetfence/html/pfappserver/root/src/views/Configuration/portalModules/_components/TheList.vue
Line 280 in 231aac0