Developer forum

jan@mediestunt.dk wrote:

After updating DW problems appear in the new editor. We host the solution.

 

Ex. Fail to show new liniebreaks. Shift to kodeview and back. Then new liniebreaks is visibale.

 

I have allso problems change font-size to ex xx-small.

 

 

Any ideas.

 

Is there a bug in the new editor?

How do I move on.

It sounds like another kind of error.... We have seen issues where cached versions of the javascript have made the editor disfunction. Try deleting your browsers cache.

Otherwise i would need a link to see what can be wrong.

 

It sounds like another kind of error.... We have seen issues where cached versions of the javascript have made the editor disfunction. Try deleting your browsers cache.

 

Otherwise i would need a link to see what can be wrong.

test.businessdanmark.dk

You can do what you like here. I dont thing it has some thing to do with cache.

I just tested the editor on the solution, and I had no problems. Linebreaks appeared fine when I presset Enter. Did you attempt to empty your cache as suggested by Nicolai?

Please post a screen dump illustrating the problem if it persists after emptying your browser cache. I assume you're running IE?

Sorensen wrote:

I just tested the editor on the solution, and I had no problems. Linebreaks appeared fine when I presset Enter. Did you attempt to empty your cache as suggested by Nicolai?

Please post a screen dump illustrating the problem if it persists after emptying your browser cache. I assume you're running IE?

Yes I am jusing IE 7 and I have cleared all files. And did it again.

Are you open a new page or have you tested on a existing page? You have to stand at the beging of a line and not at the end of the content. 

How can I post a  screen dump? 

Hi Jan

I've logged in to the solution, created a new paragraph and added a line of text, presses enter and the cursor goes to the next line - no problems. Is it the same you are doing?

About xx-small. Your text size defined in stylesheet happens to be the same size as xx-small (10px) - this is probably why you cannot see the difference. But if you place the cursor in a piece of text which has been marked as xx-small you should see the selection in the toolbar.

NP wrote:

Hi Jan

 

I've logged in to the solution, created a new paragraph and added a line of text, presses enter and the cursor goes to the next line - no problems. Is it the same you are doing?

 

About xx-small. Your text size defined in stylesheet happens to be the same size as xx-small (10px) - this is probably why you cannot see the difference. But if you place the cursor in a piece of text which has been marked as xx-small you should see the selection in the toolbar.

Hi

No. I am open an existing page and placing the cursor at the beging of a line, then the linebreak dosent work.

Am I and my clint the only one who has prolem with the editor?

I haven't heard anyone else having this problem. However, it's not "developer" related, so please submit a helpdesk case to our support department, and they'll investigate the problem further.

Hi Jan

OK - had to open quite a few paragraphs to find one that acted as you described, but I found one... PageID 191, paragraphid 579.

The issue is the HTML saved in the database - it looks like this (bold part is important):

Annoncepriser 2008

When you shift to source view the editor will fix this html "error" (thats how it sees it) and changes it to this:

Annoncepriser 2008

So the fuss is regarding empty

tags that the editor does not like.

This is a behaviour of the editor that it seems like we can not control.

NP wrote:

Hi Jan

 

OK - had to open quite a few paragraphs to find one that acted as you described, but I found one... PageID 191, paragraphid 579.

 

The issue is the HTML saved in the database - it looks like this (bold part is important):

 

Annoncepriser 2008

 

 

When you shift to source view the editor will fix this html "error" (thats how it sees it) and changes it to this:

 

Annoncepriser 2008

 

 

So the fuss is regarding empty

tags that the editor does not like.

 

This is a behaviour of the editor that it seems like we can not control.

 

 

 

 

It looks like we are on a track. But i dont think we experinece the same issue. I have the problem on all existing pages. It could be browser thing, the 'error' it not in firefox but appear in IE. I am using IE 7 with all updates and standard settings.