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

Actions are returned with an incorrect back url #236

Closed
tusmester opened this Issue Dec 15, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@tusmester
Member

tusmester commented Dec 15, 2017

When you get the available actions in a scenario through OData, the back url parameter is incorrect (it points to an OData url, which is invalid for a back url).

Repro steps

  1. got to /Root/IMS/BuiltIn in Content Explorer
  2. open the Add menu and check the urls: the back url param will be invalid
  3. choose any of the types - for example OrgUnit
  4. create an orgunit and hit Save --> the orgunit will be created but the page will be redirected to the incorrect url, which results in a 404 response.

Cause and fix

The reason is that although the correct back url can be inferred from the referrer url (in this case the Explore page), we call the incorrect action getter method overload.

ODataTools, line 141

Call the other overload that accepts a back url, because currently the back url value is passed as a different argument.

@tusmester tusmester added this to the Sprint 149 milestone Dec 15, 2017

@iviczl iviczl self-assigned this Jan 9, 2018

@iviczl

This comment has been minimized.

Contributor

iviczl commented Jan 9, 2018

As I see in the application, the default accepted two content types (Domain, System Folder) under IMS both address the Explore page and do not throw errors. The mentioned ODataTools line however calls the wrong overload. Has this problem already solved in some other way?

@tusmester tusmester modified the milestones: Sprint 149, Sprint 150 Jan 10, 2018

@tusmester tusmester removed the help wanted label Jan 17, 2018

@tusmester tusmester closed this Jan 24, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment