centre{source}

Great news! The first version of the Doctrine 1.0 branch has been released as BETA1. The project is on schedule to release Doctrine 1.0 on September 1st 2008.

Today I am happy to announce the release of Doctrine 1.0-BETA1. This marks the true start for the 1st generation Doctrine stable lifecycle. As you may already know, Doctrine 1.0 has been slated to be released on September 1st 2008 for quite some time now. We still have a few more pre-1.0 releases to go until 1.0. The roadmap for now is BETA1, RC1, RC2 and then 1.0 STABLE. You can see the roadmap in trac if you’re interested in keeping up with the Doctrine schedule. More information on 1.0 and what other things to expect on September 1st will be given soon. Make some noise!

Continue reading "Doctrine 1.0 BETA1 Released"...

A few weeks ago on the symfony blog, Fabien announced that as of symfony 1.1, Doctrine is officially supported. The documentation will slowly be updated and converted from Propel to Doctrine. Right now, the My First Project tutorial and a new Getting started with Doctrine + symfony 1.1 tutorial have been published on the symfony-project website. More documentation coming soon and tutorials for using Doctrine with symfony coming soon.

So, recently here at CentreSource we’ve been working on a project which is using the brand spanking new xServe from Apple. First, let me say the server is pretty slick, but like any other software it has issues. The reason we went with the xServe was because we needed the ability to have web applications which have central authentication and calendaring data. Open Directory, CalDAV, PHP, Apache, and MySQL are just ready to go with xServe, so it made sense!Our usage is that we have these web applications on the net which will use the PHP LDAP Functions to authenticate our users on Open Directory from our PHP web applications, we also communicate to Open Directory whenever adding or changing users passwords to keep things up-to-date. To accomplish this I have written a small web service which lives on the xServe and runs under Apache and PHP. This code talks to Open Directory via the dscl and dsimport command line utilities provided by Apple. I use dsimport for adding the initial working records, and I then use dscl to change passwords. So essentially this web service is just a web service wrapped around those two commands.

Continue reading "Apple xServe: dscl, dsimport and web services aka fun!"...

I have been waiting on this for a while. Finally, someone has put together an article detailing how to use Doctrine with the Zend Framework. The article was linked from the Doctrine website, but you can also go directly to the original article here.

This has to be one of the coolest and simplest things in PHP.

http://www.sitecrafting.com/blog/php-growl/

// Setup $growl = new Growl();
$growl->setAddress(’127.0.0.1′);
$growl->addNotification(”Test”);
$growl->register();
// Send Notification
$growl->notify(”Test”, “Test Alert”, “The body of the test alert!”);

This simple class allows you to send OS X growl notifications to any valid network address. Pretty cool. Within a few minutes, Jared and I were Growling at each other in PHP.

Check out the new Doctrine Cheat Sheet that was released today on the PHP Doctrine website.

I have put together a cheat sheet for all the day to day usage syntaxes of Doctrine. The cheat sheet can be found here. This is the first draft of the document so any comments and feedback would be very useful.

The cheat sheet document can be found here http://www.phpdoctrine.org/blog/doctrine-cheat-sheet

Over at the Doctrine PHP ORM website they have just released a tutorial on how to get started using Doctrine in under 5 minutes!!!

“I have put together a short and sweet tutorial on how to get started using Doctrine in under 5 minutes. A few weeks ago, we announced the sandbox package which allows you to get started using Doctrine with a zero configuration sandbox environment. The tutorial is built using this sandbox package and shows you how Doctrine can be easily implemented and used in your web applications.”

The tutorial can be found here

In my last post I talked about the possibility of Doctrine being in the core of Drupal 7. After some thought, and a little bit of work, I realized this is not necessary. Doctrine can be used in Drupal now with a custom module I wrote. It comes with schema files and models for the drupal core database schema so you can begin using Doctrine models immediately for interacting with your Drupal website database.

The Drupal 7 development has started in the last couple of weeks and the Doctrine bug has been planted in the ear of the Drupal development team. Hopefully the power of Doctrine can be recognized and utilized to take Drupal and Doctrine both to the next level. You can find the discussion between myself and “chx” here.

Recently we had an issue with a website which had a flash upload feature using jqUploader. This feature worked flawlessly when we initially built it but when it was moved to a new server, issues started to come up. First, I discovered that trying to upload empty files results in the following error: “IO error with test.txt.” So now I took it one step further and added 1 character to test.txt, now I don’t get the error, but the flash never shows a progress bar, and never displays that the file was being uploaded. Although, the file was actually uploaded and sent to our php script. We then discovered this, “In some cases, progress events are not received. For example, when the file being transmitted is very small or the upload or download happens very quickly a progress event might not be dispatched.” which can be found here. So, the problem is that the file is so small and the upload is happening so fast, that the events which are called for progress and completion are never even triggered. As far as I know, their is no known fix for this issue. It is just a problem with flash. The next problem was with the complete event. We eventually discovered that jqUploader requires some kind of output at the end of the upload script in order to know it is “complete”. We simply added echo “success”; at the bottom and now it works. I know I didn’t give many answers to the problems described above, but hopefully this will help someone else who comes across the same issue. If you have a solution please comment.