Deprecated - Documentation

Since I just spent a good chunk of time looking for this info I figured I would post it, since I can't find it anywhere.

the table sequences houses code based auto increment values for the various nodes or counters. For example it makes sure node 114 follows node 113. entries are made the FIRST time a node is created, they are not created with the database install.

the table node could be considered the administrative location of node information. It has things like "is this node sticky" and who created it, and so on.

Hi

I have rewritten the .htaccess file with comments to assist the newbies and too lazy to read ones. How do I post the text file or get it included in the documentation without loosing the basic layout format of it?

Regards

Hi!
I just wrote a document dealing with a problem I had to work out recently involving a custom user registration procedure.
I'd like to hear any comments on it regarding its usefulness and/or uselessness.
-----
For the past six months, I have been busy implementing a Drupal-based customer portal for a smallish ISP. (smallish being 60-70k users at the moment)

This involves a lot more integration work than any normal portal would, and has unique requirements when it comes to user registration.

The ISP in question wishes to allow existing customers to sign up using their billing number and their name, which are printed on the billing statements the users get every month in the post.

At the ISP, my team and the ISP's team set up an XMLRPC server to allow the Drupal side to validate customers without having access to the customer database. This server accepts a billing number and billing name, checks to ensure the data is correct, and sends back information about that customer that we then use on the Drupal side to autoconfigure the user's account. Things like whether the user has phone service with the ISP and what town to show weather for.

This happens once during user creation, and can also be done by the user or an administrator to reset the user defaults in an automatic fashion.

If anyone who reads this has ever been in a similar situation, I hope the following helps you.

One thing I love about the PHP help at php.net and I find incredibly useful is the user submitted comments.

For example: http://us2.php.net/manual/en/function.preg-match.php

The example_node.module in api docs is excellent. However, there is a mistake in it.

I installed it. When I go to the submit node page, I get
title
node
INPUT FORMATS
color
quantity.

INPUT FORMATS should be after all the text fields. Otherwise the module seems to work correctly. Thank you for writing it. If it can be fixed I would very much appreciate it. I'm using it instead of flexinode and cck to make my new node types.

I was looking to use this example module to extend some node types but it seems that it is designed for 4.6. The format of the API seems to be all 4.6 in that example, even though it is in the 4.7 section. Correct me if I'm wrong?