Very odd. Do you have any plugin installed? Could you try if you get the same error with mongrel (script/server) instead of thin?

Not sure what you mean with the C and @ part at the end, care to elaborate?

• redmine_todos_plugin
• stuff_to_do_plugin
• redmine_github_hook
• redmine_kanban

Will check script/server a bit later here once users are not in the system.

On the C / part it is regarding the formatting of messages here. They are not, it seems, displaying the markdown appropriately when I preview messages with these demarkation attributes. So for example, when I want to display inline code here in a message by pressing the C button, it only displays literally "@blah blah my code" when the text is multiline rather than being actually formatted as a monospaced typeface. Perhaps inline code line breaks are not supposed to be formatted as such?

George Plymale wrote:

I do have a few plugins enabled:

• redmine_todos_plugin
• stuff_to_do_plugin
• redmine_github_hook
• redmine_kanban

What version of ChiliProject are you on? If you're on 2 or later, see if any of the plugins has a acts_as_activity statement in it. If so, it's probably not been updated for ChiliProject 2.

On the C / part it is regarding the formatting of messages here. They are not, it seems, displaying the markdown appropriately when I preview messages with these demarkation attributes. So for example, when I want to display inline code here in a message by pressing the C button, it only displays literally "@blah blah my code" when the text is multiline rather than being actually formatted as a monospaced typeface. Perhaps inline code line breaks are not supposed to be formatted as such?

Yes, the @ syntax doesn't take multilines, you have to use the < pre>< /pre> (spaces added to avoid them firing) syntax for multiple lines.

Thanks for instructing me as to how to find those plugins. redmine_todos_plugin indeed has this present.

I am also seeing this in acts_as_journalized & acts_as_activity_provider, however since these are not add ons by me I'm assuming that those are appropriate for now.

Might I ask how would you properly remove a plugin? I did find with this same todos_plugin as well that on the db update after going from 2.0 to 2.1.1 that the db migrations attempt to create a db and fail so I had to remove those when updating.

George Plymale wrote:

Thanks for instructing me as to how to find those plugins. redmine_todos_plugin indeed has this present.

Then there's a 99% chance it hasn't been updated yet and thus incompatible. Try to deactivate it (give the folder 000 permissions and restart your server) and see if it works without it.

I am also seeing this in acts_as_journalized & acts_as_activity_provider, however since these are not add ons by me I'm assuming that those are appropriate for now.

acts_as_journalized replaces acts_as_versioned and wraps acts_as_activity_provider, the later meaning especially that no code should need to call it on its own, and inversely code calling it probably does it "the old way" and is thus incompatible.

Might I ask how would you properly remove a plugin? I did find with this same todos_plugin as well that on the db update after going from 2.0 to 2.1.1 that the db migrations attempt to create a db and fail so I had to remove those when updating.

If you just want to remove the plugin, removing the directory is enough. If you want to also remove any data the plugin has created in the DB, run rake db:migrate:plugin NAME=name_of_the_directory VERSION=0. This will run the down migrations of the plugin, which if the author created them the standard way will contain instructions to remove its data from the DB, make sure to have a backup though, you never know! For completeness, I'll also point to the plugin's assets that are copied to public/plugins/plugin_name (or something like that), but there's very little chance they'll bother you in the future.