Title: Headless mode bug
Last modified: November 13, 2022

---

# Headless mode bug

 *  Resolved [PD](https://wordpress.org/support/users/peterdowney01/)
 * (@peterdowney01)
 * [3 years, 6 months ago](https://wordpress.org/support/topic/headless-mode-bug/)
 * I noticed on one of my servers that the SEO section had totally disappeared. 
   After server restart, clearing object cache and opcache, nothing brought it back.
   I realized that this server was different than the rest as the site on it had
   define( ‘THE_SEO_FRAMEWORK_HEADLESS’, **false **); added to the wp-config.php
   file. I commented out that section and everything returned to normal. This, however,
   should not happen, as headless mode should only be triggered by the value of **
   true**.

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

 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [3 years, 6 months ago](https://wordpress.org/support/topic/headless-mode-bug/#post-16193999)
 * Howdy!
 * The constant accepts `true` or an array with specifics; it does not accept false
   or any other data type: anything that isn’t the specific array is read as `true`.
   So, if you wish to disable it, it’s best to leave the constant undefined. Please
   see [https://tsf.fyi/kb/headless](https://tsf.fyi/kb/headless). [Here’s the source](https://github.com/sybrew/the-seo-framework/blob/324a3cc3a61fbdb2fde71edf7208e906bb679d63/inc/classes/load.class.php#L126-L138).
 * We should not add a defense clause for everything developers could push through
   our API; every clause makes a function up to 17% slower. We would also need to
   write out why a developer is [“doing it wrong”](https://developer.wordpress.org/reference/functions/_doing_it_wrong/),
   considering every error one could make. Still, we didn’t create a programming
   language, only a framework for SEO. So, instead, we expect exclusively what we
   lay out in our documentation. You can read my reasoning in vast detail within
   this ticket: [https://core.trac.wordpress.org/ticket/49628#comment:23](https://core.trac.wordpress.org/ticket/49628#comment:23).
 *  Thread Starter [PD](https://wordpress.org/support/users/peterdowney01/)
 * (@peterdowney01)
 * [3 years, 6 months ago](https://wordpress.org/support/topic/headless-mode-bug/#post-16194037)
 * Thank you for your reply.
 * I supposed I just read your site wrong when I originally found this setting. 
   I entered the value based on this description on your site:
 * > Different modes
   > The constant THE_SEO_FRAMEWORK_HEADLESS accepts boolean values **(true/false)**
   > as well as array values.
 * To me, reading that that suggests false is a valid option. I understand now that
   it isn’t, but specifically saying in your help text that it accepts this type
   of value and then listing one it doesn’t accept can be confusing to read.
 *  Plugin Author [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * (@cybr)
 * [3 years, 6 months ago](https://wordpress.org/support/topic/headless-mode-bug/#post-16197634)
 * Ah! I am entirely to blame for spreading conflicting information. Sorry about
   that.
 * I have adjusted the KB entry to reflect the code’s intention more accurately.

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

The topic ‘Headless mode bug’ is closed to new replies.

 * ![](https://ps.w.org/autodescription/assets/icon.svg?rev=3000376)
 * [The SEO Framework – Fast, Automated, Effortless.](https://wordpress.org/plugins/autodescription/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/autodescription/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/autodescription/)
 * [Active Topics](https://wordpress.org/support/plugin/autodescription/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/autodescription/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/autodescription/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [Sybre Waaijer](https://wordpress.org/support/users/cybr/)
 * Last activity: [3 years, 6 months ago](https://wordpress.org/support/topic/headless-mode-bug/#post-16197634)
 * Status: resolved