Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: Browser back function in Backendmodules #2791

Open
breadlesscode opened this issue Nov 29, 2019 · 2 comments
Open

BUG: Browser back function in Backendmodules #2791

breadlesscode opened this issue Nov 29, 2019 · 2 comments
Labels

Comments

@breadlesscode
Copy link
Contributor

Description

I’m not sure if this is the right place for it, but me and @Sebobo discovered a bug in the Neos Backend modules. If you visit a backend module one XHR is sent out, if you then click on a subpage of the module and afterwards use the browser’s back button, you get the unparsed markup. This only happens with the Redirect Handler UI (as far as we can tell).

See here: neos/redirecthandler-ui#41

Steps to Reproduce

  1. Visit redirect handler ui backend module
  2. Click export redirects
  3. Click browsers back button
  4. Unparsed markup shown

Expected behavior

Unparsed markup shown

Actual behavior

See the backend module

Affected Versions

Neos: 5.0.4
Neos Ui: 5.0.1
Flow: 6.0.5

@Sebobo
Copy link
Member

Sebobo commented Nov 29, 2019

Important note: The XHR is sent in every backend module with Neos 5, but only the redirect module with it's actions seems to trigger the issue.

@Sebobo Sebobo added the Bug label Nov 29, 2019
@Sebobo
Copy link
Member

Sebobo commented Dec 13, 2019

Found out where the second request comes from. During the partial ember removal the endpoint url for the neos-nodetypeschema was removed and the backend still tries to load it. If no url is defined it will use the current url.
Adding the missing line again will solve the issue.

But we actually don't need the schema for backendmodules. So it would be better if our backend wouldn't try to load the schema if it's not defined.

@markusguenther maybe you can look into this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants