ERROR: Rule `content_is_page_with_template` not found.

(@curtisfraser)

Free Version 2.6.5.

Constantly seeing a new log file within uploads directory with content like this. How do I get rid of it?

Content Control Debug Logs:
2025-12-04 09:34:18 – Log file initialized
2025-12-04 09:34:18 – ERROR: Rule content_is_page_with_template not found.
2025-12-04 09:34:18 – ERROR: Rule content_is_page_with_template has no callback.

delete the .log file and another gets created:

Content Control Debug Logs:
2025-12-04 09:39:13 – Log file initialized
2025-12-04 09:39:14 – ERROR: Rule content_is_page_with_template not found.
2025-12-04 09:39:14 – ERROR: Rule content_is_page_with_template has no callback.

The Log Viewer within the Setting for Content Control:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>404 - File or directory not found.</title>
<style type="text/css">
<!--
body{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}
fieldset{padding:0 15px 10px 15px;} 
h1{font-size:2.4em;margin:0;color:#FFF;}
h2{font-size:1.7em;margin:0;color:#CC0000;} 
h3{font-size:1.2em;margin:10px 0 0 0;color:#000000;} 
#header{width:96%;margin:0 0 0 0;padding:6px 2% 6px 2%;font-family:"trebuchet MS", Verdana, sans-serif;color:#FFF;
background-color:#555555;}
#content{margin:0 0 0 2%;position:relative;}
.content-container{background:#FFF;width:96%;margin-top:8px;padding:10px;position:relative;}
-->
</style>
</head>
<body>
<div id="header"><h1>Server Error</h1></div>
<div id="content">
 <div class="content-container"><fieldset>
  <h2>404 - File or directory not found.</h2>
  <h3>The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.</h3>
 </fieldset></div>
</div>
</body>
</html>

Viewing 3 replies - 1 through 3 (of 3 total)

Plugin Support Jamie P.
(@jamiepineda)

5 months, 2 weeks ago
Hi @curtisfraser

We’re sorry to hear about the errors you’re seeing.

That message usually means the plugin is looking for a rule that doesn’t exist or isn’t properly set up, so it doesn’t know what to do with it.

To help narrow this down, could you let us know:
1. Which version of the Content Control plugin are you currently running?
2. Did the error start appearing after a recent update?
3. Does the issue persist if other plugins are disabled?
4. Are you using a custom theme or custom code that handles page templates differently?
5. Have you noticed if the issue happens with an earlier version of Content Control?
You can send us a message here if you wish to share it privately.

We look forward to your reply.
Thread Starter Curtis Fraser
(@curtisfraser)

5 months, 2 weeks ago
1. Version 2.6.5
2. It has been around for a long time. I inherited the site no too long ago
3. I am not that concerned to disable other plugins to check
4. For some pages certainly we have custom templates
5. I am not that concerned to revert to an older version to test this
Log contents on 2025-12-24 has issue from two days prior:
2025-12-22 20:06:52 – ERROR: Rule content_is_page_with_template not found.
2025-12-22 20:06:52 – ERROR: Rule content_is_page_with_template has no callback.

FYI: No code in plugin referencing content_is_page_with_template

If it is not obvious to you where this might be coming from with your plugin, then you can ignore it. It is not causing any display issues that I know of right now.
Plugin Support Jamie P.
(@jamiepineda)

5 months, 2 weeks ago
Hi @curtisfraser

Thanks for your reply.

Please try reverting to an older version of Content Control to test. Make sure to create a backup of your site before testing.

Also, please check for a plugin/theme conflict by following these steps to see if this helps:

Install and activate WordPress’s Health Check & Troubleshooting (https://wordpress.org/plugins/health-check/) plugin, along with the Twenty Twenty-Four or Twenty Twenty-Three theme.

Once the troubleshooting plugin is active, go to your plugins page and click Troubleshooting Mode for our plugin to figure out if a theme or other plugin is interfering with ours.

You’ll also need to turn off any custom code (including custom caching).

Note: The Troubleshooting Mode automatically switches to a WordPress default theme (e.g., Twenty Twenty-Four) and deactivates all the other plugins only for you (your site runs normally for everyone else).

Now, you’re ready to troubleshoot for possible conflicts. Follow these steps:
1. Test for the error. If the error is gone, it’s a good sign that your site’s theme, plugins, or custom code clashes with our plugin. Time to narrow it down!
2. Potential time saver: Check the theme first since that’s quick. Hover over Troubleshooting Mode > Themes in the top admin toolbar and switch back to your main theme.
1. Retest for the error. If you see the error, your main theme is the most likely cause. If not, you can keep the main theme active and move on to the plugins.
2. Activate your other plugins one at a time, constantly testing for the error after you activate each plugin. Keep going until the error comes back. Potential time saver: If you initially saw the error after installing new plugins or updating any existing plugins, activate those first 1-by-1.
3. If you see the error, deactivate the last plugin you activated and retest.
4. If the error disappears again, the last plugin you deactivated is causing a conflict. Make a note and keep it deactivated.
5. Return to step #4 to keep testing for other possible conflicts (do the same for custom code after you finish the plugins).
You should have a list of the conflicting themes, plugins, and custom code you can now share with the appropriate support team.

Let us know how it goes.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.