Mostrar errores de PHP en servidor de desarrollo | Ubuntu Server

En un servidor de producción es aconsejable NO mostrar los errores de PHP. En Ubuntu Server 10.04 sucede que por defecto está configurado para no mostrarlos (preparado para producción), sin embargo para desarrollar o por simples motivos de aprendizaje en muchas ocasiones se requiere que los errores sean visualizados.

En el caso de fallar, cuando no muestra errores, simplemente aparecerá una página en blanco. Para cambiar este comportamiento se deben seguir los siguientes pasos:

1. Ubicar el archivo de configuración de PHP, por lo general se puede encontrar en /etc/php5/apache2/php.ini , en caso de no encontrarlo una simple ejecución de phpinfo() nos puede mostrar esa ubicación:

2. Ubicar la linea que contenga la instrucción display_errors (en mi caso, esta en la linea 531) y cambiar el Off por el On para que quede asi:

display_errors = On

3. Guardar  los cambios en el archivo php.ini

4. Reiniciar el servicio:

sudo /etc/init.d/apache2 restart

Es suficiente con estos pasos para habilitar la visualización de errores.

Happy coding 🙂

Anuncio publicitario

GNOME Project Mallard Online – Weekly report #04

This is my weekly report # 04:

What I have done last week

• Still improving my skills on Django
• I was reading a lot of books about Django Projects, I found some interesting books:
  • 

What I will do this week

• Finish the web interface according the schedule.
• Start to create the Javascript functions to translate content to Mallard Syntax

Timeline

• I’m just on time according to my schedule

Issues

• Little problems with Django, but nothing serious.

Cool Things

• I met cool people at IRC, great developers and friends at server:irc.gnome.org

Regards 🙂

GNOME Project Mallard Online – Weekly report #03

This is my weekly report # 03:

What I have done last week

• Improving my skills on Django

What I will do this week

• Finish the web interface
• Start to create the Javascript functions to translate content to Mallard Syntax

Timeline

• I’m still delay on my weekly reports, and I remade my project schedule

Issues

• I found new things to think, about data flow of my project.
• I found some system specs that I don’t know to develop them with Django.

Cool Things

• I got money from my University (for Visa and Food), if I get the sponsorship to GUADEC 2010.

Cheers 🙂

GNOME Project Mallard Online – Weekly report #02 (Spanish Version)

Mi reporte semanal # 02:

Que hice la semana pasada

• Empezar la construcción de la interfaz web con Django
• Empezar la construcción de la base de datos, Use Dia para construir los diagramas lógicos.

Que hare esta semana

• Finalizar la interfaz web
• Empezar a crear las funciones Javascript para traducir contendio a la sintaxis de Mallard

Linea de tiempo

• Sigo con el retraso en los reportes semanales.

Problemas

• Tengo algunos problemas para construir la interfaz con Python sin un Framework. Por eso pedí sugerencias a mi mentor, y decidí usar Django.

Cosas Interesantes

• Dia es una buena herramienta, para construir diagramas, rápida y simple. Aquí algunos ejemplos and enlaces que son útiles.

Saludos 🙂

GNOME Project Mallard Online – Weekly report #02

This is my weekly report # 02:

What I have done last week

• Began to build web interface with Django
• Began to build the database, I used Dia to build logic diagrams.

What I will do this week

• Finish the web interface
• Start to create the Javascript functions to translate content to Mallard Syntax

Timeline

• I’m still delay on my weekly reports

Issues

• I have some troubles to build the interface with Python without a Framework. So I ask for suggestions to my mentor, and I decided to use Django.

Cool Things

• Dia is a good tool, to build diagrams, fast and simple. See some examples and links that are useful.

Cheers 🙂

GNOME Project Mallard Online – Weekly report #01 (Spanish version)

Este es mi reporte semanal #01:

Lo que hice la semana pasada

• Planificar las interfaces simples y útiles.
• Planificar el flujo de datos de la aplicación web.
• Bosquejos de la interfaz principal (interfaces basicas de usuarios simples, mantenedor y administrador)

Los bosquejos completos estan aqui (PDF)

Que hare esta semana

• Construir las interfaces reales basadas en los bosquejos

Linea de tiempo

• Estoy retrasado en mi reporte semanal, lo siento.

Problemas

• He gastado mucho tiempo, resolviendo y construyendo el flujo de datos y las interfaces simples y útiles.

Cosas Interesantes

• Encontré que al usar gomockingbird.com, la creación de bosquejos puede ser facil, rápida y buena. Puedo exportar los bosquejos a PDF y PNG. (Aqui esta mallard-online en gomockingbird.com)

Saludos 🙂

GNOME Project Mallard Online – Weekly report #01

This is my weekly report #01:

