User creation wizard

I am trying to build my first module for a 4.7 version.
The features I am trying to give will be available to anonymous users where :

- new user account will be created via a block on the side bar (could be just a menu item though)
- new acidfree album under certain parent album will be created
- user will not be able to login before a validation of the email has been done, via a validation link on his email account that the user has to click

Basically, what I am trying to do is an automated wizard for :
- user creation (possibly need to use the API, so all the functionality of a normal create account form is there)
- creation of an acidfree album under another acidfree album that is the parent

The reason for trying to do this is because I found out that people that try to create accounts on my site find it difficult to create the account and make their own acidfree album. The site I own is photography oriented and I want to stream out a 'one click' automated login process along with the creation of the acidfree album.

I am talking about module design here, because I want to have different types of user registration forms like :
- Photographers
- Models
- Stylists
- Make up artists
etc.

Any pointers would be helpfull!!!!

P.S. If you feel like that no module is needed but a simple page with php filter format enabled please let me know.

syntax error theme.inc on line 854

I am getting this error message on the install page.
Parse error: syntax error, unexpected '.' in includes/theme.inc on line 854,
Can anybody help? I have no clue where to start.

Altering nodereference field autocomplete query

Hi All,
nodereference module has a handler function _nodereference_potential_references, wich is used to return all nodes that has title LIKE '%%%s%', which means any title containing s will be retrieved. I want to alter this clause to only return nodes where titlt starts with (not contains) s. off course I'll not change the module itself, so, I need another way (hook or something) to alter nodes retrieved.

Seeking Indian Drupal developers for ongoing projects

Right now we have contracts for many interesting drupal development assignments, which is beyond the capacity of our inhouse team.
We are looking for an extension to our closely knit development team.

We are flexible, you can choose to work from home as independent part time contrator, or you are welcome to join us as full time employees. The pay package is good for talented developers and an opportunity of a long term relationship in many of our ongoing projects. More importantly, it is fun to be a part of our team.

Search Engines - index both the Image Node, and the Text Node describing the image.

Just thinking out aloud here - don't have a good way to handle this scenario, so looking for ideas.

I have uploaded multiple images - let's call them Hotel1, Hotel2, say they are pictures of hotels. They get URLs like /images/hotels/hotel1, and /images/hotels/hotel2 and search engines index them as such.

I have a book, with multiple child pages that go into length on each hotel.
/books/hotels/hotel1, /books/hotels/hotel2. These are the main entry pages, and the hotel1 book page contains an thumbnail of the hotel1 image, clicking on which can bring up the image. Multiple images may exist in one book page.

So going from the book page to image is fine, and anyone coming first to the book page will find the experience good.

But if someone came here from a search engine, they may enter from the /images/hotels/hotel1 image node link. They will see the image, and no text. That page has no info (unless I manually add a link - "please see /books/hotels/hotel1 for description"). So this is not a good experience.

Anyone else have thoughts on how to handle this? I do not want to add all the text in the image node - since multiple images may be present on a single book page, that would not work out.

userpoints - have users start with points? possible?

Hi there. Using an older version of Userpoints until the broken connection with Ecommerce in 5.x gets fixed (depends on degraded Ecommerce module Payment, does not communicate with replacement module Receipt).

Pages

Subscribe with RSS Subscribe to RSS - Drupal 4.7.x