Training, Open Source computer languages
PerlPHPPythonMySQLApache / TomcatTclRubyJavaC and C++LinuxCSS 
Search for:
Home Accessibility Courses Diary The Mouth Forum Resources Site Map About Us Contact
 
For 2023 (and 2024 ...) - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.

Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!

I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
Broken Link?

Posted by BothersomeBumpkin (BothersomeBumpkin), 25 November 2005
From URL: http://www.wellho.net/solutions/index.html

I clicked on link "Perl - I didn't know you could do that"

Received

Parse error: parse error, unexpected T_STRING in /home/wellho/public_html/solutions/perl-perl-i-didn-t-know-you-could-do-that.html on line 35

I am using Firefox 1.0.7

Apologies if this is posted to the wrong group

Posted by admin (Graham Ellis), 25 November 2005
OO ....errrr .... no - you're fine here.  I hadn't spotted that one.   Looks like it came about at our website update a couple of weeks back ... it's because I've got a quote in the subject title - long story and one for me to look at, afresh, in the morning.   A web site of 6000 pages requries a doooozy of a lot oc checking  

Posted by admin (Graham Ellis), 26 November 2005
Fixed!

I took the time to fix the root cause - which was a single quote mark in any subject title in the solution centre - rather than just fix the one page.   Always looking to the future.

If you're writing a page that invites user contributions, it's vital to allow for nasty characters such as single quotes, less than signs and the rest in the input.  We always do.  For pages that we generate internally / that cannot be edited by anyone except us, a lower standard is sometimes acceptable since it's only us who could exploit our own security hole - and what would be the point.

Setting this lower internal standard can, though, catch us out as it has done in this case.   Standards now raised!! - Graham




This page is a thread posted to the opentalk forum at www.opentalk.org.uk and archived here for reference. To jump to the archive index please follow this link.

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2024: Well House Manor • 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • FAX: 01144 1225 793803 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho