FRESH FORMS FOR GRAVITY

Fresh Forms for Gravity compatibility with REEID Translate

Fresh Forms for Gravity compatibility with REEID Translate is being reviewed using official plugin documentation. Flushes the current cache on plugin activation (to allow subsequent cache-exclusion behavior to take effect). No specific text shown to visitors is currently confirmed for translation.

Visit Fresh Forms for Gravity ↗

AWAITING VERIFICATION

What Fresh Forms for Gravity does

Official plugin information supports the compatibility context documented for this category.

MANUAL REVIEW
This integration has not yet been manually verified by REEID.

PLUGIN PROFILE
Fresh Forms for Gravity is documented in the Performance category with 6 documented features.

DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.

COMPATIBILITY REVIEW

How Fresh Forms for Gravity compatibility is evaluated

01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.

02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.

03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.

04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.

PLUGIN INFORMATION

What the plugin does

Plugin capabilities

  • Flushes the current cache on plugin activation (to allow subsequent cache-exclusion behavior to take effect).
  • Detects Gravity Forms embedded via supported embedding methods (e.g., WordPress editor shortcode/Gutenberg block; various page builder widgets/modules) and conditionally prevents caching for those pages/posts.
  • Prevents caching by supported caching plugins using the DONOTCACHEPAGE constant and by respecting Cache-Control HTTP headers (for proxies/CDNs that honor them).
  • Adds appropriate HTTP headers to pages containing Gravity Forms to exclude the HTML from caching when the hosting/CDN/proxy setup allows header-based cache exclusion (with noted limitations for hosts that block header modification from WordPress).
  • Supports skipping caching for Varnish-based setups by adding a cookie when a form is detected (configurable via a filter), intended for use with caching services that exclude pages based on cookies.
  • Stores only the plugin version in the database (no other data stored), and uses the stored version to handle actions after updates when needed.

TRANSLATION BOUNDARY

Fresh Forms for Gravity capabilities and translatable content are documented separately.

Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.

A feature is not considered translatable unless it includes text that users can read.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

FREQUENTLY ASKED QUESTIONS

Fresh Forms for Gravity and REEID Translate FAQ.

What does Fresh Forms for Gravity do?

Fresh Forms for Gravity has 6 documented features listed in its official documentation. See the Plugin Information section for details.

Does Fresh Forms for Gravity have any content currently confirmed for translation?

No specific content is currently confirmed for translation in this integration.

What needs to be confirmed before translating content from Fresh Forms for Gravity?

Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.

RELATED GUIDES

Explore more compatibility guides.

COMPATIBILITY INFORMATION

Evaluate Fresh Forms for Gravity in a multilingual WordPress workflow.

REEID documents Fresh Forms for Gravity functionality separately from confirmed translation support so the distinction is clear.

Supported content will be listed when specific translatable text is identified in the official documentation.

Shopping Cart
Scroll to Top