detect if teams are enabled

I haven't tested this, but I think S400 using 'team_form_team_optname'. Let us know if this is correct.

Dustin Rambo:

Sir, you are a true gentelman.

 

And your idea worked! May I ask what you referenced for the EDP "team_form_te3am_optname"?

I did recall that there was an S-Tag for getting TR settings, either from a post here in the community or from my 10 million trips through the S-Tag docs. (https://secure2.convio.net/customer/luminate_online/v10/s-tags/Help/S-Tags_Left.htm)

From there all we need is the EDP name, which you can find from checking out the name or id on the checkbox field in the TR set-up. Here's the setting we want to check.

The name is in the html code, so right click and view source. Then find the field. (Or use the awesome FireBug extension or something similar to 'Inspect this Element'.)

<input type="checkbox" onclick="fire_obs_comp_event('team_form_team_opt', this);" checked="checked" id="team_form_team_optname" name="team_form_team_optname">

I'm pretty sure that is a trick I read here in the community.

\\ Yay, community!

Dustin Rambo:

That's a great trick, thanks a million!

Howdy - 

What am I missing here? I am trying this config:

[[S400:1040:team_form_team_optname]]

teams are enabled, but nothing is returned by the STag

Thanks!

Dan

Brian Mucha:

Yea, I didn't test this when I posted and now that I'm re-reading I don't think this would work. Not sure about Dustin's success.

 

From the docs:

 

Note: EDP is a TeamRaiser Event Data Parameter defined for a specific TeamRaiser and overriding the site options.

 

Looks like this will only return EDPs that override the Teamraiser SDPs, which you access via Set-Up > Site Options.

 

The docs show this example:

 

[[S400:0:F2F_CUSTOM_SPONSOR_URL]]

 

That is an SDP field name, not the EDP. (At least it is not the input name of the field using the view source trick.)

 

Looks like FORM_TEAM is not an SDP, but just a plain old Teamraiser setting.

 

So for instance, F2F_ENABLE_ACHIEVEMENT_BADGES is an SDP in Site Options. But you can also set that on

3. Select Event Options > a. Define Fundraising Options > 14. Fundraising Milestones.

 

So [[S400:1234:F2F_ENABLE_ACHIEVEMENT_BADGES ]] will tell you how that SDP is overridden in fr_id 1234.

 

Weird tag. Why not just have this do what I initially thought it did? It would be way more useful!

 

Edit:

 

Better docs from the API version of this S-Tag.

 

http://open.convio.com/api/#teamraiser_api.getEventDataParameter_method.html

 

Valid values for edp_name are:

• F2F_ACCEPT_OFFLINE_SERVER_API
• F2F_ACCEPT_OFFLINE
• F2F_ADMIN_NEWS_FEEDS_ENABLED
• F2F_ALLOW_EVENT_MANAGEMENT
• F2F_ALLOW_OFFLINE_PART_TYPES
• F2F_ALLOW_SHOP_FOR_PREMIUMS
• F2F_BLUEPRINT_LOCKING_ENABLED
• F2F_BLUEPRINT_SHOW_ALL_DEBUG_MODE
• F2F_CENTER_TAF_BOUNCE_NOTIFICATION_ENABLED
• F2F_CENTER_TAF_PERSONALIZED_SALUTATION_ENABLED
• F2F_CHART_DATA_API_DAYS_ALLOWED
• F2F_COMPANY_FUNDRAISING_GOALS
• F2F_COMPONENT_STYLING_ENABLED
• F2F_CROSS_JVM_CACHE_ENABLED
• F2F_CUSTOMIZED_URL_IS_PERMANENT
• F2F_DEFAULT_STATIONERY
• F2F_DISABLE_CLASSIC_PART_CENTER
• F2F_DISABLE_SELF_DONATION_RECEIPTS
• F2F_DISPLAY_LIST_DONATE_BUTTON
• F2F_DISPLAY_LIST_ECOMMERCE_BUTTON
• F2F_DONOR_HONOR_ROLL_BY_ALPHA
• F2F_ECOMMERCE_ALLOW_ENABLED
• F2F_ECOMMERCE_CREDIT_PARTICIPANT
• F2F_ECOMMERCE_CREDIT_TEAM
• F2F_ECOMMERCE_ENABLED
• F2F_ECOMMERCE_PRODUCT_ID
• F2F_ECOMMERCE_STORE_ID
• F2F_EM_CONTACT_SEARCH_MAX_RESULTS
• F2F_EM_SHOW_UNCONFIRMED_GIFTS_IN_HISTORY
• F2F_ENABLE_ACHIEVEMENT_BADGES
• F2F_ENFORCE_UNIQUE_EMAIL
• F2F_ENFORCE_UNIQUE_NAME_AND_EMAIL
• F2F_EVENT_CREATION_EMAIL
• F2F_FB_CONNECT_PUBLISH_FEED_IMG_SRC
• F2F_FB_CONNECT_PUBLISH_FEED_IMG_URL
• F2F_HTML_SUGGESTED_MESSAGES_ALLOW_IMAGES
• F2F_HTML_SUGGESTED_MESSAGES_ALLOW_LINKS
• F2F_HTML_SUGGESTED_MESSAGES_ENABLED
• F2F_INCLUDE_UNCONFIRMED
• F2F_MILESTONES_ENABLED
• F2F_MILESTONES_NUM_ALLOWED
• F2F_MULTIPLE_CAPTAINS_ENABLED
• F2F_OFFLINE_GIFT_GIFT_AID_DESC
• F2F_OFFLINE_GIFT_GIFT_AID
• F2F_OFFLINE_GIFT_NOTIFICATION_DISABLED
• F2F_OFFLINE_PMT_TYPES
• F2F_OFFLINE_TEAM_GIFTS_ALLOW_TYPE
• F2F_PART_CENTER_COOKIE_MAX_AGE
• F2F_PART_CENTER_EMAIL_DAYS
• F2F_PART_CENTER_INCLUDE_SECOND_PHOTO
• F2F_PART_CENTER_LOGOUT_REDIRECT
• F2F_PART_CENTER_MIN_AB_SIZE
• F2F_PART_CENTER_OVERRIDE_ABOOK_URL
• F2F_PART_CENTER_OVERRIDE_EMAIL_URL
• F2F_PART_CENTER_OVERRIDE_GIFT_URL
• F2F_PART_CENTER_OVERRIDE_PEDITOR_URL
• F2F_PART_CENTER_OVERRIDE_PROGRESS_URL
• F2F_PART_CENTER_OVERRIDE_SETTINGS
• F2F_PART_CENTER_OVERRIDE_TENTING_URL
• F2F_PART_CENTER_OVERRIDE_TPROGRESS_URL
• F2F_PART_CENTER_OVERRIDE_URL
• F2F_PART_CENTER_PERSONAL_PAGE_DAYS
• F2F_PART_CENTER_PROGRESS_IMAGE_ID
• F2F_PART_CENTER_SHARE_ACTION
• F2F_PART_CENTER_SHARE_ID
• F2F_PART_CENTER_SHARE_MESSAGE
• F2F_PART_CENTER_SHARE_TITLE
• F2F_PART_CENTER_UPDATE_GOAL_PERCENT
• F2F_PART_CENTER_USE_YUI_STORAGE
• F2F_PART_EDIT_REG_RESPONSES
• F2F_PARTICIPANT_ALLOW_CARD_PROCESS
• F2F_PARTICIPANT_EMAILS_TRACKABLE
• F2F_PERSONAL_BLOGS_ENABLED
• F2F_PERSONAL_PRECALCULATION_ENABLED
• F2F_PRECALCULATION_ENABLED
• F2F_PRECALCULATION_INTERVAL
• F2F_PRECALCULATION_NAME_UPDATE_ENABLED
• F2F_PRECALCULATION_NAME_UPDATE_INTERVAL
• F2F_PRECALCULATION_NAME_UPDATE_TIME
• F2F_PUBLIC_EVENT_TYPES_ENABLED
• F2F_REASSIGN_RACE_NUMBER
• F2F_RECENT_ACTIVITY_SIZE
• F2F_RECRUITING_GOALS
• F2F_REG_ANONYMOUS_CHECKBOX
• F2F_REG_INTERACTION_SHOW_SNAPSHOT
• F2F_REG_PUBLIC_CHECKBOX
• F2F_RESTRICT_STATIONERY_TO_EVENT
• F2F_RETURNING_TEAMS_AB_VISIBILITY
• F2F_RETURNING_TEAMS_COPY_PREVIOUS_COMPANY
• F2F_RETURNING_TEAMS_COPY_PREVIOUS_DIVISION
• F2F_RETURNING_TEAMS_COPY_PREVIOUS_GOAL
• F2F_RETURNING_TEAMS_ENABLED
• F2F_RETURNING_TEAMS_KEEP_PREVIOUS_ROLES
• F2F_RETURNING_TEAMS_REFORMER
• F2F_RETURNING_TEAMS_USE_PREVIOUS_TEAM_PAGE
• F2F_SCREENNAME_MAX_LENGTH
• F2F_SHOW_GIFT_CATEGORIES_FOR_PARTICIPANT_GIFTS
• F2F_STATUS_INCLUDE_SECONDARY_REG_FEES
• F2F_STATUS_THERMOMETER_PROGRESS_IMAGE
• F2F_TEAM_AB_VISIBILITY
• F2F_TEAM_MILESTONES_ENABLED
• F2F_TEAM_MILESTONES_NUM_ALLOWED
• F2F_TEAM_ROSTER_MAX_INCLUDE_AMOUNT_SIZE
• F2F_TEAMRAISER_LIST_COMPONENT_MAX_SIZE
• F2F_UPDATE_CONSTITUENT_FROM_SECONDARY_REGISTRANT
• F2F_UPLOAD_REG_ALLOW_TRANSACTIONS
• F2F_USER_CAN_CHOOSE_LAYOUT
• F2F_USER_CAN_CHOOSE_STATUS_IND
• F2F_USER_CAN_CHOOSE_STYLE
• F2F_USER_RICH_TEXT_PAGES_ALLOW_IMAGES
• F2F_USER_RICH_TEXT_PAGES_ALLOW_LINKS
• F2F_USER_RICH_TEXT_PAGES_ENABLED

 

Back to the original issue.

We can get the Teams Enabled setting using the API.

http://open.convio.com/api/#teamraiser_api.getTeamraiserConfig_method.html

getTeamraiserConfigResponse.teamraiserConfig.teamsAllowed

Check out Noah's LuminateExtend.js on GitHub. Makes the API a breeze.

Brian Mucha:

Or here's another idea.

 

What about using [[S42:fr_ID:num-teams]] and make sure you have at least one team in your team-enabled TeamRaisers?

 

Not ideal, but it could work.

Thanks for the information Brian!  I will sift through this when I have a little more time. 

Dustin - Did you get S400 to work for this?  Would you mind shareing your config?

Thanks guys,

DK

Dustin Rambo:

Sorry I'm late to the game, but yes I did get it working. Our scenario is that we have 1 blueprint governing several programs and hundreds of events. We had to have a way to dynamically set the registration path. In this particular context we have two registration paths, based on whether or not the event has teams enabled. Hope this helps!

 

[[?xx::x[[E400:[[S80:trID]]:team_form_team_optname]]x::

<!-- teams true -->

<a id="btn-register" class="entry-text-link secondary-step step-button btn-register" href="//[[S29OMAIN]][[S29ATH]]TR/Events/Events?pg=informational&fr_id=[[S334:fr_id]]&type=fr_informational&sid=1220" title="teams">Register</a>

::

<!-- teams false -->

<a id="btn-register" class="entry-text-link secondary-step step-button btn-register" href="//[[S29OMAIN]][[S29ATH]]TRR/Events/Events?pg=tfind&fr_id=[[S80:trID]]&fr_tm_opt=none" title="no teams">Register</a>

]]

Thanks for the reply, Dustin.  

I still can't seem to make this work.  Regardless of the team option setting, the S400 tag is always returning "nothing" so your conditional is always rendering as "true".  Out of curiosity, why did you decide to test for "nothing" instead of some other response?  

Thanks again,

DK

Kent Gilliam:

Thanks for sharing this solution!!!!!

Yes indeed - thanks!