Scope
This article covers the public, read-only Rates & Deadlines page, also called the registration pricing page. The page is designed to show member and non-member pricing whether or not the visitor is signed in.
If this page does not load, that is different from a page on your association’s site that intentionally requires sign-in. This article does not cover the registration form itself.
Registration Settings Have Not Been Completed for the Event
Most likely cause. The Rates & Deadlines page uses the event’s registration settings for prices, deadlines, and currency. If those settings have never been saved for the event, Rhythm cannot build the page because the prices do not have a currency, so every visitor sees “Unable to load rates.”
Check. Open the event’s registration settings in the Console and confirm they have been saved at least once.
Fix. Complete and save the event’s registration settings. After those settings exist, the page loads correctly.
The Registration Settings Point to a Business Unit That No Longer Exists
Likely cause. The registration settings include a business unit, which provides the event’s default currency. If that business unit was deleted, or the settings point to the wrong business unit, the page cannot determine a currency and fails to load for every visitor, just as it does when registration settings are missing.
Check. Open the event’s registration settings and confirm the selected business unit still exists and is the one you want for this event.
Fix. Correct the business unit on the event’s registration settings, or restore the missing one, then reload the page.
The Page Fails Only for Visitors Using One Particular Currency
Less common, and easy to miss because most visitors are unaffected. Some packages let a visitor using a foreign currency buy at a converted price instead of the package’s own base currency. If Rhythm needs to convert a package price into the visitor’s selected currency and no conversion rate exists between the two currencies, the page fails to load prices for that visitor. Visitors browsing in the business unit’s base currency still see the page normally.
This is different from a package not appearing in a foreign currency. A package can block purchases in any currency other than its own, and Rhythm leaves that package out of the table for visitors using other currencies without showing an error. A missing conversion rate stops the whole page from loading for anyone using that currency.
Rhythm guesses a visitor’s currency only the first time they log in, then remembers that choice for later visits. It does not automatically switch again just because the visitor is now browsing from a different location. Keep this in mind when you ask which currency a visitor was using, because it may not match where they are browsing from today.
Check. Ask which currency the affected visitor was browsing in, then compare it with the base currency of the business unit used in the registration settings. Confirm whether a currency conversion rate exists between the two.
Fix. Add or correct the currency conversion rate between the visitor’s currency and the business unit’s base currency. Once the rate exists, the page loads normally for visitors using that currency.
The Page Gets Stuck Loading Instead of Showing an Error
A separate, since-resolved issue affected only events hosted through the portal-integrated experience, not standalone microsites. The page could stay on a loading message indefinitely instead of showing prices or an error, including on event landing pages and schedule pages that use a registration pricing widget. Resaving the portal page did not fix it. One known trigger was a rate-schedule request sent without the visitor’s currency.
If a portal-integrated pricing or schedule page is still stuck loading, check the causes above first because this issue has been addressed. If the page still will not load, contact Support with the details below.
When to Contact Support
Contact Rhythm Support if the registration settings, business unit, and currency conversion rates all look correct and the page still will not load. Include:
- the event and, if you know it, which currency the affected visitor was using;
- whether the page fails for every visitor or only some visitors;
- the event’s business unit and its base currency;
- any error message shown, including the browser’s console error if you can capture it.