Posts Tagged ‘ php ’

Pro Drupal Development 2nd Edition by John K. VanDyk

If you want to get at all serious about taking Drupal beyond a simple installation, Pro Drupal Development is going to be a massive help to you. If you’re anything like me you’ll come back to it again and again for reference and to try out some new ideas.  It covers all kinds of development areas such as [ READ MORE ]

Using Drupal by Angela Byron

Using Drupal is a great little book if you’re just starting out with Drupal, and want to know which modules could be useful for you. If you’re getting into true development stuff and want to play around with Drupal a bit more, the excellent Pro Drupal Development by John VanDyk would be a much better choice. This [ READ MORE ]

wordpress mu XSRF

Cross-site request forgery (XSRF). It’s something that’s becoming a big issue in internet security, and yet is still relatively poorly understood by many developers. If you don’t already know what it is, you can find an excellent introduction in wikipedia: http://en.wikipedia.org/wiki/XSRF In a nutshell, anything on your website is a security risk if it lets someone modify [ READ MORE ]

Review of Panic’s Coda – One-Window Web Development for Mac OS X

I’ve recently been trialling Coda, Panic’s web development environment for Mac OSX. It currently costs $99 (about £65 at current rates) per licence, and offers a fully-featured 15-day trial before you burn your money. The version I’m looking at here is 1.6.2. Coda sells itself as offering a complete environment for all-round web developers: somewhere to [ READ MORE ]

Drupal as an enterprise CMS?

  I’ve been looking a lot recently at Drupal not just as an open source CMS, but as a viable enterprise level CMS. Despite my earlier misgivings I think Drupal has a lot going for it, and it may be that over the next couple of years it will become a much bigger force in the [ READ MORE ]

acquia

Acquia is a company set up by Dries Buytaert, the guy who developed drupal, in an apparent attempt to get drupal taken more seriously by companies and institutions. The idea seems to be that Acquia (carrying on the water theme: druppel means ‘drop’ in Flemish) will provide commercial level support for drupal. When a company or institution [ READ MORE ]

IWMW 2008 – day 2

So, we’re into day 2 of the IWMW 2008 conference at Aberdeen. Day 1 passed with much alcohol, dancing, Aberdonian ‘furry boots’, oh and some web stuff too. I think the highlight was an excellent opening talk by Derrick McClure from the Centre for Linguistic Research at Aberdeen. It was a novel idea to have an [ READ MORE ]

symfony 1.1 and 1.2

symfony 1.1 went live just a month or so ago, and in the relatively short history of symfony is somewhat of a revolution. In fact, the shift in a minor version number belies the effort and heartache that seems to have gone into the newer version, and one wonders at the implied major revamp that symfony [ READ MORE ]

symfony’s sfGuard plugin and LDAP

A while ago I needed to hook up symfony's excellent sfGuard plugin to some LDAP functionality. There are a couple of issues with the plugin and the readme which I think need fixing. In particular, there is no support for checking both LDAP and standard sfGuard passwords. This is absolutely essential (eg an admin user or guest users who aren't in LDAP), and I'm somewhat amazed that there's no provision for this. Moreover, the plugin structure generally makes it seemingly impossible (or if it is possible it's just too horrible to contemplate) to write your own checkPassword() which does do both sorts of checking[ READ MORE ]

The Squiz Licence

Squiz have developed what looks like a good CMS. They provide the software for free, but make their money out of support, design, and training. They also develop a number of extra modules, which they sell to non-educational and non-governmental clients. But because the software is free, it isn't necessarily truly open source. Their SSV licence (essential if you want to use the system to its full potential and do serious stuff with it) means Squiz end up owning any changes you might make. I'm no lawyer, but it even seems like any modules you might develop end up being theirs too. This isn't necessarily a bad thing, at least if you feel it's unlikely that you'd do a massive amount of development yourself. And it's important to know that any changes you do make end up being incorporated into the product, so other Matrix users benefit. It feels like a collaborative situation where everyone gains (including the finances of Squiz!). Is this bad? I don't think so[ READ MORE ]

Follow gnozu on Twitter