Kentico Page Wizard Manager配置相关技术问题求助

Alright, let's break down the common issues you might be facing with the Page Wizard Manager in your Portal Engine setup— I’ve worked through similar scenarios before, so here are targeted troubleshooting steps and fixes tailored to your page hierarchy (A with B-E as children, F as a sibling to A):

1. Wizard Fails to Load Child Pages (B-E) Under Parent Page A #

If the wizard isn’t pulling in B-E as part of the flow, check these first:

• Verify Page Wizard Manager configuration: Double-check the Web part’s Page path property to ensure it points directly to page A (e.g., /A or the correct relative path). Also confirm the Include subpages checkbox is ticked— this is required to load nested pages like B-E.
• Validate placeholder name consistency: Your parent page A has a Page Placeholder Web part, so make sure its Placeholder name matches exactly (case-sensitive) with the placeholder used in the page templates for B-E. If the parent uses mainContent, every child page’s template must target that same placeholder name for content to render.
• Check user permissions: Ensure the test user you’re using has at least Read and Edit permissions for page A and all its child pages (B-E). Missing permissions will block the wizard from loading the page list.

2. Wizard Won’t Navigate to Sibling Page F After Completing E #

Since F is a sibling to A (not a child), the wizard won’t auto-detect it as a "next" page by default. Fix this with:

• Configure custom page sequence: In the Page Wizard Manager’s properties, switch to a custom navigation mode. Use the Page sequence setting to manually define the flow: add A, B, C, D, E, then F in order, specifying each page’s path.
• Confirm page type compatibility: Make sure page F uses a page type that’s allowed in the wizard’s configuration. Check the Allowed page types property to ensure F’s type is included (or set it to All page types for testing).

3. Child Page Content Doesn’t Render in Parent’s Placeholder #

If the wizard loads the page list but content from B-E doesn’t show up in A’s placeholder:

• Check parent placeholder settings: Go to the Page Placeholder Web part on page A and confirm the Render nested content option is enabled. This is critical for pulling in content from child pages.
• Clear Kentico cache: Portal Engine can hold onto stale configuration cache. Head to System > Cache and clear both Page cache and Web part cache, then refresh your test page.
• Validate child page templates: Since you’ve set Page Wizard Manager as the only content Web part on these pages, ensure each child page’s template has the wizard configured to target the correct placeholder (matching the parent’s placeholder name).

4. Wizard UI is Broken (Missing Buttons, Layout Issues) #

If the wizard’s interface isn’t displaying correctly:

• Check CSS conflicts: Ensure your page templates aren’t overriding Kentico’s built-in wizard styles. The Page Wizard Manager relies on classes like cms-wizard and cms-wizard-step— inspect the page with browser dev tools to see if custom CSS is hiding or breaking these elements.
• Verify display mode: In the Page Wizard Manager’s properties, confirm the Display mode is set to Full (or an interactive mode, not Hidden or Read-only).

内容的提问来源于stack exchange，提问作者BU0