I've upgraded to 4.2.4 and decided to sort out my Places hierarchy, so I've been using Search and Replace.
If you're only doing one, I suppose it's fine. If you're doing a series of fixes you can get in a mess.
The Search and Replace action is triggered/submitted whenever you move out of either the "Search text/pattern:" field or the "Replacement text:" field. First time, that's fine. Second time, the "Replacement text:" already contains the entry from the first use, so if you enter the second search text and go to fill in the second replace text, off it goes and prepares to replace the second search text with the first replace text. You can ignore the new pane that loads and not do those changes, but it disrupts the flow and can take time.
Is this how it is supposed to work?
My trick is to fill in the replace field first. You just did a replace on the text still in the search field, so unless it's a special case, nothing is found and workflow isn't interrupted. Then put the new search text in and off it goes as expected.
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
f you're doing a series of fixes you can get in a mess.
I'm assuming you are using the admin batch function - Search and Replace, and not the SEARCH feature. I would not recommend every using the SEARCH feature.
Yes, on the batch search and replace function, the action is first initiated after entering text in the FIND field and exiting (usually a tab to the replace field). Typically, after doing so, I simply hit Command-Period (if on a PC, use the equivalent to stop the browser action) and then enter the REPLACE text into the second field. As nothing is changed until you approve the UPDATE or UPDATE ALL buttons, I'm not sure how you could "get in a mess". -Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've upgraded to 4.2.4 and decided to sort out my Places hierarchy, so I've been using Search and Replace.
If you're only doing one, I suppose it's fine. If you're doing a series of fixes you can get in a mess.
The Search and Replace action is triggered/submitted whenever you move out of either the "Search text/pattern:" field or the "Replacement text:" field. First time, that's fine. Second time, the "Replacement text:" already contains the entry from the first use, so if you enter the second search text and go to fill in the second replace text, off it goes and prepares to replace the second search text with the first replace text. You can ignore the new pane that loads and not do those changes, but it disrupts the flow and can take time.
Is this how it is supposed to work?
My trick is to fill in the replace field first. You just did a replace on the text still in the search field, so unless it's a special case, nothing is found and workflow isn't interrupted. Then put the new search text in and off it goes as expected.
David
David
I'm assuming you are using the admin batch function - Search and Replace, and not the SEARCH feature. I would not recommend every using the SEARCH feature.
Yes, on the batch search and replace function, the action is first initiated after entering text in the FIND field and exiting (usually a tab to the replace field). Typically, after doing so, I simply hit Command-Period (if on a PC, use the equivalent to stop the browser action) and then enter the REPLACE text into the second field. As nothing is changed until you approve the UPDATE or UPDATE ALL buttons, I'm not sure how you could "get in a mess".
-Stephen