I agree--many editing issues are not resolved! Spacing, random changing of font size, indentation issues all still plague the process both on website edits and email design.

I just want to add that I have had A LOT of wasted time dealing with quirks in the editor. Not only does the WYSIWYG do funky things, but when I got to the HTML to correct things, that is very unpredictable, too. This is probably one of the biggest frustrations I have with this system and definitely makes it more difficult to make some of the pages and emails more attractive using custom (but not complicated) code.

WA continues to make our communications with members look unprofessional.

I just spent ten minutes reformatting an email to remove a spurious blank line that your text editor insists on reinserting. I had to edit the HTML (which would not let me type in <\p> - I had to copy and paste it) and move <p> and <br>s around.

Users who can't edit raw HTML are just stuck with random paragraph spacings.

I see a suggestion/complaint about "Email Text Formatting" that should be merged with this one, but the author can't vote here because this is marked Resolved.

This issue is NOT resolved. Some things have been improved but it is still an ongoing problem.

Katya, thank you for the explanation.

There are two purposes for the Wishlist. One is for you to gather information. I understand that for this issue it is better to submit that by support request, with full information on how to reproduce the problem.

The other is for your customers to discuss priorities and vote. That need has not gone away.

By declaring this problem "Resolved," you are telling the 275 customers who voted for it that you no longer want to hear how important it is. We are already frustrated and this is not helpful.

Why not open it back up and tell us exactly what information you need us to submit via support requests, so that you can continue to fix bugs as well as assess how important (or not) this issue continues to be to your customers?

And isn't it also useful to know which specific glitches continue to be a concern, even if the customer can't help you reproduce them?

Sharon, Walt, thank you for the feedback. I understand that we didn’t resolve all complaints related to Text editing. But let me explain what we found out during our work on this particular thread and so why we decided to close it. I believe that this helps you and other clients to understand what has happened.

We accumulated tons of comments here. Most of them sound like 'working with content is painful, terrible, buggy....' you name it, and that’s it. It’s really hard to fix problems if you can not formulate it and reproduce it.

So we started our investigation and defined two big problems: working with content in emails (mostly related to layouts and we are working on this already) plus, several painful issues with formatting (like paragraphs spacing, fonts, text selection). We tried to find the balance and fixed some major problems with formatting that we defined and reproduced, not all of them. Then decided to close the thread and collect further comments via the support channel, not here.

Our experience says that all text editing problems depend on browser version, OS and specific content. So in most cases, it is easier to work on them via support request, when users could provide all this information. On Wishlist, we try to accumulate needs, improvements, new features, not bugs.

Sorry for such a long explanation, I hope it was useful.

Katya Tyukina

Oops - because Katya has marked it Resolved. Please fix.

This is still not working properly. Why can't I vote?

Katya, why is this marked Resolved, since there are still issues and you are continuing to work on it?

If anything this batch of "fixes" has made paragraphs and line breaks less functional. A "return" stroke should always start a new <p> tag with the text inside the <p>text</p>. Instead I'm finding that a return results in <p>text<br></p>.

A shift-return should always add a single <br> tag. Instead I'm finding it results in <br>text<br> or in <br><br>text. I can't determine how it decides which to insert, but they're both wrong.

When I want to change from a <br> to a new <p>, and I delete the line break in the text-editor, and then hit return, it places the return after all of the text, instead of where my cursor is located. For illustration:
1
2
3
I place the cursor before 2, hit delete and then return and get this:
12

3

Thank you for working on the text editor! But it is still frustratingly inconsistent with industry standards for what return and shift-return should do.

Fantastic that you have fixed all these bugs.

However - I just went in to edit a member renewal notice and got an extra line. So I deleted the line break entirely using the Del key, hit Enter - and got two blank lines. Plus, the font of the first sentence following the blank lines changed from Verdana to Ariel.

So - improved, yes. Resolved, I'm afraid not.

With apologies for being grumpy - I just spent a bunch of time I didn't have to spare, editing an email, trying to get one font and size. For example, I bolded some text - and it changed the size. The email looked crummy and would not have represented our club well.

Finally after 20 minutes I just copied the whole thing, pasted it into Notepad to remove the formatting, then pasted it back into the email and reformatted.

How much time do your users have to waste before you put one clean, consistent text editor into WA?

Creating text content in WA is painful, slow, and clunky, to say the least.
My suggestion: Bite the Bullet, Contact Microsoft to ask how much $$$ to use MS Word functionality.
If you don't ask, you'll never know! You could be surprised (although I doubt it.) What's WA got to lose? It would be priceless for most of us - YOUR customers. Thanks.

When you highlight text in the e-mail builder to make changes to it, the text stays highlighted so you don't have to keep highlighting it. For example, if I want to change the font size and make the text bold, I have to highlight it once and change the size, then highlight it again to make it bold. It's time consuming and most other software doesn't make you do this, stuff just stays selected until you click off of it.

Editing in email is very difficult. I try and try and even then it isn't right. I have to send multiple test emails to myself to see if the spacing was correct.

I agree with this wishlist item:
1) Fix it so the return key always creates a single new paragraph <p> and never a line break <br>. Only Shift+Return should create a <br>.
2) Keep selection after formatting.
3) Make it so that standard shortcuts of formatting work, e.g. Ctrl+B for bold, Ctrl+I for italic, Ctrl+K for inserting a link.

Editing emails and event descriptions in Wild Apricot is very frustrating because it's unpredictable what spacing and weird HTML WA will try to throw in. For longer emails, I've taken to writing my HTML in Notepad++ and copy/pasting that into the WA HTML editor just to save myself endless frustration with oddball spacing.

The email editor is absolutely the worst aspect of Wild Apricot. I struggle each and every time I have to compose an email blast, which is usually four to six times per month. I can't believe I can't simply paste moderately formatted text out of an email that I've received, or from Word. Every single time, it takes text that is lift justified, and makes it centered. It takes text with Verdana Font and makes it Times New Roman. It takes a bulleted list and sets the lines two inches apart. The email blasts are essential for a membership management application, I can't believe the Wild Apricot system stinks this bad. I've been using it for over two years now, it's not like I'm brand new to the system and haven't tried a few things.

So - my suggestion is improve the email editor so you can paste something into it!

The email formatting is not user friendly. Make it interface with Word.

Could you please elaborate, otherwise it is too broad. What is not good not, what is not working well?

Simplify script editing (formatting and Spell-check)

Becky, I agree this should be considered a bug. (That said, there are a number of issues in text input formatting so the fix might be a lot of work.)

Pasting from Word can be problematic in many applications, not just WA. My workaround is to open Notepad, paste the Word content into it, then copy and paste into the target application.

IOW Notepad is a handy formatting cleaner.