Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Sending a message doesn't work #440

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments
Closed

Sending a message doesn't work #440

openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments

Comments

@openstreetmap-trac
Copy link

Reporter: bruce.cowan[at]dsl.pipex.com
[Submitted to the original trac issue database at 12.14pm, Tuesday, 8th May 2007]

Sending a message fails, error message is as follows:

Application error

Change this error message for exceptions thrown outside of an action (like in Dispatcher setups or broken Ruby code) in public/500.html

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 2.07pm, Monday, 28th May 2007]

The problem is that app/controllers/message_controller.rb is not setting message.user_id and the database requires that column to be non-null so we get an error when inserting the message.

I'm not sure what the user_id field in the messages table is for anyway? It already has from_user_id and to_user_id to indicate sender and recipient?

@openstreetmap-trac
Copy link
Author

Author: dan[at]karran.net
[Added to the original trac issue at 11.40am, Thursday, 21st June 2007]

Curious as to why this works on my local install but not the server version?

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 11.59am, Monday, 2nd July 2007]

This will be fixed as part of the database schema update I am working on, which will remove the problem column from the messages tables.

@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 10.49pm, Saturday, 18th August 2007]

This is now fixed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant