We've been working on it for a couple months now, and we're excited to say that Provisional Progress has arrived! What is Provisional Progress, you ask? It's a setting you can turn on (it's off by default) that lets any member of your troop enter "provisional" achievement data. It's "provisional" because a leader with the Manage Achievements Privilege (MAP) must confirm the data for it to show up in places like the shopping cart or the user's profile.
See this community post for all the details and pictures. :)
We've also released some bugfixes:
We've updated several things recently:
• Fix a bug where users paying for event tickets with PayPal couldn’t record guests
• Separate retired and active Merit Badges in forms
• For AHG users, sometimes when importing data from AHGconnect an error would occur about unnamed trainings. This has been fixed.
The provisional progress update is almost done! We're super excited to release it soon! :DPermalink
We wanted to make our users aware that TroopTrack emails being sent to AT&T or any of its affiliated companies (BellSouth, for example) are being blocked by AT&T.
We have already reached out to them, but it will take some time to hear back, have the request to remove the block approved, and then actually have the block removed. If you use an AT&T, BellSouth, or other affiliated email address for TroopTrack, please reach out to AT&T to request that this block be removed so that you can continue to receive your emails. Hopefully, this will help expedite the approval process. You can contact them at firstname.lastname@example.org.
In the meantime, we appreciate your patience as we work to get this resolved as quickly as possible.Permalink
We wanted to let everyone know that we will be out of the office all day on Friday, June 29, as we will be attending Spencer's brother's wedding out of town. We will resume our normal hours on Monday. :)Permalink
Two weeks ago, we posted on the Community that we were going to be fixing the requirements for the AHG awards: https://community.trooptrack.com/t/fixing-the-ahg-awards/7441. This is to address two issues. First, when sub-requirements for one level required girls to complete multiple other requirements (ex: Explorers need to complete 7-9, and requirement 7 is to complete requirements 1-2), we placed those sub-sub-requirements appropriately with the sub-requirement that they belonged to. Secondly, a user commented on the previous post and let us know that (per AHG National), requirements for another level cannot be repeated as electives for another level, except where specified (ex: Tenderhearts need to complete 1-3, so Explorers can only use 1-2 to fulfill requirement 9, while Pioneers and Patriots can't use any of them as electives).
Due to the way the system is set up, this will mean creating new versions of the awards and "retiring" the previous versions. This will allow the existing versions to continue functioning properly (so that we don't break anyone's achievement pages), while also making sure that the updated/corrected version is what people are adding/using from this point forward.
Before performing a massive overhaul of all of the badges, we wanted to let you know that we are testing it on one badge only first (across all levels). We have chosen the Photography badge to test. The new award will show up with two asterisks after the name, like this: Photography (T)**. We have retired the previous versions.
We are posting this on the Community, the Facebook page, and the Product Updates of the website in order to obtain feedback on the implementation of this with just the Photography badge, before we started overhauling all of the awards. If you notice any problems or have any additional feedback to share regarding this issue, please reply directly to this post (on Facebook and the Community) or send an email to me at email@example.com. :)Permalink
You can now RSVP straight from the event invitation emails! This has been one of the most-requested features for a while, and we’re excited that it’s finally arrived.
From now on, each event invitation email will include one link to view the event and several other links to RSVP to the event. And coolest of all: none of those links require you to login! Even users without a username and password can RSVP to events straight from the email.
The links use a special token that only gives access to viewing the event and RSVP’ing to the event. The token doesn’t give access to other actions like editing the event or viewing user information. To do anything besides view the event and RSVP you'll need to log in.
When you click on one of the RSVP links we record your RSVP choice and show you the event details. This way you can confirm that the RSVP was saved. Also, if you need to RSVP for several other people you can do it all on one page.
Also, we updated the RSVP box. You can now select the RSVP option right on the event details page. It’s a lot easier to RSVP for multiple people this way!
However, most of these shiny new features don’t apply to events with fees. For events with fees, you can still view the event details without logging in, but in order to RSVP and pay the fee you’ll need to log in. A future update may make it possible to pay event fees without logging in.
See the Community post for screenshots: RSVP from the Event Invitation! :DPermalink
We apologize in advance for any difficulty you may have in reaching us this week (April 2 through April 6). Spencer and I (Kelsie) are closing on a house this afternoon and packing/moving, so we will be out of the office for part of today and all of Friday. We are doing our best to maintain normal hours the rest of the time, but may not always be able to do so. We will be back to normal next week. Thank you for your patience! :)Permalink
We updated some more stuff! :)
On Friday, 2 March 2018, we made some changes to the site in order to improve security that broke the ability to access documents and pictures uploaded to our site. We worked on this over the weekend, and Dave fixed the problem yesterday morning. Troop Documents and Photos are fully operational again. We apologize for this issue, and we're grateful for the kind heads-up our user gave us in the first place. You guys rock!Permalink