Drupal 6.x

After over 1.5 years of development (since 29/11, 2005), plus number of developers contribution, and help of Drupal 6.x schema API, a new Oracle driver for Drupal 6.x is now ready for testing.

The latest version of Oracle driver overcome a lot of Oracle-specific limitation, and able to work well as like as existing Drupal database driver, e.g. MySQL and PgSQL. On the other hand, according to a simple stress test result, Oracle driver is able to keep similar performance as like as other drivers.

Special features include: isolated LOBs value handling (require additional LOBs patch to Drupal 6.x), overcome limitation in table/column/constraint naming with maximum 30 characters, rewrite table/column/constraint name if it is Oracle-specific reserved word, overcome PHP5 OCI8 oci_num_rows() bug on SELECT query, etc. On the other hand, according to number of other Drupal 6.x core patches, most core queries are now Oracle friendly. The above features will also benefit in others database driver implementation.

- Developer with lots of experience in PHP/MySQL

How do you print a custom profile value? I'll be adding this to comment.tpl.php

Tried '$location', '$profile->location', "$profileobject->location'. Nada.

This morning I typed in beinsync.com and usually it goes the their web sight but today it goes to datapod.net which id Drupal. Any ideas why?
Ed M

Greetings guys,

I want to rise a question concerning approaches to implementing user profiles in Drupal once again. I came across with a necessity to valuably extend user profiles many times and at the moment I see that core profile.module can't do it at all. We switched to nodeprofile/nodefamily modules and found them much more flexible since they were bringing CCK to user system.

On the one hand, I know about approach 'everything as a node' and understand that it is not currently in Drupal core. On the other hand, I have clients who requested features which I can't implement using core profile. At the moment we removed core profile.module from our own "Drupal build" (set of modules our company uses for web site development) and switched to nodeprofile.module

Many months ago Wundo redeveloped profile.module 4.7 and created 'profile new generation'. We ported it for Dsrupal 5.0 and developed several plugins to extend user profile. The new core was extremely raw and plugins were not as powerful as CCK plugins are. As I understood later, profile new generation was stopped and abandoned.

I also found that core profile.module evolution is extremely slow - there were almost no valuable (principal, architectural) changes since 4.7 till 6.0 (dev).

I want to emphasize two huge disadvantages of core profile:
1. No ability to extend profile (create custom fields).

Could a hook be added to user.module that would be called when the user has tried and failed to login? This would be added to the user_login_validate() function in the same block as the messages "Sorry, unrecognized username or password" and "Login attempt failed".