Search options (Page 87 of 119)

If you are just using the styles that came with PunBB 1.1.5 or earlier then you will have to edit each of the five stylesheets.

If you want to test the layout in IE without all those long error messages getting in the way  try DIV.box {OVERFLOW: hidden} which hopefully should chop them off.

Does anybody have a YOUTH => OLD FART translator. I have no idea what that means.

PunBB 1.2 works like that automatically with messages and could be made to crop subjects as well. It is trickier for PunBB 1.1.5 because tables have trouble with overflow:hidden but I will give it some thought.

The answer generally is to put the subject in a div then in the stylesheet give it a fixed width and set overflow to hidden.

Were you entering the meta tag stuff in Russian. Maybe that makes a difference. All I see when I view you meta tags as source is a bunch of nonesense characters.

Your tags do not appear to be closed properly either.

Try adding this to your stylesheet

TEXTAREA {WIDTH: 400px} adjusting the width to suit.

If that doesn't work then you will have to adjust the cols= settings for the textareas in viewtopic.php, post.php and edit.php.

Maybe he means using DW or some other WYSIAWYG app.

I don't think there is a copy on public view but that is the only change which is relevant to what you are doing.

PunBB 1.2 doesn't use graphics for new posts. There is a div which provides the new post indicator. If there are new posts it has class="inew" otherwise it is class="inormal". Could you adapt your idea just to switch the classes?

BTW: I think I came up with something similar many moons ago, I will try to find it.

EDIT:

Here it is, not the same as your idea but similar thought process at work.
http://punbb.org/forums/viewtopic.php?id=4338&p=1

See the post by zodiki above yours on the same page and my answer.

andor: Thanks for the report. Since Firefox 1.0 has been released any versions prior to that are not supported on the basis they were just beta's. The css for forms has also been altered slightly since the beta was released and I can't duplicate the error with Firefox 1.0 so consider it fixed.