I occasionally do some code development for a customer who has a HUGE site (I'd estimate in excess of 500,000 lines of code). I keep running into some really poor coding practices by previous developers. Of course, I get paid for fixing them, so I guess that's good.
Seeking some guidance here. I have a project that requires a multi-step form.
Here is what I am trying to do: There is a large form that has to be converted to allow people to complete it online. It's a fairly large paper form (small print, legal size paper) and right now it's a 3-step form. The data from this form is associated with a case-tracker case. They need to be able to edit this data afterwards as well. The gist of this being that the data needs to be a node.
Here is what has been done so far: A new node-type was created in the Content Types menu. That node was added to the case tracker system. No fields were added or removed (standard Title and Body). Following Jeff Eaton's Dynamic and Multi-Step With Drupal's Form API article the form has been implemented. The form works very well. Right now someone goes to this form and goes through the steps normally.
When the form finally gets submitted, it creates a new node using drupal_execute. The 'body' becomes the output from the form. The values get stored in a separate table.
Hi,
In drupal, suppose two users open a page at the same time and one user edits and saves it, then how can we show any kinds of updated information to the other user?