Wheels Debugging

Troubleshoot Wheels errors in CFML applications with fixes and debugging strategies.

203|108|Updated Jan 13, 2011
One-click install
npx skills add https://github.com/wheels-dev/wheels --skill wheels-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Wheels Debugging
Source: https://github.com/wheels-dev/wheels/tree/main/.claude/skills/wheels-debugging
Command: npx skills add https://github.com/wheels-dev/wheels --skill wheels-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill empowers developers to quickly identify and resolve common errors and unexpected behavior in CFWheels applications, minimizing frustrating downtime and accelerating the debugging process. It provides clear solutions and strategies to get your application back on track.

Core Features & Use Cases

  • Common Error Solutions: Provides direct fixes for frequent issues like "Missing argument name," "Can't cast Object type [Query] to [Array]," and "Association/Table/Column not found" errors.
  • Debugging Tool Guidance: Guides on enabling Wheels debug output, inspecting variables with cfdump, and checking SQL queries.
  • Browser Testing Integration: Offers quick starts for using browser MCP tools (Puppeteer, Playwright) to debug UI/view issues and verify form submissions.
  • Use Case: When your application throws a cryptic "Missing argument name" error, this skill immediately points to mixed positional/named arguments, shows you the exact fix, and guides you on how to enable detailed debug output for deeper investigation, saving you hours of guesswork.

Quick Start

In config/settings.cfm:

set(showDebugInformation=true); set(showErrorInformation=true);

In your code for quick inspection:

<cfdump var="#myVariable#" label="My Variable"> <cfabort>

Frequently Asked Questions about Wheels Debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a 'Missing argument name' error in CFWheels?

This error occurs when mixing positional and named arguments in Wheels function calls. Review your controller or model code for functions using both styles—convert all arguments to named format. Enable debug output via `set(showDebugInformation=true)` in config/settings.cfm to see exact argument positions and values.

How do I troubleshoot 'Can't cast Object type [Query] to [Array]' errors in Wheels?

This casting error typically happens when a query result is passed where an array is expected, often in validation rules or model associations. Check that your database queries return the correct data type, and verify validation rule definitions match their input format using `cfdump` to inspect variable types.

What's the best way to debug renderView versus renderPage in Wheels?

renderPage renders a complete layout; renderView renders only a view partial without layout. Use renderView for AJAX requests and component reloads, renderPage for full page responses. Enable Wheels debug output to trace which render method is executing and confirm layout inclusion.

How do I fix 'Association/Table/Column not found' errors in Wheels migrations?

These errors signal incorrect model associations or missing database columns. Verify column names match exactly in your migration files and model relationship definitions. Inspect the generated SQL using debug output, then check your database schema directly with database tools to confirm the structure exists.

Can I use browser testing tools to debug Wheels view and form issues?

Yes, Wheels debugging integrates with browser MCP tools like Puppeteer and Playwright to automate UI testing and form submission verification. Use these tools to capture screenshots, inspect DOM elements, and verify that views render correctly without manual browser steps.

Why does my Wheels application show generic error messages instead of detailed debugging info?

Generic errors appear when debug settings are disabled. Enable detailed error output by setting `showErrorInformation=true` and `showDebugInformation=true` in config/settings.cfm. This exposes stack traces, variable inspection, and SQL queries to pinpoint root causes quickly.