Event Creation Date#137
Merged
arunshenoy99 merged 73 commits intoFIX/PRESS7-375-fix-retry-logicfrom May 2, 2025
Merged
Conversation
Prevent fatal error if WC()->cart is null or not an instance of WC_Cart
…tributes * main: (113 commits) Prevent fatal error if WC()->cart is null or not an instance of WC_Cart Pin full length commit SHA for 3rd party actions. version bump to 2.6.11 Register hooks of Commerce Listener only when WooCommerce is enabled Update static site-classification-data-to-0.0.6 Add checks for Commerce Listeners hooks that requires WooCommerce update plugin paths in test files swap bluehost repo path with new one Version updated 2.6.9 => 2.6.10 Remove mock for `get_current_user_id()` Mock get_current_user_id() and expect status to equal connected Set REMOTE_ADDR Ensure we properly handle status changes Exclude phpunit cache Return value and add return type Use pre_update_option hook update test workflow bluehost plugin path bump version to 2.6.9 add version bump script and command ensure capabilities is_array ...
Version updated 2.6.12 => 2.6.13
Add `wp-json/newfold-data/v1/capabilities` for pushing capabilities
…vents-via-html-attributes PRESS0-1996: Add Hiive events via HTML attributes
Contributor
wpscholar
approved these changes
Apr 18, 2025
14 tasks
Member
|
@AleTorrisi, let’s merge this into |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
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.
Proposed changes
This pull request modifies the database entry logic so that the actual creation date of the event ($event->created_at) is used instead of the current time ($time), when available.
Previous Behaviour
Currently, the "created_at" field is always populated with the current value of $time, regardless of the actual date of the event.
New Behaviour
With this change, if the $event object contains a created_at property, this is used to populate the created_at field in the database. Only in the absence of this property is the current value ($time) used as fallback.
Reason
This change is necessary to ensure that the recorded date correctly reflects the time when the event was actually generated, improving the accuracy and traceability of the data.
Type of Change
Production
Development
Video
Checklist
Further comments