cyclestreets / cyclestreets/cyclescape
Footers have lost thread links
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 34
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Until Sun, 09 Dec 2018 21:13:34 +0000 the footer of message included links to the thread the message came from. (and an unsubscribe link)
After that the footer contains no useful info. This is a regressing - those links were very useful for when people posted images or documents. It looks as if those links are intended to be still there, but have just got lost?
First message I got in the new style: Sun, 09 Dec 2018 21:42:26 +0000
Old footer:
You can reply to the email and the message will be added to the thread.
Only members of Cambridge Cycling Campaign can view
and post messages to this discussion thread.
You can stop following this thread by visiting
http://www.cyclescape.org/threads/4458/subscriptions/603284/edit?t=[filtered]
Cyclescape discussion thread:
http://www.cyclescape.org/threads/4458#message_58077
New footer:
From Cyclescape discussion thread.
You can reply to the email and the message will be added to the thread.
Only members of Cambridge Cycling Campaign can view and post messages to this
discussion thread.
You can stop following this thread.
Whilst messing in this area, if it is possible to include a link to uploaded images or documents associated with that post, that would be great - one could just download them with that.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The payload names no source file or test entry point. Start by tracing where discussion-email footers are generated and compare the old and new footer examples; done means restoring the thread and unsubscribe links, with attachment links only if that scope is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100