CiviCRM Community Forums (archive)

It seems that adding a contact with the standalone form hijacks and changes the logged in user on the same pc and applies changes to this user even if all the values are different from the user.   Is this a bug or a feature? 

This happens even when the form used is not set for user registration or user editing.  Also happens if the user has closed their window, but not logged off.

Fortunately, the issue seems to only be when the standalone form is used from the pc that was logged on.

This is a problem for testing of standalone forms and doing data entry using the form.  Is there an option to turn the automatic hijack off or at least issue a warning message? 

One of the really neat features of CiviCRM is that we can create our own display and input form formats called profiles.  Administer CiviCRM / Configure / CiviCRM Profile

In each profile administration, there is an option to create standalone forms that can be placed on any web page anyplace with the form action being to go to your CiviCRM installation.

There may be interesting issues, like protecting against spam, tailoring the defaults to what you want, tweaking the look.  What is great though is that new contacts can enter themselves.  I have the contacts enter themselves in a new group for review and this might could be circumvented, but could save a lot of time.

We may also use the custom profile as a data entry form - however, be sure not to use the form from a computer that you are logged in on, or CiviCRM thinks you are trying to change the info for the logged in user - really - and I know know how to stop this - thus my post.

I welcome the chance to hear how others are using standalone forms.

I'm revisiting why were not able to use standalone forms to capture new contact information rather than entering the data manually.  We are currently running version 1.9 and I confirmed that at least with the 1.9 version that this issue originally reported in fall of 2007 still is an issue.

The standalone profile form works fine if we are not logged into CiviCRM and can use the form for data input.  Normally the person entering the contact information would be new and not be a CiviCRM user, however, if we use it for data entry and the user is logged in, even if the CiviCRM window has been closed, entering a new contact's information changes the contact information for the logged in user.

I haven't tested this problem with later versions yet.

Dave

I'm happy to report that the issue I had with the stand-alone form hijacking the logged in user's information with version 1.9, does not seem to be an issue with 3.1 that I'm testing.