Opened 3 years ago

Last modified 3 years ago

#2189 new improve feature

Suggestion 91: Add a subject for messages

Reported by: shevek Owned by: shevek
Priority: major Milestone: unassigned
Component: BW Mail Keywords:
Cc:

Description

See http://www.bewelcome.org/suggestions/91/results second topic in the option 'Add common message features'.

Change History (12)

comment:1 Changed 3 years ago by shevek

The following DB change will be necessary:

ALTER TABLE messages ADD Subject VARCHAR(70) CHARACTER SET utf8 COLLATE utf8_general_ci NULL COMMENT 'Contains the subject of a message sent between members' AFTER MessageType;

Last edited 3 years ago by shevek (previous) (diff)

comment:2 Changed 3 years ago by crumbking

there is a

Notice: Undefined variable: subject in /var/rox/deployment/alpha.bewelcome.org-3e30f69/build/messages/templates/compose.php on line 84

on alpha

comment:3 Changed 3 years ago by crumbking

Notice: Undefined property: stdClass::$Subject in /var/rox/deployment/alpha.bewelcome.org-3e30f69/build/messages/mailbox.widget.php on line 92

comment:4 Changed 3 years ago by shevek

@crumbking: Yes, unfortunately that's the case. Reason is simply that the missing DB update didn't workout yesterday. I try to get that fixed now.

comment:5 Changed 3 years ago by leoalone

having to touch that table would not be the case to add also 2 date fields, one numeric and two text fields to be used in case of hospitality request [suggestion 60] ?

or is better to add an enum field to say "this is an hospitality request" (or other special thing of message) and then have a different table for the other information ?

comment:6 Changed 3 years ago by shevek

The table already has a field for the message type, so that can simply be extended with a new flag.

comment:7 Changed 3 years ago by shevek

  • Milestone changed from 2.5 to backlog

Reverted the commit as the DB table update seems to block the server.

comment:8 Changed 3 years ago by leoalone

Would not be the case to use a different database for messages, completely separate from the main one (that is having at least five databases, one that holds only the passwords, the second the current one depurated by the messages and the forum/groups and finally the fifth with geocodes?

this ways even if having to open more than one sql istance, the system would be more robust.

comment:9 Changed 3 years ago by shevek

  • Milestone changed from backlog to 2.6

Added to milestone 2.6. Technical solution to be different than outlined above. See ThreadingMessages for details.

comment:10 Changed 3 years ago by crumbking

Should we remove it from 2.6?

comment:11 Changed 3 years ago by shevek

  • Milestone changed from 2.6 to 2.7

Moved to 2.7

comment:12 Changed 3 years ago by beatnickgr

  • Milestone changed from 2.7 to unassigned

Unassigned, as crumbking requested.

Note: See TracTickets for help on using tickets.