Your email form should look something like this:

[form][t]
[r][c width=100px]Your Email:
[c][text from {~email} size=30]
[r]
[c]Subject:
[c][text subject size=30]
[r][c cols=2]Message:
[r][c cols=2][box body rows=6 cols=40][box]
[r]
[c]
[c right][submit "SEND MAIL"]
[t]
[command mail [email protected] from={=from} body={=body}
subject={=subject} mode=active]
[command nextpage main.thankyou]
[form]

You shouldn't have to worry about sitemail or authorizations, though they
can be used. Maybe you just need the mode parameter?

Cheers,
Dan



On Mon, Mar 10, 2014 at 4:55 AM, jdoe <[email protected]>wrote:

> ... I tried - but somehow did not succeed, even despite upgrading
> everything to BW 4.07. - However my approach is still working :) so I'm
> going to stick with it for the time being even although it's probably not
> exactly a 'boltwire' way to do it ;)
>
> On a different note, I tried to get e-mail working (4.06 and 4.07), and
> despite having almost literally followed your note on
> http://www.boltwire.com/index.php?p=docs.concepts.mail (down to "And
> done!", adding an address for {sitemail} in config), I keep getting "Mail
> authorization failed. Mail not sent." issues (and indeed, with no mail
> being sent...). I learned from earlier release notes however, that the way
> how mailing is authorized changed - so probably I'm missing an easy clue
> here...
>
> On yet a different note, my sincere congrats on BW - remarkable work! :)
>
> Thanks & regards,
> JF
>
>
> Am Mittwoch, 5. März 2014 15:42:30 UTC+1 schrieb Dan:
>>
>> I think you could also do
>>
>> [[{+p}|img:somefile.jpg|data-lightbox='' rel='']]
>>
>> or if you need the directory:
>>
>> [[{+p}|[^somefile.jpg dir='pix'^]|data-lightbox='' rel='']]
>>
>> The third section (after the second pipe) allows you to insert any of the
>> allowed attrs. You would need to add the data-lightbox of course:
>>
>> $BOLTattrs['a'] = 'id,class,href,name,style,rev,
>> rel,target,title,accesskey,tabindex,class,id,xmllang';
>>
>> Glad you got it working.
>>
>> Cheers,
>> Dan
>>
>>
>>
>>
>> On Wed, Mar 5, 2014 at 7:12 AM, jdoe <[email protected]> wrote:
>>
>>> Hi Dan - thanks for the reply.
>>>
>>> Changing BOLTargs and adapting variables.php worked - the markup had to
>>> be adapted though, since lightbox-data actually works in <a> rather than
>>> <img> tags; so I finally got a working code using:
>>>
>>> "<a href='https://........./{+p}' data-lightbox='results'>[^{+p}
>>> dir='.......'^]</a>"   in the fmt string of the search.
>>>
>>> Thanks again!
>>> Cheers,
>>> JF
>>>
>>>
>>> Am Sonntag, 2. März 2014 14:48:28 UTC+1 schrieb Dan:
>>>>
>>>> Glad you got #0 and #3 resolved, and that #1 is at least understood. If
>>>> you need help implementing some alternate solution, let me know.
>>>>
>>>> I did look into number 2 and discovered why it wasn't working for you.
>>>> The rel attribute works fine but the data-lightbox parameter is not
>>>> recognized because of the hyphen. As it is, BoltWire recognizes paremeter
>>>> labels that include the \w characters (a-z0-9_). But I can definitely see
>>>> the need for being able to use lightbox--and I assume the data-lightbox
>>>> label is not negotiable... :)
>>>>
>>>> To fix it, try going to engine.php and replacing the first line of the
>>>> BOLTargs function down near the bottom (line 221) with this:
>>>>
>>>> function BOLTargs($x, $type='', $pat='(?>([-\\w]+)=)') {
>>>>
>>>> I've tried it and it seems to work just fine now with your parameter.
>>>> I'll add it to the next release as a bug fix/feature enhancement. Remember,
>>>> to reset the allowed img attributes in config.php, not index.php. And your
>>>> page markup will look like
>>>>
>>>> [^boltwire.gif rel=whatever data-lightbox={p}^]  (or {+p} in a
>>>> template).
>>>>
>>>> Cheers,
>>>> Dan
>>>>
>>>>
>>>>
>>>> On Sat, Mar 1, 2014 at 12:53 PM, jdoe <[email protected]>wrote:
>>>>
>>>>> ... wow, ok  - here we go :)
>>>>>
>>>>> re 0) - a workaround is working now staging the process based on your
>>>>> earlier 'forwarding' suggestion, i.e.  [if condition]<(forward some.page)>
>>>>> [if]   ...so thanks for that one.
>>>>>
>>>>> re 1) - Instead of a customised link (which does work, of course) I
>>>>> actually intended the user to use the regular 'print' link in the standard
>>>>> menu (like he would for any other page). - But when going that route,
>>>>> $_POST & $_GET specs tagged to the original page call are lost.
>>>>>
>>>>> re 2) - data-lightbox={+p} indeed is intended to tag the image for a
>>>>> nice javascript-based display handler. I added the tag to the img 
>>>>> attribute
>>>>> as suggested, but when looking at the source output, this is still not
>>>>> being rendered.  (it should be a simple concept, though - here is the link
>>>>> to the js in case this is of interest:  lokeshdhakar.com/projects/
>>>>> *lightbox2*
>>>>>
>>>>> re 3) - works as suggested - thanks :)
>>>>>
>>>>> Thanks & regards,
>>>>> JF
>>>>>
>>>>>
>>>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "BoltWire" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>>
>>> Visit this group at http://groups.google.com/group/boltwire.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "BoltWire" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/boltwire.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/boltwire.
For more options, visit https://groups.google.com/d/optout.

Reply via email to