Closed Bug 744631 Opened 13 years ago Closed 13 years ago

Add 'I need help with Firefox issue' to Get Involved page form

Categories

(www.mozilla.org :: General, defect)

Product:
www.mozilla.org
Component:
General
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: davidwboswell, Assigned: jlong)

References

(
URL
)

Details

Attachments

(1 file)

File to add at https://github.com/mozilla/bedrock/tree/master/apps/mozorg/templates/emails/issue.txt
331 bytes, text/plain
Details
A lot of support questions come through the Get Involved page form and it would help channel those to add something in the 'Area of Interest' drop down form that would let people select this as an option. We haven't had this as an option in the past since it's not really related to the function of the form as a way for people to express how they want to contribute to Mozilla, but it's not realistic to expect people not to use the form for support questions. James, I'd like to use this as a way to figure out how to make changes to the new page on Bedrock, but I may have questions along the way. Thanks in advance for your guidance and help.
I just submitted two pull requests on github for this bug: https://github.com/davidwboswell/bedrock/commit/03e45e4f56ed04de3f6d7b6a2a7e1a7fdfe98208 https://github.com/davidwboswell/bedrock/commit/1981a7d16d23cb680f821cec5dda1cdade06810b I saw how to edit an existing file but not how to add a new one through github, so I'll attach the content for the emails/issue.txt file to this bug. I also have no idea if this is the right workflow or not, so feel free to tell me how to do things a better way.
Assigning to James since I'm not sure what the next steps are. Please assign back to me if there are other steps I can take here. Thanks.
Assignee: nobody → jlong
Unassigning bugs from James that are not migration-related bedrock platform bugs. Let me know if you have any questions.
Assignee: jlong → nobody
This should be on www-dev now, can you check there and test?
(In reply to Fred Wenzel [:wenzel] from comment #4) > Unassigning bugs from James that are not migration-related bedrock platform > bugs. Let me know if you have any questions. Heh, I was already in the middle of doing it :)
Assignee: nobody → jlong
(In reply to James Long (:jlongster) from comment #6) > This should be on www-dev now, can you check there and test? Thanks for moving it over. The new drop down item is there, but the order wasn't what I was expecting. The order of the bottom of the drop down in the following commit is Other I have a suggestion for Firefox I need help with a Firefox issue https://github.com/mozilla/bedrock/commit/1981a7d16d23cb680f821cec5dda1cdade06810b and the order on the page is I have a suggestion for Firefox I need help with a Firefox issue Other How can I make the form reflect the order in the commit? Did I make the change in the wrong way or is the order being influenced by something else? CSS maybe? Also, I wasn't able to test to see if the new item correctly sent out the new auto-response text since the dev page has a partially implemented CAPTCHA that's not letting me submit the form.
In this list of changes: https://github.com/mozilla/bedrock/commit/0aa765277fe4d034b911a8005a413c5cb9e45ce8 I'm also not seeing the following changes that would set up the auto-response: https://github.com/davidwboswell/bedrock/commit/03e45e4f56ed04de3f6d7b6a2a7e1a7fdfe98208 I may just not be understanding where to track status in Github yet.
(In reply to James Long (:jlongster) from comment #7) > (In reply to Fred Wenzel [:wenzel] from comment #4) > > Unassigning bugs from James that are not migration-related bedrock platform > > bugs. Let me know if you have any questions. > > Heh, I was already in the middle of doing it :) Thanks, James! (blame the mass-bug-change form ;))
(In reply to David Boswell from comment #9) > In this list of changes: > > https://github.com/mozilla/bedrock/commit/ > 0aa765277fe4d034b911a8005a413c5cb9e45ce8 > > I'm also not seeing the following changes that would set up the > auto-response: > > https://github.com/davidwboswell/bedrock/commit/ > 03e45e4f56ed04de3f6d7b6a2a7e1a7fdfe98208 > > I may just not be understanding where to track status in Github yet. Those changes were merged in with your patch. I had to correct a syntax error in the list of form choices, so that's why that shows up. I just fixed the ordering and will try to fix the captcha so you can test it next.
I see the updated order in the form and that looks good. I'll be around and can test the auto-response whenever that's ready to try out.
I'm waiting on IT to add the recaptcha keys to the config and then the site should be working.
David, The captcha is up and running now, so please test and your changes in this bug there: http://www-dev.allizom.org/en-US/contribute/
This works fine on stage. Do we need to wait for a site release or can we push this now? The form got spammed again last night, so would be good to get the captcha up.
We will roll it into the next release, which is tomorrow, if that's ok.
Sounds great, thanks.
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
I see this on the live site and the auto-response was sent correctly when I tested.
Status: RESOLVED → VERIFIED
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: