keep custom alias and enable forwarding #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
hey there, i switched the vacation-plugin of my setup today, after upgrading rc, so i had to dive into this again.
according to the sql-driver: i combined @lluis solution for keeping custom aliases with the need of forwarding. so here is an other set of default sql.
this is still not perfect! since the user, in order to remove a forwarding would have to deactivate that without changing the forwarding adresses. so one should either lock editing the forwarder, while the responder is active or keep track of the previous forwarder and provide it in a variable in order to remove it. also a checkbox to enable, disable forwarding separatly would be great. i didnt have the time today to dive deeper into the rc-pluginstuff, so i leave it as is and hope someone else who knows the rc-stuff is going to do that.
i also did little on the layout.
changes:
config.inc.php.dist
vacation.php
todo: