functions.php Snippet Builder

A WordPress theme's functions.phpruns on every page load, before any template file. It's where you register theme supports, enqueue scripts and styles, and hook into WordPress's action and filter system to change behavior without editing core or plugin files. Think of it as a theme-scoped plugin.

Always use a child theme

Editing the parent theme's functions.php directly means every theme update wipes your changes. Instead, create a child theme — a directory containing a style.css that references the parent in its header and a functions.phpthat enqueues the parent stylesheet. Your snippets live in the child's functions.php and survive updates. For site-wide snippets unrelated to presentation, a small custom plugin or the Code Snippets plugin is usually a cleaner home than the theme.

Hooks: actions vs filters

• add_action()attaches a callback to a named "event" — WordPress calls it at specific points like init, wp_enqueue_scripts, or admin_menu. The callback doesn't return anything meaningful.
• add_filter() attaches a callback that transforms a value. Whatever the callback returns becomes the new value. Example: modifying the excerpt length or the list of allowed upload MIME types.

Safety tips

• Every new snippet should start with a quick sanity check in a staging environment — a fatal error in functions.php can white-screen your site.
• Prefix custom function names (e.g. mysite_disable_comments) so they don't collide with the theme or plugins.
• Keep WP_DEBUG on during development and tailwp-content/debug.log to see warnings early.