calendar
May 2012 M T W T F S S « Feb 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 recent comments
Category Archives: php
php coding standards
Why coding standards? In big projects, in any project, they’re essential: understandeable, much easier, solid code. Perfect, mandatory for a team. The objective is to have all decisions documented, choices and standards that I will stick on when developing. Important … Continue reading
Posted in codeigniter, featured, php
Tagged codeigniter, coding standards, error handling, framework, model view controller, mvc, naming convention
2 Comments
free graphs and charts for php jpgraph and ruhanirabin share this on…
the definitive regular expression to validate emails (preg_match) /^([\w\!\#$\%\&\'\*\+\-\/\=\?\^\`{\|\}\~]+\.)*[\w\!\#$\%\&\'\*\+\-\/\=\?\^\`{\|\}\~]+@((((([a-z0-9]{1}[a-z0-9\-]{0,62}[a-z0-9]{1})|[a-z])\.)+[a-z]{2,6})|(\d{1,3}\.){3}\d{1,3}(\:\d{1,5})?)$/i http://fightingforalostcause.net/misc/2006/compare-email-regex.php share this on…
date semantics
When dating a blog post, a comment, an article, there is usually a semantic problem. Either “07/01/09, 5:04″ or “7 January 2009 17:04 CET”, or even “1 days, 2:04:33 ago” are not very user friendly. This post shows how to present a shorter, more semantic date and time, and how to calculate it with PHP. Continue reading
regular expressions: a tutorial, a bunch of examples and a thourough list of tools share this on…
a comparison between both php frameworks: codeigniter vs symfony share this on…
when geolocation becomes a problem
Following the excellent article in smashingmagazine about geolocation, in their comments I found these interesting ideas: In a world where a lot of people travel and bring their laptops or iPhones, it is nonsense that a website turns to a … Continue reading
Posted in geo, php
Tagged default website language, IP geolocation, usability, user language preferences
3 Comments
solution to the uniq-qinu error in mediawiki
An error known as UNIQxxxx - xxxxQINU could arise when some code or text is passed twice through the parser. Badly written extensions, inapropriate wiki text or tags, a number or reasons could show this marker. Continue reading