Page 1 of 1
contactform
Posted: Sat Nov 10, 2012 6:30 pm
by Timbalu
Underneath the contactform form we have the same standard sentences like for commentform forms.
At least one is completely useless and does not really help John Doe contacters to get on their way.
"Die angegebene E-Mail-Adresse wird nicht dargestellt, sondern nur für eventuelle Benachrichtigungen verwendet."
What can we do about it?
Re: contactform
Posted: Sun Nov 11, 2012 5:08 pm
by Czorneboh
Oh, I was not recognising it.
I guess, this was overtaken from contactform underneath every article. It makes really no sense.
Everybody expects, that that message or comment addresses the blog-owner and should know, that he needs to type his/her email-address to get an answer.
So this sentence should simply deleted.
But behind the word "Kommentar" in next sentence could be added "oder Nachricht".
Or so:
"eine Frage, Nachricht oder einen Kommentar".
On Friday one reader has used the field to write for me only a comment combined with question.
regards
Czorneboh
Re: contactform
Posted: Mon Nov 12, 2012 3:07 pm
by Don Chambers
That line is emitted by the spamblock plugin when the option "Hide E-Mail addresses of commenting users" is enabled. The code is at line 1227:
Code: Select all
if (serendipity_db_bool($this->get_config('hide_email', false))) {
echo '<div class="serendipity_commentDirection serendipity_comment_spamblock">' . PLUGIN_EVENT_SPAMBLOCK_HIDE_EMAIL_NOTICE . '</div>';
}
Is there a conditional test that plugin can use to determine if this is a comment vs. contact form?
Re: contactform
Posted: Tue Nov 13, 2012 4:39 pm
by Timbalu
via CSS as easy as this...
until better solution...
Code: Select all
/* hide contactform plugin comment form email text */
.serendipity_staticpage .serendipity_comment_spamblock {
display: none;
}
Re: contactform
Posted: Tue Nov 13, 2012 4:55 pm
by Don Chambers
.serendipity_staticpage????
Re: contactform
Posted: Tue Nov 13, 2012 5:39 pm
by Timbalu
Re: contactform
Posted: Tue Nov 13, 2012 6:03 pm
by Don Chambers
The css above will only work for those using the 2k11 template. You said it was "wisely" added. I have no problem with the added class, but why did you refer to it as a "wise" addition? If it is indeed "wise", then perhaps it should be added to the plugin's tpl, and not just 2k11?
Also, for either 2k11, or the plugin, if there is to be a modified plugin_contactform.tpl, then there should probably be a matching plugin_dynamicform.tpl IMHO.
Re: contactform
Posted: Tue Nov 13, 2012 6:35 pm
by Timbalu
Don, as this thread did not fell on massive interest, I personally was satisfied with my small css solution for the moment. Please feel free to implement something better for all of us ...
Maybe you could find out with the assigned var
Code: Select all
{if !empty($staticpage_pagetitle)} do something {/if}
or change the plugin itself, to output a more specific contactform var to check for.
Or use one of these. Available are:
Code: Select all
'plugin_contactform_articleformat' => $this->get_config('articleformat'),
'plugin_contactform_name' => PLUGIN_CONTACTFORM_TITLE,
'plugin_contactform_pagetitle' => $this->get_config('pagetitle'),
'plugin_contactform_preface' => $this->get_config('intro'),
'plugin_contactform_sent' => $this->get_config('sent', PLUGIN_CONTACTFORM_SENT_HTML),
'plugin_contactform_message' => PLUGIN_CONTACTFORM_MESSAGE,
Re: contactform
Posted: Tue Nov 13, 2012 8:22 pm
by yellowled
Don't know if you care, but you do realize that this will still be read in (at least some) screenreaders? It needs an additional visibility: hidden;
Other than that, this should really be suppressed in the contact form plugin in the first place since it really doesn't make any sense in the contact form in any template.
YL