NottingHack / NottingHack/hms2

Email All Members Formatting Issues and Errors

Open
#502 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

front end
Dominant language
PHP
Stars
14
Forks
18
PR merge metrics
No merged PRs in 30d

Description

When composing an email using Email All Members and pasting from a Google Doc I initially received an error 500 on reviewing the form.

After some adjustments the error stopped happening (don't know why), but there were several formatting issues reflected in the output not visible in the preview.

I can provide the document I pasted from if that's useful, but the results have been inconsistently reproducible.

Additionally in one case I selected some text that had been implicitly made and hit the link button to change the link text, upon submitting the link dialog the link moved from where it was in the docuemtn to below the bottom of the text area where it could not be selected. Upon reloading the page (restoring the message) the URL of the link was appended to the end of the message and selectable again.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Email All Members compose, review, and submit flow, using pasted Google Docs content to investigate the reported 500 error and inconsistent formatting. Check the link-editing case where the link moves below the text area and the URL is appended after reload. Done means the flow handles pasted content consistently, preserves formatting and link placement, and no longer produces the review error.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.