Content Page grid view url doesn't work for some pages

[MrBlueEyez]

Preconditions and environment

• 2.4.6-p1
• Use the fix inside https://github.com/magento/magento2/pull/37532 so that the encoded uenc is also being decoded correctly.

Steps to reproduce

1. Open the admin panel and login
2. Go towards Content > Elements > Pages
3. Make sure some pages are existing, and try to use the "View" action of some.

Expected result

Every view action should work, and we should end up on the page we wanted to view. As of 2.4.6 the url encode is working with RFC3986, and is decoding = to ~ instead of a comma. We expect all urls to now work with tildes.

Actual result

The view url is generated using the Magento\Framework\Url\QueryParamsResolver which is using the default php function http_build_query to convert the url . However the uenc which is included is using the new encoder, and so can have tildes in it. The http_build_query is using the PHP_QUERY_RFC1738 instead of the PHP_QUERY_RFC3986 which causes the tildes to be converted towards %7E.

This all ends up with the admin getting redirect towards the home page, and not the page that was requested.

Additional information

It might be hard to reproduce this, as I am not 100% sure when the unencoded uenc contains =.

Release note

Using RFC3986 in the http_build_query, to be in line with https://github.com/magento/magento2/pull/35885

Triage and priority

• [ ] Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• [ ] Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• [X] Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• [ ] Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• [ ] Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant[bot]]

Hi @MrBlueEyez. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this

• To learn more about issue processing workflow, refer to the Code Contributions.

  Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant[bot]]

Hi @engcom-Bravo. Thank you for working on this issue. In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• [ ] 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• [ ] 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• [ ] 5. Add label Issue: Confirmed once verification is complete.
• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://55d1cece3065473da76e4c11c178cada.instances-prod.magento-community.engineering Admin access: https://55d1cece3065473da76e4c11c178cada.instances-prod.magento-community.engineering/admin_7983 Login: 830bc424 Password: faa9c4df3462

[engcom-Bravo]

Hi @MrBlueEyez,

Thank you for reporting and collaboration.

Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

• Open the admin panel and login
• Go towards Content > Elements > Pages
• Make sure some pages are existing, and try to use the "View" action of some.

Every view action is working we are getting the page wanted to view and ~ converting instead of a comma.please let us if we are missing anything.

Thanks.

[engcom-Bravo]

Hi @MrBlueEyez,

Kindly provide latest update on this comment https://github.com/magento/magento2/issues/37869#issuecomment-1673093202 still you are working on this issue if you are able to reproduce the issue please elaborate the steps to reproduce.Please let us know still if you are facing any issue.

Thanks.

[MrBlueEyez]

Hello, The issue is still reproducable, it is beter to check the decoded uenc inside the preview url itself. Instead of checking the final page you end up. In the provided example provided by @engcom-Bravo I do not see any "~" inside the url, hence the situation is not reproduced.

Please try again with another page with larger names (I do not know what triggers the "=" inside base64 decoded string, but you will have to reproduce that)

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://55d1cece3065473da76e4c11c178cada.instances-prod.magento-community.engineering Admin access: https://55d1cece3065473da76e4c11c178cada.instances-prod.magento-community.engineering/admin_e5fa Login: 8122b51d Password: e3fc7eb3ca0d

[engcom-Bravo]

Hi @MrBlueEyez,

Thanks for your update.

We have given ~ for content pages and it is converting into - in SEO.

While giving ~ in SEO section we are getting below error.

Could you please elaborate the steps to reproduce and also provide screenshots and video if possible it will helps us to reproduce the issue easily.

Thanks.

[MrBlueEyez]

Hello @engcom-Bravo ,

it is not about having those characters in the page title. For some pages, which a normal title, the url that is generated and then encoded for the switch/redirect action, is getting a ~.

Try having a url for the page which does not have a multitude of 4 characters. As base64 encoding adds extra = characters to make sure it has a multitude of 4 characters. (EG: example.test/heyy has 17 characters, which is 1 more then any amount of 4 characters). Also keep in mind that https:// will also be added and will also help in this count. So best thing is to just try changing the url_key with + 1 letter untill you get an encoded url with == in it, which should then be changed to ~.

[engcom-Bravo]

@magento give me 2.4-develop instance

[magento-deployment-service[bot]]

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service[bot]]

Hi @engcom-Bravo, here is your Magento Instance: https://55d1cece3065473da76e4c11c178cada.instances-prod.magento-community.engineering Admin access: https://55d1cece3065473da76e4c11c178cada.instances-prod.magento-community.engineering/admin_2642 Login: 1bfda593 Password: ed01a59c97da

[engcom-Bravo]

Hi @MrBlueEyez,

Thanks for your update.

We have used this String magentothusdw which contains Encoded value as bWFnZW50b3RodXNkdw==.The same value we have given in Url key for pages.

The view action is working fine and we are able to access the page.Could you please let us know if we are missing anything.Please provide screenshots it will helps us to proceed further.

Thanks.

[engcom-Bravo]

Hi @MrBlueEyez,

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.