Skip to content

Fix sticky listing order for plan custom sorts#514

Merged
sorinmarta merged 4 commits into
masterfrom
fix/sticky-plan-sort
Jul 6, 2026
Merged

Fix sticky listing order for plan custom sorts#514
sorinmarta merged 4 commits into
masterfrom
fix/sticky-plan-sort

Conversation

@sorinmarta

@sorinmarta sorinmarta commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

fixes Strategy11/business-directory-premium#354.

Featured sticky listings now honor plan weight and title/date ordering for plan-order-title and plan-order-date directory sorts.

Featured listings now follow plan weight and title/date when directory sorting uses plan-order-title or plan-order-date.
@coderabbitai

coderabbitai Bot commented Jul 3, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@sorinmarta, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 28 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5df1f3b7-7598-4a53-9ef9-d625cae809a5

📥 Commits

Reviewing files that changed from the base of the PR and between f3062df and 9982984.

📒 Files selected for processing (2)
  • includes/class-query-integration.php
  • tests/wpunit/Listing/ListingQuerySortTest.php
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/sticky-plan-sort

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sorinmarta sorinmarta added the run analysis Runs phpcs and phpunit label Jul 3, 2026
The test now accepts the database success result returned by set_fee_plan.
The regression test now avoids post__in ordering and cleans created records between cases.
The test now verifies the sticky ID order directly instead of relying on front-end query hooks.
@sorinmarta
sorinmarta merged commit ec03299 into master Jul 6, 2026
5 checks passed
@sorinmarta
sorinmarta deleted the fix/sticky-plan-sort branch July 6, 2026 05:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

run analysis Runs phpcs and phpunit

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant