Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve last few Infield issues #25

Closed
4 of 5 tasks
CynthiaParr-USDA opened this issue Jun 2, 2015 · 7 comments
Closed
4 of 5 tasks

Resolve last few Infield issues #25

CynthiaParr-USDA opened this issue Jun 2, 2015 · 7 comments

Comments

@CynthiaParr-USDA
Copy link
Member

  • new user registration (talked to cip)
  • last of user payments via PayPal (charged but didn’t report back)
  • MailChimp plugin supposedly has a manual trigger to push all new users into mailchimp, deletes dead address from Typo3 registry
  • figure out how to do news on the new site
  • enable the lost password functions
@CynthiaParr-USDA
Copy link
Member Author

Stan talked to Catherine about the first three of these. There's a news extension but we don't see how it works yet.

@CynthiaParr-USDA
Copy link
Member Author

Stan, we need an update on this ticket...

@CynthiaParr-USDA
Copy link
Member Author

stan says payments should be working. I will test.

@sblum
Copy link
Contributor

sblum commented Jun 25, 2015

  • Individual membership payments work and are now showing on the membership reporting page. I need a volunteer to test the payment an institutional membership through PayPal (with a credit card).
  • Email from the server is now working. Dependent functions (now working) include: forgot password; newly registered user can confirm email and become regular_user. (We are not requiring that newly registered users get reviewed by a secretariat member; they now become regular_users as soon as they confirm their email address.
  • News items can be added by backend admins using a form that exists there. (To keep costs down, I deferred fixing the form we had that can be accessed by regular users to submit news items. It wasn't used that often. I propose instead that all news items get submitted to and entered by the secretariat.)

Remaining steps before cut-over:

  • Review / revise this list of steps
  • create list of tests to check successful operation (critical functions)
  • Confirm DNS control with Cip (GBIF admins), reduce TTL in advance of switch
  • Freeze edits on conference page; migrate conference content
  • Execute switch ( www --> tdwgpg; tdwgng --> www )

@pmergen
Copy link

pmergen commented Jun 25, 2015

Hi
For the institution would suggest GBIF. Andrea hahn had recently contacted us.
Pat

@CynthiaParr-USDA
Copy link
Member Author

Chuck said that he tested the institutional payment.

@CynthiaParr-USDA
Copy link
Member Author

The only thing here supposedly undone is the MailChimp push. If that is still an issue, please create a new ticket.

@sblum sblum removed their assignment Jan 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants