You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's possible to set the Catalog page to have a Parent other than the default (no parent)
Doing so updates the permalink from https://[domain]/catalog to, for example, https://[domain]/home/catalog
However, setting the Catalog page to have a Parent other than the default (no parent) causes the View Complete Catalog button on the network home page to link back to the network home page instead of the catalog.
This bug is affecting one client at the moment.
Steps to replicate
As a network manager or super admin, navigate to Appearance to modify the network home page.
Ensure that the Front Page Catalog is set to be shown on the home page, including at least one selected book.
Navigate back to the admin dashboard and to Pages.
Open the editor for the Catalog page.
Set the Parent of this page to something other than (no parent)
Save changes.
Return to the network home page.
Press the View Complete Catalog button.
We expect to be taken to the catalog but the link just leads to the network home page that we're currently on.
The text was updated successfully, but these errors were encountered:
The workaround of reverting the Catalog to the default https://[domain]/catalog (restoring the working link) has been applied by the client who was affected by this.
It's possible to set the Catalog page to have a Parent other than the default
(no parent)
Doing so updates the permalink from
https://[domain]/catalog
to, for example,https://[domain]/home/catalog
However, setting the Catalog page to have a Parent other than the default
(no parent)
causes the View Complete Catalog button on the network home page to link back to the network home page instead of the catalog.This bug is affecting one client at the moment.
Steps to replicate
(no parent)
We expect to be taken to the catalog but the link just leads to the network home page that we're currently on.
The text was updated successfully, but these errors were encountered: