Contact us dropdown menu not working properly

[kobra]

spminis,

Your settings list the transport method as "PHP" but then you have entered your SMTP details for [email protected]
All of your other email addys are [email protected]
Did you install the email archive manager?
What are the results?
You still have this listed in the contact area

Set "Contact Us" Email Dropdown List Carol <[email protected]>

I thought you set it as Ajeh stated to

[email protected]

There is another thread discussing that HTML Entities not being parsed correctly - You can search for it to see if there is a solution

[spminis]

"You still have this listed in the contact area

Set "Contact Us" Email Dropdown List Carol <[email protected]>

"

That's how it ends up looking after I put the information in correctly. It becomes plain text, not html. That is the problem.
The email settings on the admin page are working fine. The contact us form works fine as long as I don't put in an email addy,

I don't think I've been able to be clear about the problem I'm having but I appreciate your willingness to help. I'll continue to search for an answer.

Carol

[mc12345678]

"You still have this listed in the contact area

Set "Contact Us" Email Dropdown List Carol <[email protected]>

"

That's how it ends up looking after I put the information in correctly. It becomes plain text, not html. That is the problem.
The email settings on the admin page are working fine. The contact us form works fine as long as I don't put in an email addy,

I don't think I've been able to be clear about the problem I'm having but I appreciate your willingness to help. I'll continue to search for an answer.

Carol

The suggestion from earlier was to remove the name and the additional "symbols" before and after the email address such that only an email address is placed in the field. The ampersand followed by lt; or gt; represents less than and greater than respectfully in "html". And currently what is happening is that if one enters <email@somewhere> those symbols are converted to the html equivalent. Further, if you open the entry and save it again the ampersand is then converted to its html equivalent (double converted basically) and therefore you end up with &amp;lt; do it again and it will continue to "grow". So... the suggestion was, don't use such "special" symbols and only enter an email address. :)

[spminis]

The suggestion from earlier was to remove the name and the additional "symbols" before and after the email address such that only an email address is placed in the field. The ampersand followed by lt; or gt; represents less than and greater than respectfully in "html". And currently what is happening is that if one enters <email@somewhere> those symbols are converted to the html equivalent. Further, if you open the entry and save it again the ampersand is then converted to its html equivalent (double converted basically) and therefore you end up with &lt; do it again and it will continue to "grow". So... the suggestion was, don't use such "special" symbols and only enter an email address. :)

Sorry, I thought I mentioned previously that I had tried that (email with no special characters) and it didn't work.
I'm just curious as to why, before I upgraded, the email addys for the contact us drop down were shown correctly and after I upgraded there was a problem. It's not a major problem, as the form works without the email addy but it was a nice feature.
Carol

[mc12345678]

Sorry, I thought I mentioned previously that I had tried that (email with no special characters) and it didn't work.
I'm just curious as to why, before I upgraded, the email addys for the contact us drop down were shown correctly and after I upgraded there was a problem. It's not a major problem, as the form works without the email addy but it was a nice feature.
Carol

No problem, I was just trying to clarify the latest. :) I think we all now understand what you had tried and what didn't work. :)

I too had just tried several variations of email addresses and the contact us form in my tests (code downloaded 2 days ago from the main page of this site) is not presenting a pick list (yet) in either template and in fact contrary to the configuration text is not displayed at all (currently). I'll be looking to see why, but could also be because of some other incomplete entries.