Url slug isn't working on mapped home page
Permalink Browser Info Environment
I can't access the mapped main page on subdomain with the url slug.
This seems to break the functionality of form block, since it's posting it's results to the slug url.
Subpages' slugs are working properly.
This seems to break the functionality of form block, since it's posting it's results to the slug url.
Subpages' slugs are working properly.
Type: | Discussion |
---|---|
Status: | Resolved |
Also, please check that you are running the latest version of the add-on if you have updated your core version lately.
Updating the plugin or toggling the navigation helper override didn't solve the issue.
Do you have full page caching enabled?
No.
Can you post a link to this page?
The site isn't online yet. I'll get back to you when it is.
OK, thanks.
Seems strange, as I tested this with a fresh installation, the form was working properly. The important thing is to have the navigation helper override enabled so that the action URL is replaced with the correct slug without the parent page.
I might also require direct access to the site in case this is something environment specific. Or if you can make another fresh installation and try to create the exact steps to replicate the problem, it would also help in case we can get the same issue appearing at our end.
Seems strange, as I tested this with a fresh installation, the form was working properly. The important thing is to have the navigation helper override enabled so that the action URL is replaced with the correct slug without the parent page.
I might also require direct access to the site in case this is something environment specific. Or if you can make another fresh installation and try to create the exact steps to replicate the problem, it would also help in case we can get the same issue appearing at our end.
The problem seems to be related to the fact that I'm redirecting to a subpage in the current domain after submission.
Navigation helper doesn't seem to handle the redirect url properly.
Navigation helper doesn't seem to handle the redirect url properly.
OK, thanks.
This is very helpful and I could replicate this bug by setting a redirect page for the form. We'll look into this.
This is very helpful and I could replicate this bug by setting a redirect page for the form. We'll look into this.
Seems like the form block is using the page's direct path for the redirection instead of using the navigation helper or fetching the page URL with the page object.
So, the problem is here:
https://github.com/concrete5/concrete5/blob/67b0c0ae41710a4c4506787d...
It's quite tough to solve through our add-on without adding yet another block override to the package which we would like to avoid as far as possible.
You can fix this locally if you change this highlighted line in the link into:
This would probably be better to be fixed in the core. We will later check into creating a pull request for the core for resolving this issue.
So, the problem is here:
https://github.com/concrete5/concrete5/blob/67b0c0ae41710a4c4506787d...
It's quite tough to solve through our add-on without adding yet another block override to the package which we would like to avoid as far as possible.
You can fix this locally if you change this highlighted line in the link into:
\Redirect::page($pg)->send(); exit;
This would probably be better to be fixed in the core. We will later check into creating a pull request for the core for resolving this issue.
There is now a pull request for this:
https://github.com/concrete5/concrete5/pull/3596...
We'll see how it goes. If they merge it, the issue will be fixed in the next core release.
https://github.com/concrete5/concrete5/pull/3596...
We'll see how it goes. If they merge it, the issue will be fixed in the next core release.
Nice, thanks.
Seems Andrew just merged the pull request, so this should probably be fixed in the next core release.
Do you have the navigation helper override enabled from the multiple domains settings?