Feature proposal #5407closed
Hardcode support for core activity
Connections are a part of core CB and it's safe to hardcode support for their activity output based off the parent value. This is already the case for status and field activity and connections usage is also already hardcoded in so there's no harm in this.
Updated by krileon about 8 years ago
Should just be the simple string that it is, but it needs to be more translatable. Maybe instead of hardcoding this the parsing be improved to better generate a translatable string. For example it could just be a tag! Example as follows.
Title: is now connected
'is now connected' => 'is now connected'
'with [tags]' => 'with [tags]'
is now connected with USERNAME
Only problem with this is tags will become subcontent since a title is specified so the display needs to be looked at further. Location and Tags probably shouldn't do a subcontent display. Display needs further review for this to work fluidly.
Updated by krileon almost 8 years ago
- Subject changed from Hardcode support for connections activity to Hardcode support for core activity
This should apply to all core activity. There should be built in access and display parsing for them. Implement this usage via triggers instead of hardcoding it into the HTML. Each core activity type should have its own template file as well.
The current hardcoded outputs should also probably become their own template files.