What I have done last week

• Planning the simple and useful interfaces.
• Planning the data flow of the web application.
• Mockups about main interface (basic interfaces of simple user, maintainer and admin)

All mockups are here (PDF)

What I will do this week

• Build real interfaces based on the mockups

Timeline

• I’m late on my weekly report sorry for that

Issues

• I Spend a lot of time, figuring and making out the data flow and the simple and useful interfaces

Cool Things

• I found that using gomockingbird.com, could be easy, fast and good creating mockups. I can export the mockups to PDF and PNG. (Here is mallard-online at gomockingbird.com)

Kind regards 🙂

My Summer of code project Portfolio

During the course of my Summer of Code project, I’ll not only have to write code, I’ll also have to spend some time on reporting the progress of my project. This consists of the following:

• Send to gnome-soc-list a weekly report
• Keep my  portfolio page up-to-date
• Promote my work on my blog

So, I have to maintain a wiki page with all the information about my project. This page should have all the necessary information about my project, for those people that want to know more about it.

The goal of this page is to inform people about my project (the link you give them if they want to know more) and to make sure that all the information about it will still be available after the summer.

A placeholder for each project at GNOME has been made here: Student Projects

My portfolio is here: GNOME Project Mallard online (Sergio Infante Montero)

Details of my GSoC Project – GNOME Project Mallard online

Title: GNOME Project Mallard online
Student: Sergio Infante Montero
Abstract: System online to create, edit, review Mallard Syntax document for GNOME Documentation Project
Content:

• What is the ultimate goal of your proposal? : System online to write,edit and review documentation for GNOME Project
• What components/modules will it touch/change or create? ProjectMallard, Yelp, GIT
• What benefits does it have for GNOME and its community? : More people involved on generate of Documentation using Mallard
• Why you’d like to complete this particular project? I want to contribute with GNOME, especially on Documentation Project and be part of GNOME Foundation
• How do you plan to achieve completion of your project?
  • Use an agile development software methodology
  • Generate all basic Web Interface with HTML, CSS and Python. Hosting project on gitorious – May 31 Deadline
  • Make a JavaScript module to give an usable web interface to write documentation according to Mallard, this module will generate XML – Jun 14 Deadline
  • Generation of Mallard Syntax document with Python- Jun 28 Deadline
  • Editing Mallard documents with web interface- Jul 12 Deadline
  • Integration with GIT using Python- Ago 9 Deadline
  • System complete and debugged – Ago 16 Deadline
• What will be showable at mid-term [1]? : Generation of Mallard files, edit, review, and creation online.
• Why do you think you are be the best person to work on this project?: I was working with Mallard on last months, understand it, write some documentation for postr (app for flickr on GNOME), giving speechs of Mallard, and developing a web application to generate .page files
• What are your past experiences (if any) with the open source world?: I’m a member of OpenOffice.org Project, as a translator, documentator and managing the Spanish web site of oooauthors.org, patchs and bug triagging too. With GNOME, I participated on Bug Team Squad, on bug triagging, and adding some code on Postr application, and now with ProjectMallard.
• Why are you interested in improving GNOME? I really like the project, GNOME 3 will be awesome and I want to contribute with the future, i like the people around it, the friendship, the way how it develop software, and I have good friends that they are part of GNOME Foundation and I want to colaborate with them.
• Please attach a link to a bug (bugzilla.gnome.org or other Free Software tracker) containing a patch you’ve written: https://bugzilla.gnome.org/show_bug.cgi?id=562160

[1] All students are invited to attend GUADEC and present theirproject there, which is right after the midterm evaluation deadline.

Charla IRC de GNOME Hispano | Abril 2010

La Asociación GNOME Hispano, con la intención de promocionar el proyecto GNOME en todos los ámbitos y, segundo, intentar servir de punto de entrada al proyecto para los usuarios/desarrolladores que lo deseen, los invita a participar de la Charla IRC de Febrero.

Para este mes tenemos ya todo confirmado:

Tema: GNOME 3
Expositor: Siegfried-Angel Gevatter Pujals
Fecha: Sábado 17 de Febrero – 2010
Hora: 18hrs UTC (12hrs, México D.F., 13hrs Lima, 13hrs Bogota, 14hrs Santiago, 15hrs Buenos Aires, 20hrs Madrid, 21hrs Helsinki)
Lugar: En irc.gnome.org canal #gnome-hispano

Los recursos previos y posteriores a la charla estarán en el sitio de GNOME HIspano

Si tienes problemas con el tiempo aquí tienes una cuenta regresiva 🙂

Están cordialmente invitados, por favor compartan esta invitación con sus colegas, amigos, curiosos y fans Gnomeros. Así que no se olviden separar un tiempo para estar presentes en la charla.