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

esc_html is not safe for exception handling in wp-redis #866

Open
6 of 19 tasks
roborourke opened this issue Apr 1, 2024 · 2 comments
Open
6 of 19 tasks

esc_html is not safe for exception handling in wp-redis #866

roborourke opened this issue Apr 1, 2024 · 2 comments
Labels
bug Existing functionality isn't behaving as expected must have Must be done, high priority
Milestone

Comments

@roborourke
Copy link
Contributor

roborourke commented Apr 1, 2024

This is a bug inherited after merging the upstream changes to wp-redis to our fork.

Issues on the pantheon repo:

PR merged on upstream repo:

We need to merge the upstream changes again, release and update the cloud module.

If we're not maintaining any of our own changes to the upstream version any more, or if we only forked it to publish to packagist, I would suggest we change Altis to include the upstream as a dependency now that Pantheon have published it https://packagist.org/packages/pantheon-systems/wp-redis

After discussion, it looks like there is no longer any need to keep the HM fork.

Acceptance Criteria

  • Remove our forked version and change to upstream
  • Test everything still works.
  • Archive HM fork

For Altis Team Use

Ready for Work Checklist

Is this ticket ready to be worked on? See
the Play Book Definition of Ready

  • Is the title clear?
  • Is the description clear and detailed enough?
  • Are acceptance criteria listed?
  • Have any dependencies been identified? (Optional)
  • Have any documentation/playbook changes been identified? (Optional)
  • Is an estimate or time box assigned?
  • Is a priority label assigned?
  • Is this ticket added to an epic? (Optional)

Completion Checklist

Is this ticket done? See
the Play Book Definition of Done

  • Has the acceptance criteria been met?
  • Is the documentation updated (including README)?
  • Do any code/documentation changes meet project standards?
  • Are automatic tests in place to verify the fix or new functionality?
  • Or are manual tests documented (at least on this ticket)?
  • Are any Playbook/Handbook pages updated?
  • Has a new module release (patch/minor) been created/scheduled?
  • Have the appropriate backport labels been added to the PR?
@roborourke roborourke added the bug Existing functionality isn't behaving as expected label Apr 1, 2024
@mikelittle mikelittle added to refine Issues needing refine must have Must be done, high priority labels Apr 2, 2024
@mikelittle
Copy link
Contributor

mikelittle commented Apr 2, 2024

I added to refine and must have labels.
We need to check we are ok to switch to the upstream version, or, if we are changing it in some way, incorporate the bug fix.

@mikelittle
Copy link
Contributor

@mikelittle mikelittle removed the to refine Issues needing refine label Apr 3, 2024
@kovshenin kovshenin added this to the Altis v22 milestone Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Existing functionality isn't behaving as expected must have Must be done, high priority
Projects
None yet
Development

No branches or pull requests

3 participants