It was August 2008 when I proposed an international "Drupalers Meet Up at Machu Pichu (Perú)", and still have that dream coming to my mind, fueling my passion for the freedom of software.

Getting back to the cancellation of Drupalcon Sao Paulo 2012, remembered that "energy never dies, it just changes form", and dude we are fully charged of energies!

Yeah! Drupal community has some dark historic episodes, including a server downtime (2005), a volcano in Iceland during Drupalcon San Francisco (2010) and a Drupalcon being cancelled, but wait! Remember... , we never give up! never!

The Drupal Latino community got great momentum and keeps moving forward! So, where all those energies moved? some were already there, others are getting extra batteries, and some are transforming into more Drupalcamps:

Menu Token has good reception in the community, thanks to hardworker co-maintainers and great patches from the community!

Now is time to make an small pause and think about the future.

So, following feature requests given me an idea on what would be the next steps:
- Features integration: http://drupal.org/node/1289302
- Additional tokens: http://drupal.org/node/973882
- Selectively expand menus with tokens: http://drupal.org/node/978948

Of course I want to see them implemented.

Additionally:

There are several ways to improve Drupal performance, and to be more honest, there are several ways to improve your infrastructure supporting Drupal (e.g. Web Server, MySQL Server, PHP opt-code cache, Varnish/Boost HTML cache, Application cache (Memcached/APC), Pagespeed (output compression/optimization), etc). You can also add gigs of RAM to your server, more processors and perhaps deploy your Drupal site on a cluster of 10+ dedicated servers. In the end, if your source code does not perform well, you will be just wasting CPU, Memory and Bandwidth and that equal money.

Sometimes we need to hide a module to avoid certain known conflicts on a site. The Following is a specific use case for doing as such:

Note: Use jQuery UI 1.8 in an specific admin page

• Module jquery_ui is installed and provides version jQuery UI 1.7
• jQuery UI 1.8 is needed in admin page: "admin/build/custompage"

Issue

Once "jquery_ui" module is installed, the "context" module plugin "reaction block" will load "jquery_ui" on every page load.

Solution alternatives

1. Patch module "jquery_ui" to load desired version when needed

Recently I were archiving a Drupal site and needed to move the "files" folder to another path. Then some critical issues raised:

• Image paths were using an nonexistent path
• All file links were missing the domain name

The following modules were affected:

• Imagecache: when displaying cached images
• User: when displaying the default avatar
• Faq: was not displaying the header image
• Node: image paths were explicit (it is usual)

Then had to update following tables and system variables:

• Variables: user_picture_default, faq_description, theme_fusion_starter_lite_settings

All of Latin America celebrates its biggest Drupal event of the year!

We can finally officially announce the biggest event dedicated to Drupal for the whole Latin American continent: "Drupal Summit Latino – Lima 2011".

The summit will take place in Lima (Peru) from 27th to 29th of January 2011.

We will have a full schedule of sessions by renowned and experienced Drupalers from several Latin American countries, the U.S. and Europe.

We are prepared and expect more than 300 attendees, that undoubtedly will be the highest concentration ever seen in Latin America of experience and knowledge of the most successful websites publishing software at the moment: Drupal, of course!

We invite you to propose a session for the Drupal Summit Latino 2011! Please be aware that the deadline for proposals is the 10th of January.

I've been working with Views since Drupal 5.x, at that time it was the longest form you could ever have imagined. But it was still an awesome module with its ability to facilitate the creation of lists and tables to display content. With the release of Drupal 6.x, the community had to wait a while to get Views 2.0 in place. It came with great UI usability improvements, amazing enhancements and a brand new API.

Can't attend Drupalcon? take it easy! watch the The Internet Archive. To date there are thousands of videos from past Drupalcons. A tremendous source of wisdom in the most exiting Drupal topics since 2007.

My d.o profile says that I'm a 3 years old drupaler, and I love it. From my personal vision, God blessed me a lot since I'm working with Drupal. Not only in my job, also had the wonderful opportunity to meet so nice people, and visit 3 new countries in just one year!

What about PHP? well..., we have a trading agreement :D

Do you want to keep your site multi-language friendly? Please follow this:

1. Use t('text') instead of 'text'
2. Enable Multilingual in your content types
3. If your site uses English, do it with pure English first, then translate
4. Avoid the use of HTML into strings as much as possible
5. In CCK fields, use PHP code for Allowed values list, i.e.: return array(1=>t('text'), ...)
6. Add the filter "Node Translation: Language" to your views
   7 - 10. Read the manual http://drupal.org/handbooks

Blessings.