WBCE CMS – Way Better Content Editing.
Du bist nicht angemeldet.
We have ported our module FR Forms for use in WBCE and are pleased to make it available to WBCE users.
We initially developed FR Forms for our own use, for a different platform. We believe it is very important for end users to have sufficient, user-friendly customisation options. That is why FR Forms has been built with five pre-installed front-end layouts, and the rest can be customised as required. Put together your own set of data fields and design your own email templates using WBCE’s WYSIWYG editor.
Incoming messages and replies can be saved as required.
Available module languages: Dutch, English and German. Built-in link to our wiki pages for up-to-date help.
Offline
Mighty module.
The visual editor is great, also the WYSIWYG email template editor.
But...
There's a small design flaw in the backend - see attached screenshot.
Afaics there's no output of the placeholder text in nice form / Bootstrap output template.
Danger zone: When there's no answer template configured, or the answer template lacks the placeholders for the form fields, and the "Formulareinsendungen in der Datenbank speichern" checkbox is unset (which is the default setting), you can create forms which are able to be sent succesful - into nirvana. This should not be possible. E-Mail configuration status is misleading in that case.
Questions:
Creating multiple choice fields (like input type="radio" yes / no, input type="checkbox" value 1 / value 2/ value 3, select option 1, option 2 etc.) is not possible?
Feature wishes:
export/import forms (fielsets) and email templates to re-use them on several pages without creating them every time from the scratch.
export submitted form enties as CSV
address the FR form page in the frontend and pre-fill text fields via URL parameter, e.g. example-form.php?field=value
Beitrag geändert von florian (11.10.2026 17:31:02)
Wir Benötigen: Cents, Euros... jetzt spenden!
Offline
Thanks for the feedback!
We'll get to work on it.
Offline
florian
Afaics there's no output of the placeholder text in nice form / Bootstrap output template.
https://forum.wbce.org/attachment.php?i … download=1
Can you tell us which browser and which front-end template you were using when you encountered this issue?
We haven't been able to reproduce the issue, not even with the WBCEtik front-end template.
When we edit your screenshot in GIMP, we see white text on a nearly white background. We'd like to fix this, but we're still trying to pinpoint the exact cause.
Offline
You're right. The invisible placeholder text is an issue with the WBCEZon template. Sorry for the confusion.
Wir Benötigen: Cents, Euros... jetzt spenden!
Offline
Danger zone: When there's no answer template configured, or the answer template lacks the placeholders for the form fields, and the "Formulareinsendungen in der Datenbank speichern" checkbox is unset (which is the default setting), you can create forms which are able to be sent succesful - into nirvana. This should not be possible. E-Mail configuration status is misleading in that case.
https://forum.wbce.org/attachment.php?i … download=1
Unfortunately, our carrier pigeons don't fly very far... We'll fix it as soon as possible.
As for the wish list, we'll include as much of it as possible right away.
Offline
florian
You're right. The invisible placeholder text is an issue with the WBCEZon template. Sorry for the confusion.
Thanks!
No problem
Offline
Since we originally developed FR Forms for our own use, it turns out that testing was done more along the lines of a “happy path”. So it’s great that you took a different approach, that’s something for us to keep in mind.
We can definitely implement the requested features, we see the value in them, so we’ll include them. And of course, the bug fixes (they’ve already been resolved; now we just need to test them thoroughly).
To be continued...
Beitrag geändert von ferrik (12.10.2026 07:54:53)
Offline
You're right. The invisible placeholder text is an issue with the WBCEZon template. Sorry for the confusion.
Your feedback is certainly valid.
The WBCEZon theme sets the placeholder text to white; see lines 192–194:
::placeholder {color:#fff;}
:-ms-input-placeholder {color:#fff;}
::-ms-input-placeholder {color:#fff;}
Our solution will be to lock the colour of the placeholder text so that no template can affect it.
Offline
florian
Seiten: 1