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

Refresh routePath for page_tree_route based Article #667

Open
Olivier127 opened this issue Mar 15, 2024 · 2 comments
Open

Refresh routePath for page_tree_route based Article #667

Olivier127 opened this issue Mar 15, 2024 · 2 comments
Assignees

Comments

@Olivier127
Copy link
Contributor

Q A
Bug? yes
New Feature? no
SuluArticleBundle Version 2.5.3
Sulu Version 2.5.13

Actual Behavior

The "refresh URL" button to update the slug of an article using a routePath based on page_tree_route calls an unknown route.

Expected Behavior

A correctly updated slug.

Steps to Reproduce

Create an article with the
page_tree.txt

put "page test" inside title section.
clic on the slug and put "page-test" inside
clic on refresh url

le browser call http://localhost/admin/undefined
with this payload

{
    "parts": {
        "title": "page test"
    },
    "resourceKey": "articles",
    "locale": "fr",
    "id": null,
    "entityClass": null,
    "routeSchema": "/{implode('-', object)}"
}

Possible Solutions

This page should have the same behavior as an article using the routePath of type route and calling the URL admin/api/routes?action=generate with the correct parameters.

@alexander-schranz
Copy link
Member

alexander-schranz commented Jun 7, 2024

Did it work on 2.5.12? Then it might be related to changes in sulu/sulu#7271. /cc @wachterjohannes

@Olivier127
Copy link
Contributor Author

@alexander-schranz no error with the "route" type. Only with the "page_tree_route".

I have test with sulu 2.5.19 and sulu article 2.6.0

See this sceen shoot

image

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

No branches or pull requests

3 participants