WYSIWYG editor screen too wide

Found a bug? Tell us!!
Post Reply
plofhead
Regular
Posts: 45
Joined: Fri Jun 23, 2006 9:01 am
Location: Netherlands
Contact:

WYSIWYG editor screen too wide

Post by plofhead »

Hi,

Since I upgraded from v1.0.2 to v1.1 the WYSIWYG editor screen is much too wide.
When creating a new entry from the administration everything seems to be as usual, but after clicking on the preview or save button the screen suddenly gets much wider than the window its dispayed in. I have to scroll from left to right to edit my text.
The editor seems to work normally for the rest, but editing in a window wider than can be displayed is quite annoying.

Regards,
Bert
To bee or not to bee, that is the question
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Re: WYSIWYG editor screen too wide

Post by garvinhicking »

Hi!

The preview will lead to your frontpage being parsed, and a javascript determines the width of it.

Can you check which element pushes the content of the entry display outside? Is it part of the layout that is pushing the boundaries, or is it maybe the text you enter?

Which template are you using? Does it happen also if you choose a different template like Serendipity 3.0 ?

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
plofhead
Regular
Posts: 45
Joined: Fri Jun 23, 2006 9:01 am
Location: Netherlands
Contact:

Post by plofhead »

Hi,

The editors screen being to wide is only visible in the Serendipity Administration part. It doesn't have anything to do with the template I'm using. In the blog itself the entry is displayed as it should.
When editing an existing entry in the administration the screen is too wide. Even when I make the window maximum size there's still a horizontal scrollbar visible. See picture.

Image

I have to scroll to the right to be able to use the preview or submit buttons.

Hope this helps.

Regards,
Bert
To bee or not to bee, that is the question
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Post by garvinhicking »

Hi!

The content display of the WYSIWYG editor is in fact dependant on the template, as it uses the CSS of the active template.

Can you please try to see what happens if you switch your theme to serendipity 3.0?

Best regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
plofhead
Regular
Posts: 45
Joined: Fri Jun 23, 2006 9:01 am
Location: Netherlands
Contact:

Post by plofhead »

Hi Garvin,

I just tried the Serendipity 3.0 template. The WYSIWIG editor is still too wide. So no changes.

Regards,
Bert
To bee or not to bee, that is the question
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Post by garvinhicking »

Hi!

Could it be that at the end of that page some plugin is responsible for the wide content? Or maybe some extra long category name?

The WYSIWYG editor panel should simply have 100% width, and if something else above or below pushes the boundaries, that would make the area too wide...?

HTH,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
plofhead
Regular
Posts: 45
Joined: Fri Jun 23, 2006 9:01 am
Location: Netherlands
Contact:

Post by plofhead »

Hi Garvin,

I found out that my entries before the update to v1.1 didn't have the editor problem. So I had a look at the way the pictures were handled.
It seems that the problem occurs when the 'Target for this link' option 'popup window (Javascript, adaptive size)' is choosen.
This was introduced in v1.1 so I didn't know exactly what it ment. I now choose 'none'. Now my problems are gone.

Thanks for your help,
Bert
To bee or not to bee, that is the question
Post Reply