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

Implemented: Url link shorten handler workflow event option drop down menu #12


Copy link

Implemented: Url link shorten handler workflow event option drop down menu

Hello NXC,

The system of url link shorten handlers was previously only configurable via ini settings which as we all know is not the most user friendly for website administrators or other end users.

Our pull request changes the configuration flexibility of the url link shorten handler system by allowing the link handler ('service') used to shorten urls to be chosen per social network via workflow event options in the admin.

The default link shortening service is still ''. We support this by default because it does not require an api key to use the service and is the most reliable/available.

The order of link shortening services / handlers displayed in the workflow event options dropdown is configurable via ini settings order, first listed, first displayed.

We think this improvement is worth of a pull request because it increases the flexibility from just one choice for link shortening service for all possible uses to a unique link shortening service choice for each workflow event social network.

Please let us know what you think!

Brookins Consulting

@brookinsconsulting brookinsconsulting force-pushed the link-shorten-handler-dropdown-menu-option branch from 6a36bc7 to 3585597 Compare October 12, 2014 17:05
@SerheyDolgushev SerheyDolgushev merged commit 3585597 into nxc:master Oct 16, 2014
@brookinsconsulting brookinsconsulting deleted the link-shorten-handler-dropdown-menu-option branch October 25, 2014 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

None yet

2 participants