Table "ush_smsautomate" cannot be found in the database.

[terrydangwa]

i have just downloaded sms automate plugin and extracted it to plugins folder.when i activated it in the admin section i got the error below

C:/xampp/htdocs/ushahidi/application/libraries/drivers/Database/Mysql.php [316]:

Table "ush_smsautomate" cannot be found in the database. Please make sure you are using the latest version of the database for this version of Ushahidi.

[rjmackay]

Can you check if a table named 'smsautomate' was created in your database?
Also can you confirm the plugin folder is named 'smsautomate' ?

You should also log this issue with the plugin author here: https://github.com/jetherton/smsautomate/issues

[srutto]

Tested this on 2.6.1. The plugin folder has to be named 'smsautomate' NOT 'smsautomate-master', that's why it's throwing the error. @terrydangwa like Robbie asked, please confirm the folder is named correctly.

[lbell]

Arghhhh!!! Ran into this while testing 2.7b -- thought it a bug, possibly my setup, hunted for hours for a solution, re-installed twice (over dial-up internet) before I found this issue...

Shouldn't plugin folders be able to be named anything -- with any calls to the directory being relative such as:

<?php 
dirname(__FILE__); 
?>

I know Wordpress includes a helper function: plugin_basename($file); etc.

Granted this is a plugin author issue -- but seems there should be best-practices guidelines. Thanks!

[aoduor]

Thanks for the heads up @lbell, this(best-practices/guidelines for building plugins) is definitely something we should have.

On Apr 24, 2013, at 12:42 PM, LBell notifications@github.com wrote:

Arghhhh!!! Ran into this while testing 2.7b -- thought it a bug, possibly my setup, hunted for hours for a solution, re-installed twice (over dial-up internet) before I found this issue...

Shouldn't plugin folders be able to be named anything -- with any calls to the directory being relative such as:

I know Wordpress includes a helper function: plugin_basename($file); etc.

Granted this is a plugin author issue -- but seems there should be best-practices guidelines. Thanks!

—
Reply to this email directly or view it on GitHub.

[aoduor]

Alrighty - seems like this is a naming convention problem/Plugin author issue. Closing :).

Edits should and will be made to plugin best practice guidelines.