Fix missing latest entries on dashboard

[Crabcyborg]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@Crabcyborg has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 51 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 08846bc and 459a93b.

📒 Files selected for processing (3)

• classes/controllers/FrmDashboardController.php (1 hunks)
• classes/controllers/FrmEntriesController.php (1 hunks)
• classes/helpers/FrmEntriesHelper.php (1 hunks)

Walkthrough

The pull request introduces changes to how unread inbox entries are counted and displayed across multiple files in the Formidable Forms plugin. The primary modification involves creating a new method get_visible_unread_inbox_count() in the FrmEntriesHelper class to retrieve the number of unread inbox messages. This count is then used to dynamically modify the dashboard column filter name in the FrmDashboardController, potentially providing more contextual information about unread entries.

Changes

File	Change Summary
classes/helpers/FrmEntriesHelper.php	Added new get_visible_unread_inbox_count() static method to retrieve unread inbox count based on Pro version settings
classes/controllers/FrmDashboardController.php	Modified filter name construction to dynamically include unread count
classes/controllers/FrmEntriesController.php	Simplified unread count retrieval logic

Sequence Diagram

sequenceDiagram
    participant EH as EntriesHelper
    participant DC as DashboardController
    participant PH as ProHelper
    participant Inbox as FrmInbox

    EH->>PH: Check Pro version installed
    EH->>PH: Get settings
    EH->>Inbox: Create instance
    Inbox-->>EH: Return unread count
    EH-->>DC: Provide unread count
    DC->>DC: Construct dynamic filter name

Loading

Possibly related PRs

• Fix issue with entries page when inbox badge is disabled #2202: Modifies the base_column_key method in FrmEntriesController, which is directly connected to the unread count logic changes in this PR.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.