276

(26 replies, posted in General discussion)

Try closing the meta tag on line 4 properly i.e. put a space before the /
In fact, do the same for all the other self closing tags.

Moved to modifications. quaker, thats not what he was asking.

Is there are referrer check here somewhere that gets screwed by the ebay stuff?

279

(10 replies, posted in PunBB 1.2 troubleshooting)

If you want to sort it easily rather than using complicated and slightly flakey css do it like this

1. Open main.tpl and add an extra wrapping div between #punwrap and .pun. Give it an id of pun-inner.

2. Put your top graphic on #punwrap. Give punwrap top padding of 30px. Position the grapic top left with no-repeat.

3. Put your bottom graphic on the new div #pun-inner with a background position of bottom left and no-repeat. Give the div bottom padding of 30px.

4. Put you side graphic bg.gif on .pun with repeat-y. Reduce the top padding on .pun to 5px.

Your problem is that you currently have the top and bottom graphics nested inside the background graphic which is the wrong order. The above puts everything into a more manageable order.

280

(10 replies, posted in PunBB 1.2 troubleshooting)

You can set the top position of a background image in pixels or percent e.g. if you set the top position as 10px then it will start 10px from the top of the containing box. Take a look here
http://www.w3schools.com/css/pr_background-position.asp

281

(5 replies, posted in PunBB 1.2 troubleshooting)

I already answered you.

282

(8 replies, posted in PunBB 1.2 troubleshooting)

Geoffrey wrote:
sirena wrote:

Why is this 'VERY urgent' and the post subject marked 'URGENT:' ?

You make it seem like life and death, rather than a simple matter of web page layout, involving a delay of perhaps 30 minutes while you figured out how to get your AdSense ad aligned.

Why cry wolf about it.

It doesn't concern you, so simply keep out of it...

But it does concern me and Sirena was right. Topic edited.

You actually provided the solution yourself. You just copy what they did on the example site you linked to. Float the banner right, give it position: relative and then nudge it into position with a negative top margin.

283

(5 replies, posted in PunBB 1.2 troubleshooting)

How would we know, you haven't given us a link to your forum.

If you mean the Unit Clan site then the answer is yes. The reason being you didn't follow the instructions properly for adjusting the font size. You have left the font size for IE6 at 68.75%. Since your style.css sets a font size for body of 12px your are getting 68.75% of 12px which is 8.25px. Just delete the IE6 font size alltogether. Its not serving any useful purpose since you have crippled text resizing by setting the body font size in pixels.

284

(1 replies, posted in PunBB 1.2 discussion)

Tricky. You could try .postmsg img {float:left, position:relative; right: 16px; margin-left: -16px} but I suspect it won't work very well. You would also have to reverse it for non smilie images in posts.

285

(12 replies, posted in PunBB 1.2 troubleshooting)

Exactly, its the TOS or the AUP of the web host/ISP who is hosting the site that is relevant. If the site is not hosted by a hosting company/ISP e.g. they have dedicated servers then the place to go is the server provider because they will have TOS/AUP regarding use of their servers. If they are running their site from a bedroom server then it would be the ISP who is providing the internet connection.

Complaining to us about a particular use PunBB is put to is like complaining to  Microsoft if somebody writes a defamatory letter on MS Word.

286

(12 replies, posted in PunBB 1.2 troubleshooting)

No there isn't. All that is necessary is that you comply with the GPL licence.

287

(7 replies, posted in PunBB 1.2 troubleshooting)

Much easier just to float the forums wrapping div which will trap the clearing behaviour within it.
http://punbb.org/forums/viewtopic.php?id=7781

orlandu63 wrote:

If you're not going to use the 'application/xhtml+xml' header, why bother with XHTML?
Also, it seems that   is not a valid entity anymore.

http://www.hixie.ch/advocacy/xhtml

1. Because I don't agree with Hickson.

2. So future versions can be made fully vailid (e.g. replace offending entity references with numeric references) and served as application/xhtml+xml with the addition of a very simple content negotiation script for IE. If it was written in html anybody who actually had a need for xml would be screwed.

3. I find it easier to use xhtml particularly when it comes to error checking. The xml error messages in Opera are very good, much more helpful than the validator so serving the page as application/xhtml+xml is a good way of debugging. You find all sorts of little errors which the validator doesn't show.

