11
Vote

Formatting is broken, edit not working

description

With the new release, if I click edit to edit my existing post, the formatting is lost, it just makes it one long line, no formatting, no line breaks nothing.

Can you please revert to the old editor, it worked perfectly!

comments

rboy1 wrote Jan 31 at 2:29 AM

This new box editing box is terrible, not only does it not work - it's lacking the nice features the old editor had including editing the HTML as well code snippest in a GUI friendly manner, this is more manual and doesn't work half as well.

Please REVERT it back

TomCornelius wrote Jan 31 at 3:23 AM

It's due to the switch over to markdown. If you edit a post that was created before the switch you may need to reformat it before you save, because of the conversion from html to markdown. Editing posts created after today will stay maintain their original format.

Please do continue to use it and give us more feedback!

rboy1 wrote Jan 31 at 4:46 AM

Sorry to keep spamming, but I REALLY miss the old word style editor, Ctrl B, Ctrl I instead of this mark up crap.

Why did you change it? WYSIWYG is so much better and more intuitive than mark up stuff. I thought the idea was to make life easier and not worry about what dot and dash I need to put where and compare the results.

I'm pretty sure some geek came up with this idea of how flexible it is to have mark up language, guys come on learn something from Apple. Geeks are out, simple and easy to use are IN!

rboy1 wrote Jan 31 at 4:55 AM

That's a very bad implementation I'm sorry to say. I've written pages and page of documentation for users and now I"m stuck. I don't know to edit it, the moment I try to edit the pages to update the documentation adn instruction I get garbled text/markup language.

Basically a total waste of time me, either I start a brand new page or I just don't update it.

AT THE LEAST, it should be compatible with the old format. This like the days of WinME and WINNT. Tom, request you guys to please relook at your editor strategy, it's seriously flawed.

rboy1 wrote Jan 31 at 5:09 AM

BTW since you're asking for feedback (not to sound like a rant) but one of the reasons I moved from sourceforge to codeplex was you super friendly word sytle editor unlike the crappy sourceforge markup stuff. :-)

rboy1 wrote Feb 5 at 5:23 AM

This really sucks!
  1. I can't put characters like * and _ in the discussion threads, this is a CODING website, we need a way to put special character
  2. The formatting broken, I click Bold and it inserts a __ before and after, when I click save/preview, nothing - I get a __ no bolds.

rboy1 wrote Feb 5 at 5:30 AM

Look at this page. the formatting isn't working.


https://mcebuddy2x.codeplex.com/discussions/429106

TomCornelius wrote Feb 5 at 6:23 PM

Try including the period inside the __
If there's a character immediately following the underscore it assumes that bold is not intended.

Also, you can use backslash to escape special characters (like * and _).

rboy1 wrote Feb 5 at 8:03 PM

tried it didn't work..

rboy1 wrote Feb 5 at 8:04 PM

what about the link I had posted, why isn't that page working?

TomCornelius wrote Feb 6 at 8:12 PM

As I said, the period needs to be inside the __

So this:
To participate in the EARLY ACCESS PREMIUM program you will need to donate atleast $15 (one time) to MCEBuddy.

Should be this:
__To participate in the EARLY ACCESS PREMIUM program you will need to donate atleast $15 (one time) to MCEBuddy.__

And it will look like this:
To participate in the EARLY ACCESS PREMIUM program you will need to donate atleast $15 (one time) to MCEBuddy.

rboy1 wrote Feb 6 at 8:58 PM

Think you missed the point. I want the sentence to be bold instead it's showing me underscores.

TomCornelius wrote Feb 6 at 10:18 PM

Which sentence? Post it in this comment. :)

I'm saying include the period inside the underscores and it will be bolded.

To participate in the EARLY ACCESS PREMIUM program you will need to donate atleast $15 (one time) to MCEBuddy.

rboy1 wrote Feb 6 at 11:24 PM

Okay yes it's working now. Without sounding like a bashing session, you see that's anohter point I was making, why the . inside? it's not intuitive or easy - too many conditions. Why not just go back to a WYSIWYG editor and at the BACKEND change it to this markup language. Essentially to the user it should be a easy interface.

TomCornelius wrote Feb 27 at 9:44 PM

Thanks for the feedback. In today's deployment we updated the feature so you can use punctuation outside of the underscore.

Sign in to add a comment or to set email notifications