-
Notifications
You must be signed in to change notification settings - Fork 506
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
USH-684: add HttpSMS data-provider entry , other clean-up
- Loading branch information
Showing
3 changed files
with
3 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,7 +3,7 @@ | |
namespace Ushahidi\Addons\HttpSMS; | ||
|
||
/** | ||
* Infobip Data Source | ||
* HttpSMS Data Source | ||
* | ||
* @author Ushahidi Team <[email protected]> | ||
* @package Addons\HttpSMS | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Without this line, deployments won't look for these new data providers. With this missing in the code, a similar entry needs to be added to the config table JSON (group_name="data-provider", config_key="providers"). It seems like this db update was manually done in staging environments, and I bet local too, then forgotten in regards of the implications for other deployments. Let's not forget again.