View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0017031 | mantisbt | plug-ins | public | 2014-02-25 10:14 | 2014-03-15 11:59 |
Reporter | manunuma | Assigned To | dregad | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | Linux | OS | Debian | ||
Product Version | 1.2.16 | ||||
Summary | 0017031: Problem with ManTweet plugin | ||||
Description | Hello, I installed the ManTweet plugin, I confired it on a local using. "Database query failed. Error received from database was 0001064: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '2014-02-25 16:12:46'', ''2014-02-25 16:12:46'')' at line 1 for the query: INSERT INTO mantis_plugin_ManTweet_updates_table ( author_id, status, date_submitted, date_updated ) VALUES (?, ?, ''2014-02-25 16:12:46'', ''2014-02-25 16:12:46''). Could somebody help me please. Manu. | ||||
Tags | No tags attached. | ||||
This is not a bug or feature request for MantisBT. Please report issue for this plugin at https://github.com/mantisbt-plugins/mantweet |
|
ok, thanks, I will do it. |
|
Reminder sent to: vboctor The README at https://github.com/mantisbt-plugins/mantweet tells users to enter bugs on http://www.mantisbt.org/bugs Unfortunately the bug reporting is also enabled at GitHub and there are some reports in it. Wouldn't it be better to have a project "Plugins - ManTweet" instead of hosting the bug reporting at GitHub? |
|
It was me who enabled the issue tracker at github, because there was no specific project on mantisbt.org for the plugin and it was less effort than to create one here. I also believe that for plugins (especially small ones) having a project here is too much overhead. In short, I would suggest to update the plugin's README unless Victor objects. |
|
Should we have a standard model for plugins independent of their size? I kind of agree with the with dregard's point about the issue of possibly having too many lightly used projects in this tracker. I also wonder if there are plugins that are big enough that are going to have requirements beyond the simple githbub tracking. My question is whether we should have a consistent model. Here are some options:
I'm thinking that 4 may be good enough. If not, then I would choose a consistent model from the others. |
|