fix: add support for The Events Calendar#599
Merged
planv merged 1 commit intoudx:latestfrom Oct 16, 2023
Merged
Conversation
[The Events Calendar](https://wordpress.org/plugins/the-events-calendar/) does not use local media files. However, it was looking for a filename 'silence' which was confused by the cache-buster.
3ae3288 to
7a31f7f
Compare
Member
|
Related conversation on .org forums at https://wordpress.org/support/topic/incompatibility-with-the-events-calendar-2/ |
Contributor
|
Hello @donbowman We are going to include this feature to our next release. Do you still use this compatibility? Can you please provide some details about configuration where do you use it. |
Contributor
Author
|
yes i still use it. |
balexey88
approved these changes
Oct 3, 2023
Merged
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
4 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.
The Events Calendar
does not use local media files. However, it was looking for a filename
'silence' which was confused by the cache-buster.