debug

Hello, I just released an update to Drupal Quickstart:

Version 0.9.1

This release works almost exactly the same as the 0.9 release, but fixes two issues:

• Drush make file problem that appeared after the Git migration
• Git 417 errors caused by squid proxy server

I have created a site based on open atrium.
i can create an openatrium site based on the distribution through aegir
I add and configure modules to the created site.

When I clone the site,
1. backup created
2. vhost file created
3. database is created
4. i can access the site through the url

but the clone task never terminates
I also do not get a site entry in aegir
Is there a way to debug this? I don't get any entries from the backend provision anywhere? Is there a way that error messages can be written to the clone log once the provision-verify script is written?

Even before diving into XDebug, check out the FireBug for Drupal project!

Install and enable the FireBug for Drupal module on your Drupal install, install the FireBug for Drupal FireFox extension and start debugging. The new Drupal panel in FireBug has a number of sub-panels to show essential information about the pages loaded. There are function calls you can make on the server to generate messages and everything goes to a FireBug for Drupal panel.

I had mentioned the idea before of having a session on how to debug Drupal with break-points and step through etc.

Who would like to do this?

Finbarr

Quando temos que desenvolver algo além de um site "simples", é certo que vamos ter que sujar as mãos e criar um pouco de código que seja. Se existirem regras mais complexas, vem outra necessidade: debug.

Na página do projeto Devel(http://drupal.org/project/devel), tem um link sobre esse assunto que é leitura obrigatória, podemos dizer, detalhando a utilização desse módulo que é fundamental na hora de desenvolver módulos.

"This page gives a brief overview of some of the tools you can use to make Drupal development and debugging easier.