Semantic-Org/Semantic-UI · info

The method you called is not defined.

Error message

The method you called is not defined.

What it means

Declared in search.js settings.error.method but the module's invoke() (search.js:1138-1172) does NOT call module.error on a failed lookup — it just returns false (lines 1169-1171). So this string is never emitted by search.js. Compare with sidebar/progress/dimmer whose invoke() does log error.method. In search, calling an unknown method simply fails silently.

Source

Thrown at src/definitions/modules/search.js:1307

    active    : 'active',
    empty     : 'empty',
    focus     : 'focus',
    hidden    : 'hidden',
    loading   : 'loading',
    results   : 'results',
    pressed   : 'down'
  },

  error : {
    source          : 'Cannot search. No source used, and Semantic API module was not included',
    noResults       : 'Your search returned no results',
    logging         : 'Error in debug logging, exiting.',
    noEndpoint      : 'No search endpoint was specified',
    noTemplate      : 'A valid template name was not specified.',
    oldSearchSyntax : 'searchFullText setting has been renamed fullTextSearch for consistency, please adjust your settings.',
    serverError     : 'There was an issue querying the server.',
    maxResults      : 'Results must be an array to use maxResults setting',
    method          : 'The method you called is not defined.'
  },

  metadata: {
    cache   : 'cache',
    results : 'results',
    result  : 'result'
  },

  regExp: {
    escape     : /[\-\[\]\/\{\}\(\)\*\+\?\.\\\^\$\|]/g,
    beginsWith : '(?:\s|^)'
  },

  // maps api response attributes to internal representation
  fields: {
    categories      : 'results',     // array of categories (category view)
    categoryName    : 'name',        // name of category (category view)
    categoryResults : 'results',     // array of results (category view)

View on GitHub (pinned to 597843ab84)

Solutions

1. No fix is required for the message itself; instead debug the silent failure by checking the return value of the method call.
2. Verify method names against the documented search behaviors ('set disabled', 'show results', 'hide results', 'search local', 'read cache', etc.).
3. If you want such calls flagged, wrap invoke's else branch in a fork to log error.method.

// Search invoke is silent on unknown methods; assert the name yourself
var known = ['set disabled','set value','show results','hide results','search local','read cache','set focus','get result','get results'];
if (known.indexOf(methodName) === -1) console.warn('Unknown search method:', methodName);

When it happens

Trigger: No active path in search.js emits it. The conceptual trigger — calling $('.ui.search').search('bogusMethod') — yields no console output in this module because invoke returns false without logging.

Common situations: Seeing the string while inspecting settings and assuming search logged it; migrating from a fork where invoke was patched to log it; confusion with other modules that do throw error.method.

Related errors

• Error in debug logging, exiting.
• The method you called is not defined.
• The method you called is not defined.
• The method you called is not defined
• The method you called is not defined.

AI-assisted analysis of Semantic-Org/Semantic-UI@597843ab84 (2026-08-13). Data as JSON: /api/errors/655205bbf858d717. Report an issue: GitHub.