Created 16 years ago by Matt,
Last updated February 27th 2018, 1:51:55 pm

Our latest money making scheme involves selling our old crap to people that like buying old crap, who will probably sell it again, at another boot sale! :-)


  1. wow, it looks like he is encoding it properly now - Geffy on Mon Aug 29 2005 18:18:42 GMT+0000 (Coordinated Universal Time)
  2. Thanks for that guys :-) hehe the cheese was lovely. - matt stabeler on Mon Aug 29 2005 18:19:08 GMT+0000 (Coordinated Universal Time)
  3. Just "testing" (pound) to make sure it is fix'd! - Tom on Mon Aug 29 2005 18:32:12 GMT+0000 (Coordinated Universal Time)
  4. Picking on Matt too eh? :P - Luke on Mon Aug 29 2005 20:15:38 GMT+0000 (Coordinated Universal Time)
  5. Think you should use that nice new comment management system to delete those comments where Geffy and I were messing with your system :) Also, join - Tom on Mon Aug 29 2005 21:41:44 GMT+0000 (Coordinated Universal Time)
  6. Yet more (unwanted) advice... Consider removing the line: xml version="1.0" encoding="iso-8859-1" ?"." In your source - yes it should technically be there but there are 2 reasons why not to put it in. The first is that unless the DOCTYPE is the top line in your source, it causes some browsers to use quirks CSS rendering mode (you'll learn more about that if you read Jeffrey Zeldman's book: "designing with web standards", which I *think* might be on our year 3 reading list). The second is that although it is xhtml, in reality most xhtml is sent as content-type "text/html" as otherwise most browsers frack it up (real xhtml data would be sent as "application/xhtml+xml" - but try sending it as this to all but the coolest browsers). So it might be cool Tim Berners-Lee dripping XHTML, but browsers are still treating it like HTML as per the content-type they are receiving). Once you remove this, you'll need to ensure you have: <meta http-equiv="Content-Type" content="text/html: charset=iso-8859-1" /> within the head data (or utf-8 if you prefer), as this will be the main way for clients (including the W3C validator) to know what charset you are using. In regards to the mobile blogs, I'd suggest: When adding to the database: 1). quoted_printable_decode() 2). addslashes() When retrieving from the database: 1). htmlentities() 2). nl2br() - will you ever submit mobile blogs with line breaks in though? If not omit. 3). stripslashes() Don't do any other encoding / decoding, especially in relation to equals signs for mobile blogs - quoted_printable_decode() will handle them. That includes things like POUND being changed to =A3 - again, quoted_printable_decode() will sort that out. - Tom Burnt-a-Tree on Mon Aug 29 2005 22:16:59 GMT+0000 (Coordinated Universal Time)
  7. thanks for that advice Tom, I will implement that soon! :-) when I get the chance! Will probably when I get back to Scarborg (Sun 4th sep) :) - matt on Tue Aug 30 2005 12:26:39 GMT+0000 (Coordinated Universal Time)