We have had couple of posts on http://blog.atk4.com/ , but you have missed them!
This is last chance to update your RSS address or link.
See you on the new domain!
We have moved this blog to
Please update RSS links. There are going to be no more posts on WordPress.
Password complexity is a fine balance between memorable passwords and crack-able passwords. But how you measure that? For instance “john192” is much easier to crack than “9john2”. However password strength tests approach both with the same algorithm. Even company policies are being made up requiring passwords to cary certain amount of digits or symbols.
A fine line is drawn by a CrackLib – a library coming a long way from Unix and designed for a single purposes of assessing password strength. This article is about how to integrate CrackLib into password verification field.
You can see demo: http://agiletech.ie/pwcheck/
By default pages created with Agile Toolkit end with .html. I myself believe that this is a good extension because HTML is being passed over. However it is easy to use different URLs in Agile Toolkit, here is how
Some discussions prompted me to focus on security goals of ATK4. This post is about how we are approaching security and human-factor as well as flexibility in dealing with external systems.
Based on our current usage and user feedback we are preparing to start development on a new database layer. Thanks to new cool features in PHP (PDO) it’s going to be real easy. However we plan to add some exciting new features such as:
- Rely on PDO, DSN format will change
- Single-table dsql. You can still use joins, which will create multiple dsql instances and make them work together seamlessly.
- Automatic alias management.
- Database driver decides when to fetch data and how.
- Multi-table update() and insert(). MySQL have some support for multi-table update, but this feature will take it to a whole new level.
- Support for simple storage such as SimpleDB. Database engine will allow to compensate for missing [R]DB features.
- dsql Implementation of Iterator, Countable, Seekable and more for nice syntactic sugar.
- Much stricter towards field use. Do not allow developers to slip in any SQL logic.
- Support for expression objects. Similar to $this->js(), this will allow you to build sql operators and functions dynamically
- Proper support for sub-selects. Sub-select being another dsql query.
- Better debugging
- Automated tests
- Transaction support.
As my designer says – best way to break a great web design is to give CMS access to the client. Without any consideration for style they will star moving things around and break stuff. Often not willing to pay for a proper update they will continue to tweak themselves. So what’s the alternative?
There is some – contextual editing. In this post i’ll show how you can do it in ATK
I receive a lot of questions about how to reload page with ATK in certain conditions. There are many approaches and I wanted to write a blog post just about that.
This post continues comparison of ATK and Symfony 2.0. This post is based on features described in Quick tour – page 5
This post continues comparison of ATK and Symfony 2.0. This post is based on features described in Quick tour – page 4
- You have missed few posts!
- ATK4 Blog moved to its own domain. Please update.
- Checking password strength with CrackLib
- Creating beautiful URLs with Agile Toolkit
- Security model
- New features of DB and dsql planned for ATK 4.0
- Lightweight CMS in ATK (video)
- Symfony 2.0 vs ATK3.8 – part 5 – Architecture and beyond
- Symfony 2.0 vs ATK3.8 – part 4 – Bundles, Users, DB
- Symfony 2.0 vs ATK3.8 – part 3 – The Controller
- Symfony 2.0 vs ATK3.8 – part 2 – The View