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

Update recently-added PathUrlTest to be more representative #16607

Merged
merged 1 commit into from
Feb 21, 2020

Conversation

totten
Copy link
Member

@totten totten commented Feb 21, 2020

Before

The test generates the URL for an example page (civicrm/mailing/subscribe)
by calling url(). It does not explicitly set the url(...$frontend...) option,
so it defaults to $frontend=FALSE.

By contrast, the other places which make URLs for civicrm/mailing/subscribe
(eg CRM/Mailing/BAO/Mailing.php and CRM/Utils/Token.php) do pass $frontend=TRUE.

After

The test behaves the same way as other code (i.e. passing $frontend=TRUE).

Comments

This issue was noticed while debugging this E2E test on WP (which has been failing). This plausibly would cause problems with the correctness of the test on WP/J, although (in my local testing so far) I don't think this actually fixes things. But it's still good to address.

Before
------

The test generates the URL for an example page (`civicrm/mailing/subscribe`)
by calling `url()`. It does not explicitly set the `url(...$frontend...)` option,
so it defaults to `FALSE`.

By contrast, the other places which make URLs for `civicrm/mailing/subscribe`
(eg `CRM/Mailing/BAO/Mailing.php` and `CRM/Utils/Token.php`) do set `$frontend` to `TRUE`.

After
-----

The test behaves the same way as other code.
@civibot
Copy link

civibot bot commented Feb 21, 2020

(Standard links)

@seamuslee001
Copy link
Contributor

this makes sense

@seamuslee001 seamuslee001 merged commit 3f7f127 into civicrm:5.23 Feb 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants