webui gallery: follow the WebUI page rename - #134
Merged
Conversation
Code Review by QodoNo Changes in PRQodo reviewed your PR and found no changes in the codeTip of the day💡 Did you know, you can route each action level your way: inline, summary, both, or drop |
The WebUI renamed every page after the word its own menu uses, so the eleven paths this file photographs no longer exist: status.cgi is dashboard.cgi, preview.cgi is live.cgi, mj-settings.cgi is camera.cgi, and so on. The old paths still answer, but only as tombstones that 302 away, and those carry a removal date — a gallery run against them would follow a redirect today and photograph a 404 later. Captions follow the same source. They are meant to be the page's name as the camera prints it, and the camera prints the nav word now, prefixed by its menu where it has one: "System - Network", not "Network Settings". That is the whole browser title, which is what a reader is matching against on the device. Slugs move where the name they carried is gone — status/preview/majestic-* have no meaning left — and the image pairs move with them so the tiles keep resolving. WHAT THIS DOES NOT DO: the images are still pictures of the old UI, so five tiles now caption a Dashboard screenshot "Dashboard" while the screenshot itself says "Device Status". Re-shooting needs tools/webui-gallery pointed at a real camera, and that publishes a camera's own frames to a public site, so it is a deliberate act rather than a side effect of a rename. Run it when there is a camera whose picture is meant to be published.
openipc-ai
force-pushed
the
webui-gallery-page-rename
branch
from
September 4, 2026 09:55
c510024 to
f161697
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The WebUI has renamed every page after the word its own menu uses
(OpenIPC/majestic-webui#319), so the eleven paths this gallery photographs no
longer exist:
status.cgiisdashboard.cgi,preview.cgiislive.cgi,mj-settings.cgiiscamera.cgi, and so on.The old paths do still answer — but only as tombstones that 302 away, and those
carry a removal date. A gallery run against them would follow a redirect today
and photograph a 404 later.
Captions follow the same source. This file says a caption is "the page title as
the camera prints it", and the camera prints the nav word now, prefixed by its
menu where it has one: System - Network, not Network Settings. That is the
page's whole browser title, which is what a reader is matching against on the
device.
Slugs move only where the name they carried has no meaning left —
status/preview/majestic-*— and the image pairs move with them so thetiles keep resolving.
What this deliberately does not do
The images are still pictures of the old UI, so five tiles now caption a
screenshot "Dashboard" while the screenshot itself says "Device Status".
Re-shooting needs
tools/webui-gallerypointed at a real camera, and thatpublishes a camera's own frames to a public site. That is a deliberate act
rather than a side effect of a rename, so it wants a camera whose picture is
meant to be published. Worth doing before or soon after this merges — the
mismatch is visible on
/web-interfaceeither way, and it is a smaller wrongthan tiles that point at pages which have moved.