Name | Type |
---|---|
'ext' fields not displayed by name | tracker item |
snarlydwarf
Contributors |
tracker item |
eclvvin
Contributors |
tracker item |
daniam
Contributors |
tracker item |
Add support for all relevant microformats
hcal was added to 1.10! As this is an ongoing process, we'll use a wiki page to coordinate efforts. Please see: ((microformats)). |
tracker item |
Community Currencies | wiki |
Community/Customer/Constituent Relationship Management system (CRM)
Since this is vast project, we'll use a wiki page: ((CRM)) |
tracker item |
GroupMail
Project to perform many of the functions of CRM using as many existing Tiki features as possible (dev notes). |
wiki |
natokpe | tracker item |
Send direct message via tiki-user_information.php
The ((doc:Inter-User Messages)) system is quite nice. However, it means: 1- That users have duplicate mailboxes 2- And the recipient can't just click reply On dev.tikiwiki.org, this is not so nice because people already have an internal tiki mailbox on tikiwiki.org So, let's think about an additional/modified feature called "direct message" or "direct mail". This would simulate a regular email. (let's plan ahead that this should be able to send other types of messages (jabber, sms, etc.) The headers could be: "from" is Full Name ({$Username}) {senderemail} "to" is Full Name ({$Username}) {recipientemail} "bcc" to {senderemail} (So we have a trace of what we sent) In case some spammers get a hold of it, let's have something like this at the bottom: This message was sent via {$name of site} Not sure if this should be done with the ((doc:webmail)) feature, or maybe as an option of ((doc:Inter-User Messages)) See how MediaWiki does it for a good example: http://en.wikipedia.org/wiki/Special:EmailUser/Marclaporte |
tracker item |
SQL error saving a Contact | tracker item |
tiki_contact doesn't "shared" fields correctly.
'Shared' contacts don't shared the field names. If userA creates an entry with a 'custom' field of 'Company' as 'The Smith Company', we see this in the db: ||contactId|fieldId|value|hidden 1 | 7 |The Smith Company|0|| The problem is that other users do not 'inherit' that custom field: so other users seeing that record will see no description of the field name. Indeed, if another user chooses 'Company' from the list of fields to add, it will get a new fieldId: ||contactId | fieldId | value | hidden 1 | 7 | The Smith Company | 0 2 | 23 | Smith Industries | 0 || It should, especially for the predefined (semi-custom fields, like 'Company' and 'Street Address', defined in lib/webmail/contactlib.php) 'share' these values with others instead of creating new fieldId's. |
tracker item |
Using desktop mail client (ex.: Thunderbird) to reach Tiki contacts, groups or newsletter
Tiki newsletter works well for small volumes. But for large volumes, as with any web app, sending emails from a server can be a challenge. Risk of being flagged as spammer, high server load/difficult to throttle, limits from your web hosts (ex.: max x emails per hour), etc A helpful alternative would be something like this: https://addons.mozilla.org/en-US/thunderbird/addon/4883 So my Thunderbird client or desktop newsletter application (ex.: [http://gammadyne.com/mmail.htm|Gammadybe Mailer]) should be able to access the TikiWiki database to generate recipient list. --- Another approach is to make the Tiki contacts (address book) accessible via the LDAP protocol and thus, email clients can access. Related: http://www.egroupware.org/egroupware/index.php?menuaction=wiki.uiwiki.view&page=AddresbookAccountsConcept |
tracker item |
Save record.
When viewing, the name of the field is not displayed, even for the user that entered it.