## PHP/JS Errors

Product: Monogram - Personal Portfolio WordPress Theme
URL: https://hub.jkdevstudio.com/docs/monogram/troubleshooting/phpjs-errors
Updated: 2026-08-19

Encountering PHP or JavaScript errors can be frustrating, but they usually point to a specific, fixable problem. This guide walks you through identifying and resolving the most common errors in Monogram.

## Debugging PHP Errors

PHP errors show up as white screens, warning notices, or fatal error messages. To see what's actually going wrong, [enable WordPress debug mode.](https://hub.jkdevstudio.com/docs/monogram/troubleshooting/wp-debug)

### Common PHP Issues

**Memory limit exceeded** You'll see: `Fatal error: Allowed memory size of X bytes exhausted` Fix: Increase `memory_limit` to `256M` in `php.ini` or add to `wp-config.php`:

```php
define('WP_MEMORY_LIMIT', '256M');
```

**Wrong PHP version** Monogram requires **PHP 8.0 or higher**. Check your version at **Tools > Site Health > Info > Server**. Contact your host to upgrade if needed.

**Missing PHP extensions** The theme needs these PHP extensions: `curl`, `gd`, `mbstring`, `xml`, `zip`. Most hosts have them enabled by default. Check **Site Health** for any missing extensions.

## Debugging JavaScript Errors

JavaScript errors cause features to stop working - animations may freeze, sliders won't slide, or page transitions break. The browser console is your best diagnostic tool.

1. Open your site in Chrome, Firefox, or Safari
2. Open DevTools: press **F12** (Windows) or **Cmd+Option+I** (Mac)
3. Click the **Console** tab
4. Look for red error messages - they include the file name and line number

### Common JavaScript Issues

**jQuery conflicts** Some plugins load their own version of jQuery, causing conflicts. Look for errors mentioning `$ is not a function` or `jQuery is not defined`. Try deactivating plugins one by one to find the conflict.

**GSAP version conflicts** Monogram uses GSAP v3.13.0 for animations. If another plugin loads a different GSAP version, animations may break. Check the console for GSAP-related warnings.

**Barba.js page transition conflicts** Plugins that manipulate page navigation (custom link handlers, analytics trackers, popup plugins) can conflict with Barba.js SPA transitions.

To quickly test if Barba.js is the issue, add `?barba_enabled=false` to any URL on your site. If the problem disappears, a plugin is conflicting with page transitions.

<div data-callout="tip">

The URL parameter trick works for any Customizer setting. For example, `?smooth_scroll_enabled=false` or `?grain_enabled=false` to isolate specific features.

</div>

## Quick Isolation Checklist

When you can't pinpoint the cause:

1. Switch to a default WordPress theme (Twenty Twenty-Four) - does the error persist?
2. Deactivate all plugins except the required five - does it work now?
3. Reactivate plugins one at a time to find the conflict
4. Check if the issue appears on a specific page or all pages
5. Test in an incognito/private browser window to rule out browser extensions

<div data-callout="info">

When reporting errors to [support](https://jkdevstudio.ticksy.com/), include the full error message from the debug log or browser console, your PHP version, and a list of active plugins.

</div>