You'll want the perch3_content_items table so your query will look something like
(Code, 4 lines)
It's worth noting that the field ID's are also stored in the itemJSON, so if the text you're replacing contains and ID of one of you're fields it will also…
(Quote from Byron Fitzgerald)
Fantastic, thanks for checking for me!
So would this be the correct statement to run?
SET `itemJSON` = replace(itemJSON, 'Original text', 'Replacement text')
I can't actually see itemJSON…
So from your SQL query it looks like what you are doing is updating the cached HTML, which is why it shows correctly on the front end. In the admin site, perch ignores this so it will be showing the old content.
I think you should be looking to update…
(Quote from Clive Walker)
Thanks for the reply Clive. I am using perch_content. The issue is:
- Content in a region is [a]
- I use SQL to find and replace [a] with [b]
- The front-end of the website now displays [b] in the browser
- In perch, when I click
Byron Fitzgerald 's answer does not apply unfortunately.
If I use an SQL query for example to find and replace content in regions in the database - the front-end site appears fine, however the data in the fields in Regions are not updated. Which means…