Skip to main content

Planner 1.0.0 - "Show Planner" toggle broken - missing /api/views/ endpoint (404)

Body:

Summary

The "Show planner" toggle in the Scheduler view does nothing. Both the right-click context menu option and the P keyboard shortcut fail silently.

Environment

  • AYON Server: 1.15.11+202607031715 (latest)

  • Planner Addon: 1.0.0

  • Browser: Chrome

  • OS: Windows

Steps to Reproduce

  1. Open a project in the Scheduler view

  2. Right-click on the timeline → click "Show planner"

  3. Nothing happens — the planner panel does not appear

Console Errors

Two errors appear in DevTools console:

1. API endpoint not found:

GET http://link/api/views/scheduler/base? 404 (Not Found)

2. Settings update blocked:

updateViewSettings: no settings baseline available, aborting to prevent data loss.

Call stack: command (SchedulerRemote-B3whaLuu.js:80) → LicenseWrapper-blS_677C.js:28 → updateViewSettings (WithViews-BQrbuIVR.js:1) → aborts

Root Cause

The Planner 1.0.0 addon's frontend uses the Views API (/api/views/scheduler/base) to load a settings baseline when the Scheduler page loads. This endpoint returns 404 on AYON Server 1.15.11 because the /api/views/ API does not exist yet on the server.

Without the baseline, the updateViewSettings function in the core frontend (WithViews-BQrbuIVR.js) refuses to save any setting changes as a safety measure, which means the planner toggle cannot be persisted and the panel never appears.

The addon's package.py declares ayon_server_version = ">=1.14.0", but the addon actually requires a server version that includes the /api/views/ endpoint.

Expected Behavior

Clicking "Show planner" should toggle the planner panel above the scheduler timeline.

Suggested Fix

Either:

  1. The AYON server needs to ship the /api/views/ API endpoint, or

  2. The Planner addon needs to handle the 404 gracefully and fall back to localStorage or default settings

2 comments

Log in to comment and vote

Comments2

  • Luke Inderwick

    Team

    Thank you for the report, a newer version we will release soon should fix it.

    The work around to get it to work is to create a new view on that page first, then it should start working.

    • #youssef#

      Thank you for looking into this so quickly.