feat: set a CMS menu link to open in new tab - via data

[wesleyboar]

Overview

Let CMS admin set a nav menu link's target attribute per page.

• Controlled by CMS admin; no dev required.
• Stored in the database.

Previously, only external links got target="_blank" (via custom Core-CMS JavaScript).

Related

• fixes WP-1230
• client-side alternative: WP-1290
• alternative: feat(nav): set a CMS menu link to open in new tab - via setting #1150

Changes

• added PageNavOptions page extension (model + migration)
• added NewTabModifier for node.attr['target']
  ^{adds data for template to read}
• added PageNavOptionsAdmin and PageNavOptionsToolbar
  ^{exposes field via CMS toolbar Page menu → Page Options → Nav Options}
• updated target_blank tag
• updated cms_menu.html

Testing

1. make start
2. Navigate to any internal page in edit mode.
3. Change nav target:
   1. Open Page menu in CMS toolbar → Page Options → Nav Options
   2. Set Target to "Open in new window"
   3. Save.
4. Verify the nav link has target="_blank".
5. Verify external redirect links still open in a new tab (existing behavior).

UI

Toolbar.Option.mov

Admin.URL.mov

Old Solution (from 196496c)

how.you.could.change.whether.page.opens.in.new.window.mov

/admin/ UI

Notes

The field lives in the CMS toolbar's Page menu under Page Options → Nav Options, not in Page settings. That is the only officially supported injection point for page extensions in Django CMS 3.11.

PageExtensionAdmin hides the model from the Django admin index by design, so it is not discoverable by browsing. Direct URLs:

• Add: /admin/taccsite_cms/pagenavoptions/add/?extended_object=<page_pk>
• Change: /admin/taccsite_cms/pagenavoptions/<extension_pk>/change/

The CMS toolbar item generates these URLs automatically.

---

Made with Cursor. Directed and scrutinized by @wesleyboar.

[taoteg]

Works as advertised.

[wesleyboar]

Important

I like this, but I have not merged yet, because I consider changing it's name and form to suggest we can add more (e.g. pagemenutarget → pagemenuoptions), so that future features do not each require a new menu item.

Update: Done.

[wesleyboar]

Polished. Future additions would not further increase size of main menu.

Might not use, because WP-1290 has simpler solution: add sub-domain to URL.