Nov 24, 2010
visibility 4890
star star star star star
(2 votes)

EPiServer Search and Replace Plug-in v1.1 Released

About a month ago I released version 1.0 of the search and replace plug-in I have built for EPiServer 6 and onwards.

For those of you who have not taken a look at the plug-in yet, basically it allows a user to search and replace content within a site.  Replaced content is not automatically published, new versions of the pages are created and it is down to some business rules and user interactivity to force the approval/rollback of modified pages.  The previous version of the plug-in would only update page properties and dynamic content (if this option was enabled in the config).

The plug-in is perfectly safe for updating WYSIWYG and xml serialized properties.  The code will determine whether the string being updated is of a xml format and will then use an SGML reader to parse the mark-up and then will update attribute values and text node contents.

Specific page types and property names can be excluded from the search and replace by updating the SearchAndReplace.config file.

New features added to v1.1:

- Dynamic content will now be searched and replaced by the plug-in.

- A new version of a page is created in the version history when a page has been updated.

- Some UI and logic enhancements have been made.

Give it a try!

Please feel free to download the plug-in and give it a try.  Any feedback good or bad will be greatly received.

To install it is as simple as copying an assembly to your bin folder and adding some configuration settings to your web.config.

The assemblies and source code if required can be found here

Installation/Usage instructions can be found here.

Nov 24, 2010

Comments

error Please login to comment.
Latest blogs
Finding Thomas Part 3 - The Moment of Recognition

Remember Thomas? In digital landscape, Thomas is the returning visitor who reads everything, opens every email, converts on nothing. In standard...

Ritu Madan | Jun 26, 2026

Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |

Understanding Optimizely Graph: Caching, Webhooks & Avoiding Stale Content (Optimizely SaaS CMS)

📌 Scope: This post covers Optimizely CMS (SaaS) only — using the official @optimizely/cms-sdk and @optimizely/cms-cli packages with Next.js 15. If...

Kiran Patil | Jun 23, 2026 |