-
Notifications
You must be signed in to change notification settings - Fork 151
Feature/template filtering search in post form #1621
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
Merged
sapayth
merged 16 commits into
weDevsOfficial:develop
from
arifulhoque7:feature/template_filtering_search_in_post_form
Jul 30, 2025
Merged
Changes from 10 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
c649a64
fix- template filtering search in post form
arifulhoque7 0da7e33
Merge branch 'weDevsOfficial:develop' into feature/template_filtering…
arifulhoque7 eb4b03b
fix: minor changes
arifulhoque7 aa96798
fix: potential cause of fatal errors
arifulhoque7 57bb3a0
fix: category select issue and template drop shadow issues
arifulhoque7 fbc9df7
fix: some design consistency like previous form
arifulhoque7 2f5e644
fix: Pro_Prompt no found
arifulhoque7 41c89c9
fix: coderabbit inconsistency issue
arifulhoque7 63fd136
chore: Follwed DRY principle
arifulhoque7 8ffe86e
fix: code rabbit issues and other design related fix
arifulhoque7 3bf7bd2
fix: animation issues
arifulhoque7 ef85d93
fix: Fix syntax error in href attribute
arifulhoque7 692eadb
fix: pro prompt not found
arifulhoque7 cbc5582
fix: design suggestion change
arifulhoque7 b0a644d
Merge branch 'weDevsOfficial:develop' into feature/template_filtering…
arifulhoque7 6467969
chore: changelog added
arifulhoque7 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
:has()is still an experimental selector – add a JS/utility‐class fallbackRelying solely on
:root:has(.wpuf-modal-open …)will silently fail in Safari ≤15.6 and old Chromium/Firefox builds shipped with WordPress Core.Recommend toggling a simple class (e.g.
wpuf-modal-lock) on<html>via the same JS that opens the modal and targeting that instead; keep the:has()rule as progressive enhancement.🤖 Prompt for AI Agents