Testing setting wp version #3584
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…emplate for emails
…age-template-override-path-correction [ET-2296] Correct template override path for My Tickets page
…s-calendar/event-tickets into feature/add_ian_for_et
…s-calendar/event-tickets into feature/add_ian_for_et
…s-calendar/event-tickets into feature/add_ian_for_et
…-booking-fees-to-emails [ET-2297] Add Booking Fees to Confirmation Emails
…m:the-events-calendar/event-tickets into fix/ET-2309-prevent-fatal-attenddee-model
* Modify pup config and GitHub zip workflow. * Organize composer.json and add code to prevent composer from timing out when running pup build commands. * Add distfiles * update-browserslist (bonus)
…vent-tickets into fix/ET-2309-prevent-fatal-attenddee-model
…m:the-events-calendar/event-tickets into fix/ET-2309-prevent-fatal-attenddee-model
Co-authored-by: Stephen Page <[email protected]>
…-fatal-attenddee-model Prevent fatal error for Attendee Models with Invalid Orders
coupled with removing the update --force in the yml files.
tec-bot
reviewed
Feb 21, 2025
| date_i18n( tribe_get_date_format( true ), strtotime( esc_attr( $order['purchase_time'] ) ) ) | ||
| esc_attr( $purchaser_name ), | ||
| '<a href="mailto:' . esc_url( $purchaser_email ) . '">' . esc_html( $purchaser_email ) . '</a>', | ||
| $purchase_time ? date_i18n( tribe_get_date_format( true ), strtotime( esc_attr( $purchase_time ) ) ) : __( 'Unknown Time (invalid order)', 'event-tickets' ) |
There was a problem hiding this comment.
[phpcs] reported by reviewdog 🐶StellarWP.XSS.EscapeOutput.OutputNotEscaped
Expected next thing to be an escaping function (see Codex for 'Data Validation'), not '$purchase_time'
| date_i18n( tribe_get_date_format( true ), strtotime( esc_attr( $order['purchase_time'] ) ) ) | ||
| esc_attr( $purchaser_name ), | ||
| '<a href="mailto:' . esc_url( $purchaser_email ) . '">' . esc_html( $purchaser_email ) . '</a>', | ||
| $purchase_time ? date_i18n( tribe_get_date_format( true ), strtotime( esc_attr( $purchase_time ) ) ) : __( 'Unknown Time (invalid order)', 'event-tickets' ) |
There was a problem hiding this comment.
[phpcs] reported by reviewdog 🐶WordPress.Security.EscapeOutput.OutputNotEscaped
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found 'date_i18n'.
| date_i18n( tribe_get_date_format( true ), strtotime( esc_attr( $order['purchase_time'] ) ) ) | ||
| esc_attr( $purchaser_name ), | ||
| '<a href="mailto:' . esc_url( $purchaser_email ) . '">' . esc_html( $purchaser_email ) . '</a>', | ||
| $purchase_time ? date_i18n( tribe_get_date_format( true ), strtotime( esc_attr( $purchase_time ) ) ) : __( 'Unknown Time (invalid order)', 'event-tickets' ) |
There was a problem hiding this comment.
[phpcs] reported by reviewdog 🐶StellarWP.XSS.EscapeOutput.OutputNotEscaped
Expected next thing to be an escaping function (see Codex for 'Data Validation'), not ')'
| date_i18n( tribe_get_date_format( true ), strtotime( esc_attr( $order['purchase_time'] ) ) ) | ||
| esc_attr( $purchaser_name ), | ||
| '<a href="mailto:' . esc_url( $purchaser_email ) . '">' . esc_html( $purchaser_email ) . '</a>', | ||
| $purchase_time ? date_i18n( tribe_get_date_format( true ), strtotime( esc_attr( $purchase_time ) ) ) : __( 'Unknown Time (invalid order)', 'event-tickets' ) |
There was a problem hiding this comment.
[phpcs] reported by reviewdog 🐶WordPress.Security.EscapeOutput.OutputNotEscaped
All output should be run through an escaping function (see the Security sections in the WordPress Developer Handbooks), found '__'.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.