Add a null check to avoid deprecated message when previewing

[Crabcyborg]

This is more of a WP/Theme issue, but this update helps make sure that Formidable isn't triggering a deprecated message.

[coderabbitai]

Walkthrough

The update introduces a new private static function to the FrmFormsController class, aimed at addressing the issue of null values in a specific filter. This function, fix_deprecated_null_param_warning(), ensures that no deprecated warnings are triggered by setting null $src values to an empty string, thereby maintaining smoother operations and compatibility.

Changes

File	Change Summary
.../FrmFormsController.php	Added a new private static function fix_deprecated_null_param_warning() to handle null $src values in a filter, preventing deprecated messages by ensuring $src is not null through assignment of an empty string if it is null.

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1b5120e and 4a00ed1.

Files selected for processing (1)

• classes/controllers/FrmFormsController.php (1 hunks)

Files skipped from review as they are similar to previous changes (1)

• classes/controllers/FrmFormsController.php

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 0

Out of diff range and nitpick comments (2)

classes/controllers/FrmFormsController.php (2)

Line range hint 347-355: Consider refactoring the method maybe_load_css to avoid direct manipulation of global variables, which can lead to maintainability issues. Encapsulating the state management within a class or using getter/setter methods could enhance robustness.

---

Line range hint 357-365: The method footer_js uses global variables to manage script loading state. Consider refactoring to improve clarity and encapsulate state management, possibly by moving state-related logic to a dedicated class or method.