And before anybody asks, yes, 1.3 does have a supported content negotiation extension.

Personally I hope the future is xml/xslt, that would remove most of the processing needed for conditional formatting from php or whatever language you are using and make a much cleaner seperation between the backend and frontend of an applicaiton.

Moved.

290

(4 replies, posted in Programming)

Its there for a reason. An inline image is treated the same as inline text. The line box which is automatically generated to hold inline text has to allow for descenders in lower case text which fall beneath the baseline e.g. "j" and "g". When the image is rendered its bottom edge sits on the baseline that lowercase text without descenders would occupy so you see a gap below it. I'm told you can also fix it with {vertical-align: sub} for Firefox etc and {vertical-align:bottom} for IE if you need to display the img inline. I'm not sure but I suspect the reason the problem doesn't occur in IE is that it incorrectly treats the bottom edge of the descender as the baseline.

It isn't just images where this is relevant either. The other place you can run into similar problems is when trying to properly align form controls.

291

(4 replies, posted in Programming)

img {display: block} in your stylesheet or styleblock will fix the dispaly though it won't correct the errors with the page.

Check the validator. You need to get all the attributes such as height, width, border etc out of hte markup and use css instead. Also, strict doctypes are case sensitive, that is, lower case only for attribute names.

292

(1 replies, posted in PunBB 1.2 troubleshooting)

It should work fine provided you are using the stylesheets which came with the latest version of PunBB which contain the IE7 fixes.

Which browser? I can't see any problem. At least none apart from the font sizes being screwed up in IE in respect of which see here http://punbb.org/forums/viewtopic.php?id=7181 and the style author having made a little mess of the left column in viewtopic.

orlandu63 wrote:
Paul wrote:

2. Whilst everything has to work in IE6 I don't think it appropriate to optomise for a previous generation browser.

3. I doubt the difference in rendering time could be detected in normal use.

Doing so is still considered good practice, though.

Considered by whom? Certainly not by me and not by anybody else I can think of. Now there may be a case for prefixing classes with the tag from a point of view of making the stylesheets easier to follow but thats a different point alltogether.

1. IE5 won't be supported by the default styles though 5.5 should still work fine.

2. Whilst everything has to work in IE6 I don't think it appropriate to optomise for a previous generation browser.

3. I doubt the difference in rendering time could be detected in normal use.

4. There is no point in taking too close a look a the stylesheets as they are just for development. They will be torn up and replaced prior to release.

296

(10 replies, posted in PunBB 1.2 troubleshooting)

Because content occupies the height of an element excluding padding but backgrounds also occupy the padding area. If you set the height to 0 and just have top padding equivelant to the height of the background image then the image is visible becuase it occupies the padding but the text is hidden. Its a technique used to make graphic links and banners accessible. Visually you get the graphic but somebody using a screen reader or viewing an unstyled page gets the text. Its also good for SEF because you have a real link not just an image. In PunBB's case the best way to do a banner would actually be to use the H1 and hide the text using this technique. That way the H1 is still there in the markup, you just can't see it. There are other ways to do it of course, you can put the content in a span and shift it off screen but this method doesn't involve any extra markup.

297

(10 replies, posted in PunBB 1.2 troubleshooting)

You still have the <img> tag in your markup, get rid of it and replace it with a text link. Also, the height must be 0px not 120px.

298

(10 replies, posted in PunBB 1.2 troubleshooting)

The best way to do it is to get rid of the <img /> from your markup and then set a background image to the <a> tag in the stylesheets. That way you can use a different background image for each style without touching the code at all.

First I would add an ID to link something like <a id="mybanner"
I would then add a text link to the existing <a> tag to say something like "fourthSTREET Homepage" and then style the <a> something like this 

a#mybanner {
  display:block;
  font-size: 0;
  height: 0;
  line-height: 0;
  overflow: hidden;
  text-decoration: none;
  padding-top: 140px;
  background-image: url(whatever);
  background-repeat: no-repeat;
  background-position: top center;
  }

That also has the adavantage of getting rid of the invalid code you currently have and you can remove the pointless <center> tag.

Unless of course you are referring to fieldsets which have rounded borders by default in IE only.

300

(4 replies, posted in PunBB 1.2 bug reports)

Not a bug, merely a perpetual ommission.