DOCUMENTATION

Documentation for the way you actually build.

Start with installation and FileMaker connection setup, then move through shortcodes, parameters, scripts, containers, helpers, troubleshooting, and hosted WP-CLI operations.

WordPress Functions

Universal Toggle Setting Callback

cwp_universal_toggle_setting_callback()

Universal AJAX handler for admin toggle switches and settings updates. Handles all validation, nonce checking, and permission verification.

Parameters (via POST/AJAX):

  • action (string): Always 'cwp_universal_toggle_setting'
  • option_name (string): WordPress option group name (e.g., 'cwp_authnet_api_keys')
  • setting_key (string): Specific setting key within that option (e.g., 'api_mode')
  • setting_value (string): Value to save
  • message (string): User-friendly notification message
  • nonce (string): Security nonce token

Returns:

  • Success: {'success': true, 'data': {'message': '...'}}
  • Error: {'success': false, 'data': {'message': '...'}}

Security Features:

  • Nonce verification via check_ajax_referer()
  • Capability check (manage_options)
  • Input sanitization on all fields

cwp_safe_redirect($url, $status = 302)

Safely redirect to a URL, even if headers have already been sent. Critical for WordPress custom development environments where traditional wp_redirect() fails due to output buffering and header conflicts.

Why This Function is Essential: In WordPress custom development and snippet environments, wp_redirect() rarely works because:

  • The page has already loaded by the time plugins/snippets execute
  • Headers are sent early in the WordPress loading process
  • Output buffering issues prevent proper header modification
  • Content is already being output before redirect logic runs

Usage:

// Basic redirect - works even after headers sent
cwp_safe_redirect(home_url('/thank-you'));

// Redirect with custom status code
cwp_safe_redirect('https://example.com', 301);

Parameters:

  • $url (string): The URL to redirect to
  • $status (int, optional): HTTP status code (default: 302)

Fallback Behavior:

  • Headers not sent: Uses standard wp_redirect() and exits
  • Headers already sent: Falls back to HTML meta refresh + JavaScript redirect:
    <meta http-equiv="refresh" content="0;url=https://example.com">
    <script>window.location.href="https://example.com";</script>

Returns:

  • false if URL is empty/invalid
  • Does not return on successful redirect (exits execution)

Security:

  • Automatically escapes URLs for HTML and JavaScript contexts
  • Validates URL before redirecting
PROVIDED BY RGC DATA

Free tools, backed by real integration experience.

CWP Snippets, restCWP, and ODataCWP are provided free by RGC Data to help developers build better FileMaker-connected websites.

They are shaped by the same practical experience we bring to custom FileMaker, WordPress, PHP, Data API, and OData projects.

FILEMAKER • WORDPRESS • PHP • APIs
NEED A CUSTOM SOLUTION?

Bring us your integration project.

Whether you need a complete FileMaker-to-web application or help with one difficult part, RGC Data can help you plan, build, troubleshoot, and deploy it.

Architecture, custom development, API integration, security, deployment, and ongoing support—all shaped around your solution.

Tell us what you are building and where you would like help.