esmith818 / f3isotope Goto Github PK

Given ample time to ensure the local site calendar offers mirrored functionality, remove Google's "daily planner" from main page.

Optionally, move site calendar to main page rather than having a link in primary menu bar.

Rather than relying on users to tweet counts of daily workouts, automate this data from pax attendance in back blasts. Create a View to display this information to users on the site based on roles. Research option to send automate tweeting daily counts from all workouts.

Some pax would like users to have more complete profiles (similar to the Who's Who section of the newsletter) so that peers could learn more about the men they work out with in the gloom.

iOS uses a custom "scroll wheel" UI for displaying options in a multi select field. The Chosen module intentionally unsets the "_none" option which seems to cause a problem on iOS devices -- as soon as the field is selected, the first value in the list is chosen by default. To remove, user must re-enter field and manually deselect the first option.

At least 3 users have mentioned this bug in the UI. All are iOS users. I was able to recreate the bug on my work laptop using and XCode iPhone 5S simulator. However I was later UNable to produce the problem on my personal laptop doing the same (selecting field did NOT auto-select an option; user had to manually select value or field would --correctly-- remain without a value).

Will overwrite files and DB on server with my local repo to see if some unknown setting "fixes" the issue. Otherwise the possible solution is to remove line #207 from chosen.module to reset the _none option. This appears to work although the presentation is not as clean on other operating systems (_none is unnecessary in these cases). Note that line #207 (above) was added as a recent patch to the Chosen module per this DO ticket: https://www.drupal.org/node/2117827

Can site recognize if a week has passed without a back blast posted for a particular workout? Send email notification to listed Q/master Q reminding them that a back blast needs to be posted.

User wants to be able to offer sign-ups for individuals for various events (e.g. mud run, BRR, pax roast). Ideally would include option to offer PayPal payments using a custom F3/Isotope account.

My preliminary research suggests using the following modules:
https://www.drupal.org/project/registration
https://www.drupal.org/project/commerce_registration
https://www.drupal.org/project/commerce
https://www.drupal.org/project/commerce_paypal

This issue seems complicated enough to require testing in a local environment before adding changes to live site.

Quantify user attendance at workouts for various challenges:

1. 250 Club ~ post at 250 workouts in a year.
2. Spread the Love ~ post at different AOs over course of year.

Both of these "challenges" seem to be trackable via site data assuming back blasts are posted for all workout attended and user is correctly tagged in each of them. Seeing this data "at-a-glance" might be helpful to those trying to reach them.

Only an admin can change a user profile name (F3 nickname) but when this happens (e.g. add capitalization, space, correct spelling) the MailChimp module throws an error. I think this is a false positive since refreshing screen clears errors leaving changes intact. Not sure MailChimp is directly affected. This needs to be confirmed and corrected if possible.

Add option to navigate to specific letter when scanning pax names in CoT. Easiest solution that comes to mind is a set of hyperlinks as top of page for each alpha-numeric character.

(This functionality could also be extended to lexicon.)

Error encountered if a new user registers during or just after cache(s) cleared. Error fixed in a dev branch; waiting on fix to update on stable branch (https://www.drupal.org/node/2566307).

SoCal mentioned error on 1/5/16.

Freepass mentioned issue with how line breaks are handled in preblasts. CSS likely the root cause, especially where classes/IDs are common among multiple content types.

Originally had Comment Subscribe module installed which allowed authenticated users to check a box to subscribe to comments on back blasts and pre blasts. That module had a security flaw and the dev was unwilling to fix so the module had to be removed from site. Users miss the subscription functionality.