Editing of profile. Why does it keep messing up?

[Morningside]

Quick edit and you get
<div>
profile text
profile text
</div>

and smilies turn into <img src="/inc/images/smile.gif" alt="smile"> instead of

So after a quick edit you need to re-edit all the formatting text out otherwise it looks even worse.

I also see that other peoples profiles are also showing the same symptoms.

[Mattt]

I asked a while ago, and "it was being looked at".

[Mr Will]

The current version of the parser only works in one direction, so once your profile has been turned into html it cannot be turned back into forum code the next time you edit it.

Building a new version of the parser which will do this (and quite a few other things) is on the to-do list, but unfortunately it is a very big job to build and test so it is likely to be a while before it gets done.

[Morningside]

But I am sure that it used to work ok. Or is this after the last massive re-write.

[Mr Will]

Morningside said:

But I am sure that it used to work ok. Or is this after the last massive re-write.

It was a minor tweak which broke it, so now it is a big job to put right properly (rather than bodging things and making it worse in the long run)

[miniman]

Mr Will said:

The current version of the parser only works in one direction, so once your profile has been turned into html it cannot be turned back into forum code the next time you edit it.

Building a new version of the parser which will do this (and quite a few other things) is on the to-do list, but unfortunately it is a very big job to build and test so it is likely to be a while before it gets done.

Why do you need to build a new version of the parser? Surely you can use the one that the forums use??

[Mr Will]

miniman said:

Mr Will said:

The current version of the parser only works in one direction, so once your profile has been turned into html it cannot be turned back into forum code the next time you edit it.

Building a new version of the parser which will do this (and quite a few other things) is on the to-do list, but unfortunately it is a very big job to build and test so it is likely to be a while before it gets done.

Why do you need to build a new version of the parser? Surely you can use the one that the forums use??

The forums don't have a reverse parser either, they just store an unparsed version for editing/quoting

[miniman]

Mr Will said:

miniman said:

Mr Will said:

The current version of the parser only works in one direction, so once your profile has been turned into html it cannot be turned back into forum code the next time you edit it.

Building a new version of the parser which will do this (and quite a few other things) is on the to-do list, but unfortunately it is a very big job to build and test so it is likely to be a while before it gets done.

Why do you need to build a new version of the parser? Surely you can use the one that the forums use??

The forums don't have a reverse parser either, they just store an unparsed version for editing/quoting

Interesting conundrem then, I guess - what will load the servers up more, storing the profile contents raw for editing purposes (more database contents but not a vast amount more load in the grand scheme of things, I'm thinking one more insert per transaction and a bit of disk space) versus webserver processing cycles to reverse-parse the stored HTML? Personally I would go for storing the un-parsed version of the content because at least each time you tweak the parser you only have to do it once, rather than having to also adjust the un-parser.

[RacingPete]

There are several areas of the site, some not overly used, where a reverse parser would be of use too so I currently have a project just starting to fix this. Also it can be used to handle some other little niggles we have on the site, so hopefully this will be built and fully tested by beginning of next month.