[file name=code_original.txt size=15569]http://www.chronoengine.com/components/com_fireboard/uploaded/files/code_original.txt[/file]
First Steps:
Installation, no issues in to RC3 J1.5!😉 - always a good start.
We have minor layout bug in the backend - the words 'form manager' split on the line incorrectly when the its not full screen
As I have very little coding experience I have opted to use
woofu to create my forms with valid css and layout etc.
I have found it to be dead easy - however the free account has a limitation of 10 questions per form, and three forms. I have sent an email asking if there are options I can use that will let me mock up long forms, but not use the backend :whistle: - we will see, I don't mind paying a fee, but paying a monthly fee for occasional changes will be a bind - I guess I can just delete a form, and change queries, then try to merge the code ? But that will be a pain for colour changes and ad-hoc question chages - of which I expect many.
Anyhow, my first foray has led to the following (very basic) form, which will be the basis for the questions that everybody gets (as opposed to class or archetype, see the link in the orignal post):
Application Form
I have made some very minor code changes however.
(note: in woofu you can view the code, I simply copy pasted this into the 'form code' in the 'form:html' area - the rest of the fields were filled in logically, the submit value for woofu code is indeed 'Submit()')
Firsly the instructions pop up dialogue box ran 'over the top' of my side modules - ugh.
So off to fix it!
After trying to change several random values I discovered that:
form .instruct{
position:absolute;
top:0;
left:60%;
z-index:1000;
width:35%;
margin:0 0 0 8px;
padding:8px 10px 9px 10px;
border:1px solid #e6e6e6;
background:#f5f5f5;
line-height:130%;
font-size:80%;
color:#444;
visibility:hidden;
}
Controlled the position and the width of the 'pop up instructions'. Changeing the values 'left:100%;' to 60% move it left (doh!) and 'width:42%;' to 35% gave me the position and width I needed.
So how well did it work ?
Firslt, lets look at the email - no issues sending, however the first recieved email looked like this:
Field0 Mr
Field1 Test
Field4-1 16
Field4-2 08
Field4 1976
Field5 UK
Field16 Mizpah
Field17 0
Field11 Guardian
Field12 Aquilonian Working, but as clear as mud! :blink: - Mainly due to the field names!
However this is not a chronoform issue, but connected with the names embedded in the code. After some searching I found the following:
<label class="desc" id="title0" for="Field0">
Name:
<span id="req_0" class="req">*</span>
</label>
<span>
<input id="Field0"
name="Field0"
class="field text" size="8"
tabindex="1"
value="" />
<label for="Field0">First</label>
</span>
Which after some testing, became:
<label class="desc" id="name" for="name">
Name:
<span id="req_0" class="req">*</span>
</label>
<span>
<input id="name_first"
name="name_first"
class="field text" size="8"
tabindex="1"
value="" />
<label for="name_first">First</label>
</span>
Of course I tested this before changing all of the field references, but applying this logic across the board, gives me the following email:
name_first Martin
name_surname Dean
dob_mm 08
dob_dd 16
dob_yyyy 1976
country UK
char_name Mizpah
char_level 1
class Guardian
Field12
char_race Stygan
Note the 'extra' field 12 (which is char_race) ? This seems to be connected with radio buttons, will deal with this later!
For anyone playing with this, I have attached the original, woofu code, as a .txt files! I will post the modified code in another thread!
Next post, getting it into the database!
Post edited by: Mizpah, at: 2007/11/19 01:07<br><br>Post edited by: Mizpah, at: 2007/11/19 01:12