Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

Hi *,

On Tue, May 24, 2011 at 7:14 PM, Charles-H. Schulz
<> wrote:
Le Tue, 24 May 2011 17:07:14 +0200,
Christian Lohmaier <> a écrit :

2. someone building the backend for the call for papers,
i.e. a form where people can enter their data, and it will be
e-mailed somewhere

(not published yet, so you can only see it with corresponding
permissions for the conference site) no pretty-printing or stuff yet,
just a working form.

So if you don't want any backend management, i.e. if just receiving
the submissions via mail/storing them in the cms unaltered is enough,
then all can be done without touching php-code.

I think it should be enough.

So then what alias or explicit addresses shall incoming messages be sent to?
You have the choice between full notification (i.e. including all the
form data, including the attachment), or just "there has been a
submission" type notification (where you have to go to the Submissions
tab within the CMS to see what has been submitted)

If it is considered to be a problem that the submissions (the
submitted files) are available to  anyone knowing the filename
(uploaded files are stored to assets/Upload), then the upload-folder
must be changed and restricted accordingly.


Unsubscribe instructions: E-mail to
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.