Typically, when the payment page shows old information, for a different event or previous event, this is due to the page or part being copied, instead of creating a new page and part. A new page and part will need to be created, and then run the template updater.
If you recently (the same day) created the donation form or event registration form
When a page or part is recently created, it's possible the secure payment template updater has not been run yet. This will need to be run in order to dynamically pull the design of the event page onto the secure payment page.
Run the Secure Payment Template Updates
Run the Secure Payment Template Updates
If after creating a new page, new part and running the updater, the default BBSP page displays, as shown below
This typically indicates there is a design element preventing the correct design from being displayed properly.
Please refer to our BBSP design guide. You may need to consult a qualified designer or web developer.
Please refer to our BBSP design guide. You may need to consult a qualified designer or web developer.
The incorrect or old template shows on the payment page on a mobile device ONLY
We may see this issue if the template does not have a set layout for mobile devices. To resolve this issue, we can set the layout for mobile devices.
Verify the Targeting & Security of the part, page, template and style sheet is set to View Everyone
Confirm the Primary Site URL
Confirm the Primary Site URL
If NetCommunity is on an older version of the product, you may need to upgrade in order to allow the secure payment templates to work properly. Previous items which conflicted with the BBSP templates:
- Page name cannot have single quote or apostrophe
- Page name cannot have double quote
- Page name cannot have a colon ":"
- Page name cannot contain an "&" symbol
- Page name cannot have a "-"
