Descripción
Find the text. See its source. Review the change.
An old phone number, a company name or a phrase you cannot find in the page editor? FindWeave helps you locate stored text across supported WordPress content and selected theme or plugin files.
See the source of each match, open its WordPress editor or inspect the matching line in a file. For supported content, compare the old and new text before confirming a change. All included tools work without a purchase or licence key.
What you can do with FindWeave
- Find content across WordPress. Search posts, pages, supported public content types, comments, categories, tags and media text, plus selected settings, widgets and non-protected custom fields.
- Locate text in themes and plugins. Search selected folders for text in HTML, TXT, Twig, PHP, JavaScript, CSS and other supported text files. View the matching line and its surrounding text without changing the file.
- Go straight to the source. Open the responsible WordPress editor when available. Use Copy path to copy that editor link or the full server path of a file.
- Narrow your search. Use content filters, case-sensitive or case-insensitive matching, and regular expressions with supported numeric capture references in replacements.
- Review before replacing. Compare before and after values, choose which supported values to include and confirm the change plan. Supported serialized strings and arrays retain their structure.
- Keep a change journal. Review completed changes and prepare a rollback while the journal is retained. Later edits are treated as conflicts rather than overwritten.
- Export findings and supported content. Download matches as CSV, or use the limited content export, domain/prefix tools and confirmed import. Content export is not a database backup or a complete site migration.
- Replace one image. Preview and confirm replacement of a supported local JPEG, PNG or WebP image, with a journal and conflict-checked rollback.
Start with a search
- Open FindWeave in your WordPress dashboard and enter the text you want to find.
- Choose the source. For HTML, TXT or theme text, select Plugin and theme files, then select the relevant plugins or themes.
- Run the search and inspect a match. For supported content changes, enter the replacement text, review the preview and confirm a plan.
Searching and previewing do not change your content. Theme and plugin file matches are read-only. A stored match identifies where text is saved; it does not prove where that text appears on the public website.
Help when you need it
Open FindWeave > Handbook for the bundled German and English guide, including supported sources, limits and WP-CLI commands. The handbook works offline.
Before applying changes to a live site, test on staging and keep an independent backup.
About FindWeave
FindWeave is developed by NovaPlug and licensed under GPL-2.0-or-later.
Capturas
Instalación
- Install FindWeave from the plugin directory, or upload the ZIP through Plugins > Add New > Upload Plugin.
- Activate the plugin and open FindWeave in the dashboard.
- Choose a source and run your first search. No account or licence key is needed.
Requires WordPress 7.0 or later and PHP 8.3 or later. Administrators receive the plugin’s capabilities on activation; access to each source still requires the relevant WordPress permissions. On multisite, activate separately for each subsite. Network activation is not supported.
Preguntas frecuentes
-
Why does my search find pages but not HTML or TXT files?
-
Each search uses the selected source. Website contents searches saved content; Plugin and theme files searches files in the folders you select. To find file text, switch to that source and select the relevant plugin or theme before searching.
-
Can I edit theme or plugin files?
-
No. File matches open a read-only view with line numbers and highlighted context. Copy path copies the full server path so you can locate the file with your hosting tools. For supported WordPress objects it copies the responsible editor link instead. Changed or unavailable files require a new search before their context can be opened.
-
Does FindWeave search everything on my site?
-
No. It searches the supported sources you select, not arbitrary database tables or the rendered website. It excludes protected or unsupported values, credentials, configuration files, backups, binary files and symbolic links. WordPress core, uploads, must-use plugins and drop-ins are not file-search areas. Derived readable HTML/block text and block-theme documents remain read-only.
-
How much can one search check?
-
A run checks up to 10,000 objects or files, 256 MiB and 100 matches. Text files are limited to 1 MiB each; content values to 256 KiB. Content searches return the first match per field. Limits, skipped sources, errors and cancellation are reported; an incomplete search does not prove that there are no further matches.
-
Can I undo a replacement?
-
While its journal is retained, you can prepare and confirm a rollback. A value is restored only if it still matches what FindWeave wrote. Newer changes remain untouched and are reported as conflicts. Rollback is not a substitute for a backup.
-
Is content export a full backup or migration?
-
No. It covers posts/pages with ID, title and content, allowed custom fields and selected settings/widgets. Imports update existing values on the bound site through a confirmed plan; they do not recreate a website or execute uploaded SQL. Users, credentials and third-party configurations are excluded.
-
What data is stored, and for how long?
-
Working data stays in the plugin’s tables on your site:
- Search runs: search text, progress, excerpts and source references; retained for 60 minutes, with at most five runs per user.
- Change plans: pending drafts expire after 30 minutes. Completed plans retain their before/after journal for seven days after the last change, with at most ten plans per user.
- Image replacements: local image snapshots are retained with the journal.
Search data and journals can contain personal information from your content. Access is permission-checked. Exports are downloaded to your browser, not stored as server export files. You can delete working data earlier; deleting a journal also removes its rollback. Absolute server paths are shown in authorised file views, not saved in search logs.
-
What happens when I deactivate or delete FindWeave?
-
Deactivation stops running searches and open plans; content stays unchanged. Deleting the plugin removes its tables, working data and assigned capabilities, including across existing subsites. Previously changed content stays in place. Historical file-change journals follow normal retention, but their plans cannot write files or roll them back in this edition.
Reseñas
No hay reseñas para este plugin.
Colaboradores y desarrolladores
Este software es de código abierto. Las siguientes personas han contribuido a este plugin.
Colaboradores
Traduce “FindWeave” a tu idioma.
¿Interesado en el desarrollo?
Revisa el código, echa un vistazo al repositorio SVN o suscríbete al registro de desarrollo por RSS.
Registro de cambios
1.1.2
- Remove the distribution SDK and automatic service initialization from the free plugin; local tools and explicit checkout links remain available.
1.1.1
- Preserve native HTML sanitization and current permissions when changing widgets and supported options, including imports and rollbacks.
- Enforce current field-specific permissions for custom-field searches, changes, exports and stored results.
- Require verified HTTPS for the distribution service and package downloads, including redirects.
- Keep theme customization values read-only when their native validation cannot be safely reproduced.
1.1.0
- Add read-only file locations with highlighted lines and full server paths; remove general file editing.
- Expand content sources, filters and supported changes, including comments, categories and media text.
- Add readable HTML/block-text search, regex capture replacements, value selection and CSV export.
- Add per-subsite operation, core WP-CLI workflows and controlled single-image replacement.
- Give tools their own menu areas and place the plan list before plan details.
- Clarify supported sources, limits and data handling in the directory description.
1.0.2
- Correct the earlier provider-generated distribution packages.
1.0.1
- Prepare an updated provider distribution package.
1.0.0
- Introduce text search, change previews, confirmed plans, journals and conflict-checked rollback.
- Include the local handbook, limited content export/import and optional external checkout links.