String locator


When working on themes and plugins you often notice a piece of text that appears hardcoded into the files, you need to modify it, but you don’t know what theme or plugin it’s in, and certainly not which individual file to look in.

Easily search through your themes, plugins or even WordPress core and be presented with a list of files, the matched text and what line of the file matched your search.
You can then quickly make edits directly in your browser by clicking the link from the search results.

By default a consistency check is performed when making edits to files, this will look for inconsistencies with braces, brackets and parenthesis that are often accidentally left in.
This drastically reduces the risk of breaking your site when making edits, but is in no way an absolute guarantee.


  • Searching through the Twenty Fourteen theme for the string 'not found'
  • Having clicked the link for one of the results and being taken to the editor in the browser
  • Smart-Scan has detected an inconsistency in the use of braces

Vanlege spm.

Will Smart-Scan guarantee my site is safe when making edits?

Although it will do it’s best at detecting incorrect usage of the commonly used symbols (parenthesis, brackets and braces), there is no guarantee every possible error is detected. The best safe guard is to keep consistent backups of your site (even when not making edits).

As of version 1.6, the plugin will check your site health after performing an edit. If the site is returning a site breaking error code, we’ll revert to the previous version of the file.

My search is failing and I am told that my search is an invalid pattern

This error is only related to regex searches, and is based off how PHP reads your regex string.

When writing your search string, make sure to wrap your search in forward slashes (/), directly followed by any modifiers like case insensitive (i) that you may want to use.


13. juli 2019
I don't know how many weeks I spent trying to find a single line of code just to change two letters in my blog, but was never able to find them. With string locator I finally took care of it.
25. juni 2019
Em segundos ele achou o arquivo com o código que eu queria, já abriu o arquivo na linha do código procurado e editei nele mesmo! Excelente! Parabéns!
6. juni 2019
Working perfectly. Thank you for this great solution as it save a lot of my time.
15. mai 2019
I wouldn't advise using this plugin. I used it to search for a code in my WordPress directory, and it crashed my entire website. To the point where I nearly lost everything and my server host had to install one of the automatic backups we created the night before. If we hadn't had that backup all would be lost (15+ years of work). It injected 115 MB of data instantaneously into my tables. I have the proof in phpMYadmin. DO NOT USE – unless you hate your website of course.
Les alle 73 omtalar

Bidragsytarar og utviklarar

“String locator” is open source software. The following people have contributed to this plugin.


“String locator” er omsett til 6 språk. Takk til omsetjarane for bidraga deira.

Omset “String locator” til ditt eige språk.

Interested in development?

Les kjeldekoden, sjekk SVN-lageret eller abonner på utviklingsloggen med RSS.



This is a maintenance and security release, with thanks to RIPS Technologies for the responsible disclosure of several security concerns.

  • Fixed an escaped URL that should’ve allowed some HTML links.
  • Patched a potential security vulnerability with file path traversals.
  • Patched a potential security vulnerability that allowed writing to arbitrary files.
  • Patched a few Cross Site Scripting (XSS) vulnerabilities.
  • Removed unused code that might allow file creation.


  • Upped version requirement to 4.9 as we now use the bundled CodeMirror in WordPress core.
  • Converted translation functions to the escaping versions to avoid accidental output from translations.
  • Removed bundled languages, these should be served by now.
  • Improved behavior when a search failure happens, we were accidentally looping error messages for every file (whoops).
  • Added more translatable strings.
  • Added various filters:
    ** string_locator_bad_http_codes
    ** string_locator_bad_file_types

Older entries

See changelog.txt for the version history