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
For most top-level pages ('home', 'blog', 'shop', etc.), I disallow the option to 'Change URL'. In a page that doesn't allow the user to change the URL, clicking on the URL link inside the SEO field will cause an error. If the site's 'debug' option is true, it will trigger the Kirby debugger. If 'debug' is false, it will go to a Panel Error page that states that 'you are now allowed to do this'.
Steps to reproduce:
edit the blueprint of one of your site's pages, to disallow changing of the page's URL:
title: Homeicon: homeoptions:
url: false[...]
add the SEO field to the page:
fields:
seo:
type: seo
Go to the Panel, and in the SEO field that is now displaying, click the page's URL - which appears in green underneath the Page Title.
This will cause an error on the site - Kirby 2.5.4.
Ideal Solution:
The plugin should check whether 'change url' is permitted for the current page/user, and if not, the URL in the field should not be a clickable link.
The text was updated successfully, but these errors were encountered:
luxlogica
changed the title
Crash When Clicking URL and 'Change URL' Is Forbidden
Error When Clicking URL and 'Change URL' Is Forbidden
Aug 5, 2017
For most top-level pages ('home', 'blog', 'shop', etc.), I disallow the option to 'Change URL'. In a page that doesn't allow the user to change the URL, clicking on the URL link inside the SEO field will cause an error. If the site's 'debug' option is true, it will trigger the Kirby debugger. If 'debug' is false, it will go to a Panel Error page that states that 'you are now allowed to do this'.
Steps to reproduce:
This will cause an error on the site - Kirby 2.5.4.
Ideal Solution:
The plugin should check whether 'change url' is permitted for the current page/user, and if not, the URL in the field should not be a clickable link.
The text was updated successfully, but these errors were encountered: