What would be the best way to construct a contact form in Drupal 6 for each node of a particular type? I have some CCK nodes of type "profile" which have email address as a field. I want to have a view for each node with a contact form that users can fill out and send with their own email address as a return address (so that further contact is being done offsite).
Basically I just want that initial email contact to be done through my site, and when the recipient replies it just goes to the address that the sender entered when they filled out the contact form.
You might be asking yourself why I don't use the personal contact form that comes baked into Drupal. The issue is that the way my institution deploys their Drupal instances to use the local Kerberos logins, the user accounts it creates in Drupal do not have email addresses. They just get a basic skeleton account with username. I don't really want to force users to go through another hoop of editing their user account info, because they most likely just won't do it.
There is nothing to do particularly with node itself, all you need for this - is form with fields (from, to, subject, message) and custom submit handler for this form.
you can implement all this in custom module using forms API to create form and write custom submit for it. And in this submit you need to send email via drupal_mail() - take a look at this, it is provides examples as well. That topic can help you with forms.
Then, if you need to place this form within a node, you can do the following:
via hook_nodeapi, on "view" operation, add form you've created before, you can check for particular node_type and use existing field values (you mentioned cck field with email) to pre-fill form. So that every time user views node, he sees this form.
as logical continue of your task, I suggest it makes sense to take a look at menu system and create local task (tab) for the node, where you'll display email form.
In general, that's all. There are of course other ways of implementing this, however I think this one is the easiest for understanding.
Regards, Slava
Related
I was a user of Right Signature, where we can create merge fields, and we can send the data through post request,
I have recently migrated to Docusign,
I see that they have prefil fields.
What I want to achieve is, Create Prefil fields, like Owner Name, Owner Email, etc,
And supply this fields through DOCUSIGN API, and send them. Is this functionality even possible.
I could not find any documentation, or perhaps I do not have the right search. Can some one point me to it, what will be the syntax for sending the templates, with prefil fields.
Thanks.
Anything you can do from the web app - you can do from API.
The term "pre-fill fields" means something very specific, but I'm not sure exactly what you want.
Any field in DocuSign can be "pre-filled" such that the value is set by the sender. The field can be read-only or can be edited by the person that it is assigned to.
You can also use pre-fill fields that are specific for the sender and therefore cannot be modified by anyone except the sender.
All of this is possible with the API, I suggest you first try it with the web app to understand. You can do everything for free with a developer account - try it and see if it serves your need.
I have created a contact form under Forms with first name, last name, and email that is designed to sign up people for a newsletter. I then created a page so when people click on the link placed on the home page it takes them to a page with the contact form.
Right now when I test the subscribe form out, the data does to to the "back office" where it can be retrieved. However, the information I entered is still in the text fields and, unless you notice the small flash of the web page, one might think nothing happened.
I'd like to know how (or be directed to somewhere in the Kentico 8.2 Documentation) I can make it so that the fields clear and a message appears saying "You have been subscribed to the newsletter." That message can either appear on a separate page on the web site, or send a message to the user email, or both. In the Email Marketing part under the templates there are Subscribe and Unsubscribe templates, but I don't know how to use those.
The other issue is creating an Unsubscribe link. Ideally that will open up to a new page saying "You have been unsubscribed." Kentico 8.2 has an unsubscribe page you can create where the user enters in an email address and then hits the Unsubscribe Request button, but I'd rather not do that. As it stands, I did create a page with that form and tested it, but it doesn't seem to work.
When you edit your form, under general tab, there are settings for what will happen after the form is submitted:
Display Text
Redirect to URL
Clear Form
Continue Editing.
Currently you're using the standard Forms application for something which can be managed through the Newsletter/Email Campaign module. Read the documentation more on how to configure this vs. using the Forms application.
Essentially the steps you will do are:
Create your newsletter following the directions in the linked documentation.
Place a newsletter subscription webpart on your page template and configure it to the newsletter you want them to subscribe to.
Use the out of the box unsubscribe feature to allow users to unsubscribe to your newsletter. No need to add any page to the content tree but you can if you want OR just use the OOTB functionality.
If you follow the documentation you should be able to get it setup properly vs. using an online form.
We want to open sender view of draft/created envelope in our application using REST API and allow sender/user to add signature fields/tags in documents. This sender view currently shows and allow all the options where sender can add new recipient or modify, can change the document and etc. But we want to restrict sender to only can add/edit signature fields/tags, we do not want to allow user to modify any other envelope information or even can send from there.
In short words: Want to open sender view of envelope only for edit signatory fields/tags using REST API.
Could anyone help how we can achieve this.
You can start the view on the tagging page by adding send=1 to the API call. Eg:
https://demo.docusign.net/restapi/v2/accounts/{account_id}/envelopes/{envelope_id}/views/sender?send=1
However the user can still go back to the recipients page if they want to by using the "Other Actions" menu item.
An alternative is for you to figure out what your users need to do on the tagging page and do it for them programmatically. That way you're both providing a better user experience for them and you don't have to worry about them changing the recipients or documents.
What are they doing on the tagging pages? It is not hard for you to programmatically place the tags by using anchor field locating. See the recipe.
I have create a form in Notes Designer version 9.0 and i am unable to forward this form to any users, as i do not find Forward Button under Create Menu.
Not sure if am looking at right options to forward the form, please help.
Thank You
Venu
There are two classic approaches to publishing a form for users to fill out.
Set the Store Form in Document property on the form (see here), and add mail fields (SendTo, Subject, etc.) to it. Add a button that is only visible to you and use #MailSend code in that button to send a document to the people you want to fill out the form. Add another button that is visible to the recipients, and use #MailSend code in that button to send the document back to you, or to a mail-in database. The form will accompany the document wherever it goes. (It will be stored in a field called $Form.)
Just put the form in a database on your server, and set the ACL so that your users can create documents in that database. Send an email message to all the users containing a button with code that executes #Command([Compose]...) with the options set to point to the correct server, database, and form.
Note that both of the above techniques assume that the people you want to fill out the form have Notes clients. If that's not the case, then what you'll want to do is this:
Just put the form in a database on a server that is running the Domino http task, and set the ACL so that your users can create documents in that database. Send an email message to all the users containing a link in the form http://server/path/databasename.nsf/formname?OpenForm
I've got some nice little LotusScript that I can put into the Click event of an Action Hotspot in a rich text field when I'm sending an email manually. Is there a way to programmatically create that in the UI?
My script determines the user's home server and then opens a specific document in the replica of a training database on their home server. I could create these messages with hotspots manually and provide them to the folks who want to email them out. Of course, time being money and the task being boring, I'd rather automate it. I know that I could do this by using a stored form, but am wondering if the greater capability exists, as I can see further applications for it.
One trick I used in the past was to create a profile document in a database, and store some rich text in a field on that profile doc. Then when I needed to programmatically send an email, I could get that rich text field from the profile doc and use AppendRTItem to get it into the body of an email. That should work with any type of rich text, including hotspots.
Note: this won't work in the UI to populate a new email. It does work if you are generating the emails completely in code, though.