Fix for preview post -> real post.

[HenrikOlsson]

Yes, but it should not do that. It should display the textbox/codewindow exactly as it's displayed in the preview. It should not break any lines - if the textbox isn't wide enough (because the window is too small or the line is too long) it should show the box with a horisontal scrollbar - like it does in the preview.

[lester]

Henrik, i looked into this. Its beyond the resource i have.

I fear that many changes that seem trivial, are often quite complex, the forum is a massive system with much interracting code and the requirement to preserve the structure so that updates are unaffected.

I see no similar request from other forum owners, so there seems to be no demand on the core developers to improve this feature,

I'm sorry, but, It fair to say that its not going to happen anytime soon, sorry.

[lester]

I'd be happy to have any volunteer(s) that wants to join the admin / moderator group and take this on a as a project.

We have a development system that can be sued as a test bed for core code chnages.

Its no small task.

[HenrikOlsson]

Hi Lester,
Fair enough, if none of the other forum owners you mention thinks it's a problem then OK. Have you tried it, do you get the same results as I do?

It just seems wrong that a preview window doesn't show what you'll actually get - it kind of defeats its purpose altogether.

I'm afraid I have zero know-how when it comes to these kinds of systems so I'm afraid I'll just destroy the thing if I went at it.

/Henrik.

[mister_e]

I could be wrong but it isn't a vBulletin issue? How about asking/report to them directly?

[lester]

Yes, its vBulletin functionality, but i don't see its a BUG, its just a requirement to change the way the way it works.

We've been using vBulletin for many years now, nothing has changed to my knowledge.

I use the preview, yes, but this issue has not affected my posts since they are mainly text.

I know that the editor can produce some strange results when you try to hard format text in articles. But i work around it.

I'll drill through the bug reports and development requests on the vbulletin support site to see if there is any other mention of this or a proposed solution.

It maybe that there is some way to use a different editor. In Joomla we can install enhanced editors to resolve issues, but in VBulletin i've not seen this.