Your portal does not check the page and menu editing tools each time a visitor arrives. It uses a saved index of your site’s pages and menus called the site map. When that index no longer matches what you have published, visitors may see missing pages or broken navigation. Rebuilding the site map refreshes that index from your records.
Prerequisites
- You need permission to open Setup and run maintenance tasks.
Rebuild the Current Site's Map
- Go to Setup › Maintenance.
- Select Rebuild Current Site Map.
- Confirm the warning dialog.
Result
A toast says "Site rebuild initiated." This means Rhythm accepted your request, not that the rebuild has finished. The screen does not show whether the rebuild succeeded, so check your live site directly when you expect the rebuild to be complete. The site can still show an error for a short time after a rebuild finishes. If you check right away and still see a problem, wait a few minutes and check again before treating it as a persistent issue.
This rebuilds the map for the site you are working on when you select the button. If you need to switch sites first, see Choose the Site You Are Working On.
Warning
A rebuild can remove live pages. The new map keeps a page or menu only when it is unpublished or has not changed since it was last published. If you edited a published page after publishing it, even as an unpublished draft, the rebuild drops it from the map. Visitors cannot reach that page again until you publish it.
You cannot use this option to rebuild a site that has more menus than fit on one page of results. Most sites will not run into this, but keep it in mind if your site has an unusually large number of menus.
Starting a Second Rebuild
If you request another rebuild for the same site while one is still running, Rhythm does not queue the second request. The new request replaces the first one, so only the latest request publishes a new map. In rare cases, rebuilding one site can replace another site’s running rebuild when both requests use the same run name. This matters only when you rebuild more than one site in very quick succession.
When a Rebuild Happens Automatically
When you install a feature on a site, Rhythm rebuilds that site’s map automatically after the installation finishes. A brand-new site has no site map until you build one from this screen, install a feature, or create the site from an existing one. If a new site shows no pages right after you create it, it usually just needs its first rebuild.
Tip
Installing a feature can still add pages you did not expect. You may see older Review Center pages, such as /abstractReviews/ or /reviews/, installed and added to an event’s menu even where your account has otherwise moved to Reviews Overview. Installed features cannot be uninstalled, so if you do not want the extra page, delete it from Pages and remove it from the menu instead of trying to install the feature again.
If Recent Changes Are Not Showing
If you published a page or menu change and it still does not appear on the live site, rebuild the current site map. Go to Setup › Maintenance, then select Rebuild Current Site Map to refresh the site so your recent changes appear. For an event microsite whose pages are not rendering correctly, try both maintenance actions together: rebuild the current site map for the pages and menus, then rebuild the asset map for the templates and components they depend on.
A very large microsite page can fail to publish outright. If a page will not publish and the content itself looks fine, rebuilding the current site map can let the publish complete.
Tip
This screen also includes Rebuild Asset Map, which repairs a separate index for your templates, components, stylesheets, scripts, and files. It does not rebuild your pages and menus. See Working Copies, Published Versions, and the Asset Map Explained for what that index does.
Warning
Publishing a page can show a message telling you to run Maintenance › Rebuild Current Site Map before the page is available in the portal. In some cases, this message has appeared even after the site map was already rebuilt, and rebuilding again did not clear it, even though the page had published. A similar publish message has pointed to Rebuild Asset Map when rebuilding the current site map was actually the step that helped. If a rebuild does not clear the message, check your live site directly before assuming the page did not publish, and contact Support if the message does not go away.
Rebuilding the current site map and the asset map refreshes their saved indexes, but that alone does not guarantee every kind of change is picked up. If you update your account’s main template and the live portal still shows the old design after rebuilding both maps, you may need to delete the affected pages and reinstall the feature that created them so they are rebuilt from the new template.
If an event microsite was cloned from another event and still shows the first event’s content, resaving the portal site and republishing all of its pages has cleared up the mismatch in cases like this.
If a public microsite is active, has pages, and already has a rebuilt site map but still shows the generic portal error page, running these maintenance tasks to refresh the microsite has restored it in cases like this before escalating further.
If a welcome or landing page loads but appears blank, you may be able to restore it by making a small edit to that page and then reinstalling the feature for it, rather than relying on a site map rebuild alone.
Recreating or republishing individual pages for an event feature, such as Schedule of Events or a speaker directory, may not restore the links from a list page to its detail pages. If detail links stop working, delete all of that feature’s pages and reinstall the whole feature to recreate the routes between them.
Warning
Deleting and reinstalling a live event’s integrated portal pages is safe only when no one is currently registering for the event. Schedule this kind of repair for a quiet window, or confirm registration is paused first.
Rebuilding the asset map and site map together can also be worth trying if members report trouble signing in or reaching their portal pages, even outside a publishing problem.