CMS Made Simple Forums

I've encountered a few issues tryng to get FeedbackForm working on my site. My configuration is:
RedHat 9 Linux
Apache 1.3.33 (Unix)
PHP 4.3.11 (apache)
MySQL 4.0.25
CMSMS 0.11.2
FeedbackForm 0.9.10
CMSMailer 1.73.9

These are the issues I've got:

• I've been using an "Email Results Based on Pulldown" disposition, but I'm not getting the result I expected. The email is sent OK, but the template vriable for the pulldown field isn't output in the email - all that's output is the variable name ($subject_of), not the value.
• I tried using a check box field, with a field name "Tick here if...video?" The template variable for this field was only output if the box was checked - otherwise just the variable name was output ($tick_here). But it works OK if I change the field name so that it doesn't end with a "?" character!
• The field order buttons don't always work. Some fields become impossible to move up and down, while others can be reordered successfully. I haven't been able to spot a pattern so far!

It's the email dispositon field value problem that's really an issue for me at the moment, so I'd be really grateful to hear of a solution!

At the moment the feedback form seems to have problems with special chars as for example the german ä, ö, ü and ß. I think the problem with the "?" goes in the same direction. As no real alternative exists, I´m using at the moment the good old formmail.cgi with a handmade form realized as global_content. It´s not really an alternative to the modul, but it works and that´s important for me.

Greats Larry

PePiPoo wrote:
These are the issues I've got:

• The field order buttons don't always work. Some fields become impossible to move up and down, while others can be reordered successfully. I haven't been able to spot a pattern so far!

I'll have to say this problem happens to me as well. Random fields cannot be reordered, it remains where it is after the 'up' or 'down' button is clicked. No errors returned.

Otherwise I'll have to say this module really rocks! Beats lots of commercial offerings that I've came across for it's flexibility, control and ease of use.

Will database support as a form handling input be a possible option anytime soon? 

zcysr wrote:

PePiPoo wrote:
These are the issues I've got:

• The field order buttons don't always work. Some fields become impossible to move up and down, while others can be reordered successfully. I haven't been able to spot a pattern so far!

I'll have to say this problem happens to me as well. Random fields cannot be reordered, it remains where it is after the 'up' or 'down' button is clicked. No errors returned.

Otherwise I'll have to say this module really rocks! Beats lots of commercial offerings that I've came across for it's flexibility, control and ease of use.

Will database support as a form handling input be a possible option anytime soon? 

The form field ordering issue is a known bug. It can be fixed by editing the field order in the database directly. If you do a search here you'll turn up my post of a week or two ago and sjg's reply telling exactly how to go about solving the problem.

Ah, threads like this pain me 

I'm getting really close to putting FormBuilder up for beta testing. I thought I'd have a release by now, but I'm just slammed with deadlines at work, and then I got a cold. Regardless, FormBuilder is going to be ready soon. I know I've said that before. I apologize for all the delays.

The new FormBuilder will solve the reordering problem. But I'm not sure about the foreign character problem. Maybe someone here can offer some suggestions.

Here's the deal. In FormBuilder, the field names won't be as important as they are in FeebackForm. An internal representation will be used for creating the field names inside the forms themselves. But when you build your templates for sending the email or whatever, you'll need to name the forms using smarty tags.

I haven't been able to get smarty to accept tags that have characters with umlauts or even punctuation symbols. It claims, in the documentation, to honor the locale when it decides what are valid characters for tags. But I haven't been able to get that to work. So what I do is replace all characters that match the regular expression \W with an underscore.

This will mean that you'll be able to use field names with arbbitrary characters in them, but when you create a field named "grüß!" for example, you'll need to identify it in your smarty template as "{$gr___}".

Is that going to be acceptable? Any suggestions on how to improve that?

Thanks,
___Samuel___

I think that´s the best possibility you have. Hoping for a release to test

Greats from Germany
LeisureLarry