Articles récents
Commentaires récents
- In Working with a company that embraces open source
- Guy Steels wrote: And a big thank you for open sourcing your plugins. When we look if certain functionality is...
- In Marius Wilms - The CakePHP Media Plugin
- Sotir wrote: Some practice use examples will be nice to have around...
- In Felix Geisendörfer - Recipies for successful CakePHP projects
- Felix Geisendörfer wrote: http://felixge.s3.amazonaws.com/09/cakephp-receipes.pdf (sorry, 8mb download)
- In Joël Perras - Demystifying Webservices in CakePHP
- Neil Crookes wrote: I have an upcoming project that could use the Google Chart / Visualisation API so would be...
Catégories
Marius Wilms - The CakePHP Media Plugin
Ecrit le Sat, Jul 18th 2009, 00:27 dans CakeFest
If Marius had more than an hour to talk about the Media Plugin, he most certainly would have taken it. To go over the features and functionality of the entire plugin would have been many hours as there is a lot there. A brief touch on the features provided by the plugin was discussed, with some examples.
Requirements are in the high end, but considering the state of PHP and the upcoming version of CakePHP, developers should be moving forward in terms of their PHP version and library support anyway. The Media plugin requires CakePHP 1.2.x.x and PHP 5.2.0+. It enables the transfer, manipulation and embedding of files in many varied ways.
You can find the media plugin at: http://github.com/davidpersson/media
Marius' focus was on doing media manipulation and embedding "properly", and identified that while there are lots of user contributions floating around the net, none of them were meeting his needs and were flexible enough. One of the main points he made here was that if done incorrectly, potential security risks arise due to command line interaction and file saving. Validation was one particular section of the code that made this a tricky plugin to develop, but allowed tests to be implemented to ensure security.
Some common points that we hear all the time came through, and they make sense for CakePHP as well as any web application for security reasons:
- Don't trust users supplied filenames
- Don't store files in an accessible webroot, rather have them accessible to scripts.
- Make the upload location (and local filenames) unguessable (like referencing files by UUIDs)
To ensure flexibility of use, a behavior is included to allow attachment to any number of models, and generioc storage and linking provided to ease integration into existing apps.
Retour aux articles de Graham's

Qu'est-ce que OpenID ?
OpenID est un nouveau standard ouvert qui permet de se connecter à des sites web grâce à une simple URL vous appartenant. Cette URL peut être votre page personnelle ou blog, ou peut vous être fournie par un site web que vous utilisez. Dans tous les cas, vous n'avez qu'à vous connecter une seule fois auprès de votre fournisseur OpenID, vous permettant ainsi de n'avoir qu'un seul mot de passe à maintenir.Learn more.
Comment est-ce que CakeDC utilise OpenID ?
Vous pouvez utiliser votre identité OpenID lorsque vous postez des commentaires sur le site. Lorsque vous voyez un champ de formulaire avec
il suffit de renseigner votre identité OpenID pour vous permettre de poster. Nous acceptons également les identités Google et Yahoo!. Utilisez simplement soit "google.com" soit "yahoo.com" et notre librairie OpenID ira chercher vos informations au bon endroit.
Commentaires:
Add New Comment
tuts baby
Reply | Sotir | posted on 18/7/09