about 1 year ago - 11 comments
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
about 2 years ago - 1 comment
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
about 2 years ago - 3 comments
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
about 2 years ago - 16 comments
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.
about 2 years ago - No comments
I recently read this post by Francois Zaninotto (recently an ex-core symfony developer) about modifying symfony to make it lightweight enough for ajax calls. As he puts it: That’s when the idea of a “small symfony” comes. Wouldn’t it be great if you could get access to the model layer, the configuration, the autoloading, the user
about 2 years ago - 2 comments
Looks like Francois Zaninotto, one of the core symfony developers, has quit the team. He was largely responsible for the documentation, and co-authored the excellent symfony book, published by Apress. One of the key successes behind symfony was the documentation. The fact that there was human-readable documentation, and not just an API, was a remarkable
about 2 years ago - 3 comments
The symfony admin generator is one of the best features of the framework. With just a couple of commands and a few changes to a config file, you can have something pretty close to a database access interface. There’s a simple built in security module, and sfGuard is fairly simple to understand if you need a more complex security module.
about 2 years ago - 1 comment
I’ve recently been looking at the essential (ie why isn’t it included in the core?) symfony plugin sfGuard. It offers are really nice, simple way of building a simple user, role, and permissions system into your symfony app.
about 2 years ago - 2 comments
Routing is a great way to get user-friendly urls, generate new urls for the same code, or refactor old urls without having to touch your code. They are perhaps a little tricky to get used to at first, but fairly quickly make sense. The main thing to realise is that rules work from top to bottom, and the first one to match is used. Quite often problems or unexpected results come from not ordering the rules correctly. Always put more general rules lower down!
about 2 years ago - No comments
I’ve recently been deploying some symfony (http://www.symfony-project.org/) applications at The University of Kent. I’m pleased with the results. Symfony is an MVC framework, along the lines of Ruby on Rails, but based on PHP5. It is widely used, including yahoo bookmarks: http://www.ysearchblog.com/archives/000376.html and the beta of the new version of del.icio.us: http://www.symfony-project.org/blog/2007/10/02/delicious-preview-built-with-symfony Why? So why did
about 2 years ago
Yes basically, redirect perform a header(“location: “); whereas forward is 100% symfony made.
about 2 years ago
just a tip, always redirect after a post method
about 2 years ago
So redirect after a post method. Otherwise a forward generally seems the way to go.
I’ve certainly found the forward404 etc methods very useful too.
about 1 year ago
The quote was quoted near-verbatim from the official symfony docs:
http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Layer
The strength of the documentation is one of the main reasons I chose to go with symfony as my PHP web framework of choice.
about 1 year ago
I don’t think it’s that straight forward when you involve Ajax call. Using redirect means Symfony is unable to detect if a request is initiated via Ajax or not.
So in addition to that rule of thumb, if it is a post, but an Ajax call (use $request->isXmlHttpRequest() for detection), use forward instead of redirect.
Use forward as much as you can and only redirect if you really really have to.
I think that’s better rules, but correct me if I’m wrong.
about 9 months ago
well heres one normal case where you would need to use a forward i think…
if you are handling form submission in another action, then the handleError for that action, will need to forward back to original form(action) so the form has orig request variables to display the error messages i believe. or you could submit the form to itself (i choose against this recently on 1 form as there are a few buttons to submit, and it was easier to just set validation yml files for each action [versus do custom validation with validateActioname() and check which button was pressed]).