BayouBill

P.S. Because of what’s contained in .backup_warnings, I have tried excluding the wp-content/themes/responz/themify/ directory and everything beneath it, but that does not help.

Follow-up: This only happens with the 2-column layout on the editor page. The text is running past the right margin of the editing window and “under” the panels that are on the right side of the page when the 2-column layout is used. I’ve discovered that if I widen the browser, the panels in the 2nd column move to the right, giving the editing window more room. If the browser is widened sufficiently, there is enough room in the editing window to show the text without it running past the margins.

But it doesn’t seem that widening the browser should be necessary. Shouldn’t the text be wrapped in the editing window to adjust to its size?

Btw, the problem occurs in every browser I’ve tested: IE, Firefox, Chrome, and Safari, all running on Windows 7.

If you are still looking for a way to do this, you can do it with Localization. See how to do localization at https://docs.woothemes.com/document/woocommerce-localization/

In my case, I wanted to change all variations of the word “ship” to the equivalent variation of “deliver” throughout the plugin, both frontend and backend. I’m based in the U.S., and so is my client and all of their customers, so I used the CodeStyling Localization plugin described in the link to create an English/United States localization file for the WooCommerce plugin and made the substitutions there. Since that is the default locale for my client’s website, all the translations were done without having to change the base locale (which can be done in wp-config.php if necessary) and without having to change or override any of the WooCommerce code files.

If you want me to send you the resulting localization files, let me know.

Yes, step #6 at the quirm link you point to is now documented, but for quite a long time, when many, many people were asking how to solve this problem, there was just one lonely suggestion about that step from a user buried in one of the threads, and nothing from the moderators of the quirm site. That’s why I posted it here.

It would have been possible for the developers to solve the problem another way, and that would have been to move the settings to Column 1 in the 6.2.12 release so people wouldn’t have had to try to figure out how to enable the 2-column display, but that was not done. That was another reason I posted what I did here.

I’m sure you don’t object to eShop users trying to help one another this way, even if they are duplicating your own efforts, right?

I found the problem. After some debugging attempts I had multiple variants of the main class in the plugin’s root folder. Deleting them and going through a cron cycle removed the extraneous listings in the Dashboard. (Sorry if I alarmed you, Paul. <g>)