File Manager
<?php
$lang['friendlyname'] = 'Form Builder';
$lang['field_type_'] = 'Field Type Not Set';
$lang['field_type_CatalogerItemsField'] = 'Select one (or more) cataloger items';
$lang['field_type_FieldsetEnd'] = '-Fieldset End';
$lang['field_type_FieldsetStart'] = '-Fieldset Start';
$lang['field_type_TextField'] = 'テキスト';
$lang['field_type_TextFieldExpandable'] = 'テキスト (複数)';
$lang['field_type_TextAreaField'] = 'テキストエリア';
$lang['field_type_CheckboxField'] = 'チェックボックス';
$lang['field_type_CheckboxGroupField'] = 'チェックボックス・グループ';
$lang['field_type_PulldownField'] = 'プルダウン';
$lang['field_type_MultiselectField'] = '複数選択';
$lang['field_type_StatePickerField'] = 'U.S. State Picker';
$lang['field_type_ProvincePickerField'] = 'Canadian Province Picker';
$lang['field_type_CountryPickerField'] = 'Country Picker';
$lang['field_type_DatePickerField'] = 'Date Picker';
$lang['field_type_TimePickerField'] = 'Time Picker';
$lang['field_type_RadioGroupField'] = 'Radio Button Group';
$lang['field_type_DispositionDirector'] = '*Email Results Based on Pulldown';
$lang['field_type_DispositionFileDirector'] = '*Save Results to File Based on Pulldown';
$lang['field_type_DispositionMultiselectFileDirector'] = '*Save Results to File(s) Based on Multiple Selections';
$lang['field_type_DispositionPageRedirector'] = '*Redirect to Page Based on Pulldown';
$lang['field_type_DispositionEmail'] = '*Email Results to set Address(es)';
$lang['field_type_DispositionEmailConfirmation'] = '*Validate-via-Email Address';
$lang['field_type_DispositionFile'] = '*Write Results to Flat File';
$lang['field_type_DispositionDatabase'] = '*Store Results in Database';
$lang['field_type_DispositionFormBrowser'] = '*Store Results for FormBrowser Module v.3';
$lang['field_type_DispositionUserTag'] = '*Call A User Defined Tag With the Form Results';
$lang['field_type_DispositionDeliverToEmailAddressField'] = '*Email to User-Supplied Email Address';
$lang['field_type_DispositionEmailSiteAdmin'] = '*CMS Admin Userへメールする';
$lang['field_type_PageBreakField'] = '-Page Break';
$lang['field_type_FileUploadField'] = 'ファイルアップロード';
$lang['field_type_FromEmailAddressField'] = 'メールの "From Address" 項目';
$lang['field_type_FromEmailNameField'] = 'メールの "From Name" 項目';
$lang['field_type_FromEmailSubjectField'] = 'メールの "Subject" 項目';
$lang['field_type_StaticTextField'] = '- 静的テキスト';
$lang['field_type_SystemLinkField'] = '- 静的リンク';
$lang['field_type_LinkField'] = 'リンク (User-entered)';
$lang['field_type_HiddenField'] = '- 非表示項目';
$lang['field_type_ComputedField'] = '- Computed Field';
$lang['field_type_UniqueIntegerField'] = '-Unique Integer (Serial)';
$lang['validation_none'] = '入力チェックなし';
$lang['validation_numeric'] = '数値';
$lang['validation_integer'] = 'Integer';
$lang['validation_email_address'] = 'メールアドレス';
$lang['validation_usphone'] = '電話番号 (US)';
$lang['validation_must_check'] = '必須チェック';
$lang['validation_regex_match'] = 'Match Regular Expression';
$lang['validation_regex_nomatch'] = 'Doesn\'t match Regular Expression';
$lang['required_field_missing'] = 'A value was not supplied for a required field';
$lang['please_enter_a_value'] = 'Please enter a value for "%s"';
$lang['please_enter_a_number'] = 'Please enter a number for "%s"';
$lang['please_enter_valid'] = 'Please enter a valid entry for "%s"';
$lang['please_enter_an_integer'] = 'Please enter an integer value for "%s"';
$lang['please_enter_an_email'] = 'Please enter a valid email address for "%s"';
$lang['please_enter_a_phone'] = 'Please enter a valid phone number for "%s"';
$lang['not_valid_email'] = '"%s" does not appear to be a valid email address!';
$lang['please_enter_no_longer'] = 'Please enter a value that is no longer than %s characters';
$lang['title_list_delimiter'] = 'Character to use as delimiter in results that return more than one value';
$lang['you_need_permission'] = 'You need the "%s" permission to perform that operation.';
$lang['lackpermission'] = 'Sorry! You don\'t have adequate privileges to access this section.';
$lang['field_order_updated'] = 'Field order updated.';
$lang['form_deleted'] = 'フォームを削除しました。';
$lang['field_deleted'] = '項目を削除しました。';
$lang['configuration_updated'] = '設定情報を更新しました。';
$lang['you_must_check'] = 'You must check "%s" in order to continue.';
$lang['must_specify_one_destination'] = 'You need to specify at least one destination address!';
$lang['are_you_sure_delete_form'] = 'Are you sure you want to delete the form %s?';
$lang['are_you_sure_delete_field'] = 'Are you sure you want to delete the field %s?';
$lang['notice_select_type'] = 'Advanced options are not available until the field type has been set.';
$lang['field_name_in_use'] = 'The field name "%s" is already in use. Please use unique field names, or disable unique field names in the Form Builder configuration.';
$lang['field_no_name'] = 'Fields must be named, unless you disable this in the Form Builder configuration.';
$lang['anonymous'] = 'Anonymous';
$lang['abbreviation_length'] = '長さ: %s';
$lang['boxes'] = '%s boxes';
$lang['options'] = '%s options';
$lang['text_length'] = '%s chars.';
$lang['order'] = 'Order';
$lang['unspecified'] = '[unspecified]';
$lang['added'] = '追加しました。';
$lang['updated'] = '更新しました。';
$lang['sort_options'] = 'Sort options on output';
$lang['select_one'] = 'ひとつを選択';
$lang['select_type'] = 'Select Type';
$lang['to'] = 'To';
$lang['yes'] = 'はい';
$lang['no'] = 'いいえ';
$lang['recipients'] = 'recipients';
$lang['file_count'] = '%s possible files';
$lang['destination_count'] = '%s destinations';
$lang['save'] = '保存';
$lang['add'] = '追加';
$lang['update'] = '更新';
$lang['save_and_continue'] = '保存し、編集を続ける';
$lang['information'] = '情報';
$lang['automatic'] = 'Automatic';
$lang['forms'] = 'Forms';
$lang['form'] = 'Form %s';
$lang['configuration'] = '設定情報';
$lang['field_requirement_updated'] = 'Field required state updated.';
$lang['maximum_size'] = '最大サイズ';
$lang['permitted_extensions'] = 'Extensions';
$lang['permitted_filetypes'] = 'Allowed file types';
$lang['file_too_large'] = 'Uploaded file is too large! Maximum size is:';
$lang['illegal_file_type'] = 'This type of file may not be uploaded. Please check that the extension is correct.';
$lang['upload'] = 'アップロード';
$lang['form_imported'] = 'Form Imported.';
$lang['form_import_failed'] = 'Form import failed! There was a problem with the format of the XML file.';
$lang['rows'] = '%s 行';
$lang['cols'] = '%s 列';
$lang['12_hour'] = '12時間表示';
$lang['24_hour'] = '24時間表示';
$lang['hour'] = '時';
$lang['min'] = '分';
$lang['merid'] = 'Meridian';
$lang['date_range'] = '範囲: %s - %s';
$lang['thanks'] = 'Thanks! Your submissions have been received.';
$lang['edit'] = '編集';
$lang['delete'] = '削除';
$lang['day'] = '日';
$lang['mon'] = '月';
$lang['year'] = '念';
$lang['none'] = '(なし)';
$lang['uninstalled'] = 'モジュールをアンインストールしました。';
$lang['installed'] = 'Module version %s installed.';
$lang['upgraded'] = 'Module upgraded to version %s.';
$lang['button_previous'] = '戻る...';
$lang['button_submit'] = 'Submit Form';
$lang['button_continue'] = '続ける...';
$lang['value_checked'] = 'チェック';
$lang['value_unchecked'] = '非チェック';
$lang['tab_main'] = 'メイン';
$lang['tab_symbol'] = 'フォームの表示設定';
$lang['tab_submit'] = 'Form Submission';
$lang['tab_captcha'] = 'Captcha設定';
$lang['tab_advanced'] = 'Advanced Settings';
$lang['tab_templatelayout'] = 'フォーム・テンプレート';
$lang['tab_submissiontemplate'] = 'Submission Template';
$lang['canuse_smarty'] = '<em>Smarty variables are valid in this field.</em>';
$lang['add_options'] = 'オプションを追加';
$lang['delete_options'] = '選択したオプションを削除';
$lang['add_checkboxes'] = 'チェックボックスを追加';
$lang['delete_checkboxes'] = '選択したチェックボックスを削除';
$lang['add_address'] = 'Add Another Address';
$lang['delete_address'] = 'Delete Marked Addresses';
$lang['add_destination'] = 'Add Another Destination';
$lang['delete_destination'] = 'Delete Marked Destinations';
$lang['suspected_spam'] = 'Too many emails generated from your IP address. Anti-Spam code has prevented delivery.';
$lang['suspected_spam_log'] = 'Suspected spam from IP %s stopped.';
$lang['reorder'] = 'Reorder Fields';
$lang['cancel'] = 'キャンセル';
$lang['value_set'] = 'Value set: %s';
$lang['help_cataloger_attribute_fields'] = 'Below is a list of the attributes available from the Cataloger module.<br/>You can optionally specify valid ranges, values, or numerous values to be used in filtering the list of items that is displayed to the user.<br/>
<br/>
<strong>Ranges:</strong><br/>
Ranges can be specified by signifying a minimum and maximum value using this syntax: "range: minvalue to maxvalue"<br/>
<br/>
<strong>Multiple Values:</strong><br/>
To specify multiple values for an attribute use the syntax "multi: value1|value2|value3"<br/>
<br/>
<strong>Values from hidden fields</strong><br/>
To specify a value from a hidden field use the syntax {$fld_id}<br/>
<br/>';
$lang['help_name_regex'] = 'A regular expression to allow filtering cataloger items by name';
$lang['help_field_height'] = 'The height of the multiselect field';
$lang['title_name_regex'] = 'Cataloger Item Name Regular Expression';
$lang['title_field_height'] = '項目の高さ';
$lang['title_file_path'] = 'Destination Directory for output files';
$lang['title_udt_name'] = 'ユーザ定義タグ';
$lang['title_uploads_destpage'] = 'Page to return to with uploads link';
$lang['title_uploadmodule_summary'] = 'Submitted with formbuilder';
$lang['title_uploads_category'] = 'カテゴリのアップロード';
$lang['title_sendto_uploads'] = 'Send this file to the uploads module';
$lang['title_legend'] = 'Legend';
$lang['title_maximum_length'] = '最大長';
$lang['title_checkbox_label'] = 'チェックボックス・ラベル';
$lang['title_radio_label'] = 'ラジオボタン・ラベル';
$lang['title_checked_value'] = 'Value when checked';
$lang['title_unchecked_value'] = 'Value when not checked.';
$lang['title_checkbox_details'] = 'Checkbox Group Details';
$lang['title_delete'] = '削除しますか？';
$lang['title_select_one_message'] = '"Select One" Text';
$lang['title_selection_value'] = 'Selection Value';
$lang['title_selection_displayname'] = 'Selection Display Name';
$lang['title_selection_subject'] = 'Selection Subject';
$lang['title_select_default_country'] = 'Default Selection';
$lang['title_select_default_state'] = 'Default Selection';
$lang['title_select_default_province'] = 'Default Selection';
$lang['title_option_name'] = 'Option Name';
$lang['title_option_value'] = 'Value Submitted';
$lang['title_pulldown_details'] = 'Pulldown Options';
$lang['title_multiselect_details'] = 'Multiselect Options';
$lang['title_destination_address'] = 'Destination Email Address';
$lang['title_destination_filename'] = 'Destination File Name';
$lang['title_email_from_name'] = '"From name" for email';
$lang['title_relaxed_email_regex'] = 'Use relaxed email validation';
$lang['title_relaxed_regex_long'] = 'Use relaxed email address validation (e.g., allow "x@y" instead of requiring "x@y.tld")';
$lang['title_email_from_address'] = 'メールの"From address"';
$lang['title_email_encoding'] = 'Email character set encoding';
$lang['title_director_details'] = 'Pulldown-based Emailer Details';
$lang['title_file_name'] = 'ファイル名';
$lang['title_email_subject'] = 'メールサブジェクト名';
$lang['title_form_name'] = 'フォーム名';
$lang['title_form_status'] = 'フォームステータス';
$lang['title_ready_for_deployment'] = 'デプロイできます。';
$lang['title_not_ready1'] = 'デプロイできません。';
$lang['title_redirect_page'] = 'Page to redirect to after form submission';
$lang['title_not_ready2'] = 'Please add a field to the form so that the user\'s input gets handled. You can';
$lang['title_not_ready_link'] = 'use this shortcut';
$lang['title_form_alias'] = 'フォームエイリアス';
$lang['title_form_fields'] = 'フォーム項目';
$lang['title_field_id'] = '項目ID';
$lang['title_show_fieldaliases'] = 'Show Field Aliases';
$lang['title_show_fieldaliases_long'] = 'Clicking this will display field aliases when adding or editing a form';
$lang['title_field_name'] = '項目名';
$lang['title_field_alias'] = '項目エイリアス';
$lang['title_radiogroup_details'] = 'Radio Button Group Details';
$lang['title_field_type'] = '項目型';
$lang['title_not_ready3'] = 'to create a form handling field.';
$lang['title_add_new_form'] = 'フォームの追加';
$lang['title_show_version'] = 'Show Form Builder Version?';
$lang['title_show_version_long'] = 'This will embed your installed version number of Form Builder module in a comment, to aid in debugging';
$lang['title_add_new_field'] = '項目の追加';
$lang['title_form_submit_button'] = 'Form Submit Button Text';
$lang['title_submit_button_safety'] = 'Add Javascript to final Submit Button that will help prevent multiple submissions?';
$lang['title_submit_button_safety_help'] = 'Add safety script';
$lang['title_form_next_button'] = 'Form "Next" Button Text (used for multipage forms)';
$lang['title_form_prev_button'] = 'Form "Previous" Button Text (used for multipage forms)';
$lang['title_field_validation'] = '項目の入力チェック';
$lang['title_form_css_class'] = 'CSS Class for this form';
$lang['title_field_css_class'] = 'CSS Class for this field';
$lang['title_form_required_symbol'] = 'Symbol to mark required Fields';
$lang['title_field_required'] = '必須';
$lang['title_field_required_long'] = 'Require a response for this Field';
$lang['title_hide_label'] = '非表示ラベル';
$lang['title_hide_label_long'] = 'Hide this field\'s name on Form';
$lang['title_text'] = 'Static text to display';
$lang['title_field_regex'] = 'Validation Regex';
$lang['title_lines_to_show'] = '行番号を表示';
$lang['no_default'] = 'No Default';
$lang['redirect_after_approval'] = 'Page to redirect after approval';
$lang['title_regex_help'] = 'This regular expression will only be used if "validation type" is set to a regex-related option. Include a full Perl-style regex, including the start/stop slashes and flags (e.g., "/image\\.(\\d+)/i")';
$lang['title_field_required_abbrev'] = 'Req\'d';
$lang['title_hide_errors'] = 'エラーを非表示';
$lang['title_form_displaytype'] = 'Form Display Type';
$lang['title_hide_errors_long'] = 'Prevent debug / error messages from being seen by users.';
$lang['title_email_template'] = 'メールテンプレート';
$lang['title_maximum_size'] = 'Maximum upload file size (kilobytes)';
$lang['title_maximum_size_long'] = 'This limitation is in addition to any limits set by the php or web server configuration';
$lang['title_permitted_extensions'] = 'Permitted Extensions';
$lang['title_permitted_extensions_long'] = 'Enter a comma-separated list, excluding the dot (e.g., "jpg,gif,jpeg"). Spaces will be ignored. Leaving this blank means there will be no restrictions.';
$lang['title_show_limitations'] = 'Display restrictions?';
$lang['title_show_limitations_long'] = 'Display any size and extension restrictions with the upload field?';
$lang['title_form_template'] = 'Template to use to Display Form';
$lang['title_page_x_of_y'] = 'Page %s of %s';
$lang['title_no_advanced_options'] = 'Field has no advanced options.';
$lang['title_form_unspecified'] = 'Text to return for unspecified field values';
$lang['title_enable_fastadd_long'] = 'Enable fast field adding pulldown for forms?';
$lang['title_enable_fastadd'] = 'Enable fast field add pulldown?';
$lang['title_fastadd'] = 'Fast field adder';
$lang['title_enable_antispam_long'] = 'Clicking this will only allow 10 emails to be triggered from a given IP address (per hour).';
$lang['title_enable_antispam'] = 'Enable primitive anti-spam features?';
$lang['title_show_fieldids'] = '項目IDを見る';
$lang['title_show_fieldids_long'] = 'Clicking this will allow displaying field ids when adding or editing a form';
$lang['title_xml_to_upload'] = 'Upload form from XML file';
$lang['title_xml_upload_formname'] = 'Use this form name';
$lang['title_import_legend'] = 'XMLフォームのインポート';
$lang['title_xml_upload_formalias'] = 'Use this form alias';
$lang['title_html_email'] = 'HTMLメールを作成しますか？';
$lang['title_link_autopopulate'] = 'Automatically populate?';
$lang['title_link_autopopulate_help'] = 'Automatically populate with the URL of the page containing the form? (this overrides site page link option below)';
$lang['title_default_link'] = 'デフォルトリンクURL';
$lang['title_default_link_title'] = 'デフォルトリンクテキスト';
$lang['title_link_to_sitepage'] = 'Link to site page';
$lang['title_captcha_not_installed'] = 'You can use <a href="http://www.wikipedia.org/wiki/Captcha" target="_new">"Captcha"</a> to protect form submissions if you install the Captcha module. For more information, <a href="http://dev.cmsmadesimple.org/projects/captcha/">check the Captcha project</a>.';
$lang['title_use_captcha'] = 'Use Captcha to protect form submissions?';
$lang['title_use_captcha_help'] = 'Check here to protect your form with a <a href="http://www.wikipedia.org/wiki/Captcha" target="_new">"Captcha"</a>.';
$lang['title_user_captcha'] = 'Please confirm that you are not a script by entering the letters from the image.';
$lang['title_user_captcha_error'] = 'Failed text for Captcha';
$lang['wrong_captcha'] = 'Captcha は利用できません。';
$lang['title_title_user_captcha'] = 'Help text for Captcha';
$lang['title_dont_submit_unchecked'] = 'Don\'t submit values for unchecked boxes';
$lang['title_dont_submit_unchecked_help'] = 'Check this if you only want checked boxes to return values.';
$lang['link_label'] = 'リンクラベル';
$lang['link_destination'] = 'Link Destination URL';
$lang['title_default_set'] = 'Checked by Default?';
$lang['title_24_hour'] = 'Use 24-hour clock?';
$lang['title_before_noon'] = '午前';
$lang['title_after_noon'] = '午後';
$lang['title_smarty_eval'] = 'Process smarty tags within field?';
$lang['title_textarea_rows'] = 'Rows (note: this may be overridden by CSS)';
$lang['title_textarea_cols'] = 'Columns (note: this may be overridden by CSS)';
$lang['title_form_main'] = 'Main Form Details';
$lang['title_show_username'] = 'Display User\'s login name?';
$lang['title_show_userfirstname'] = 'Display User\'s first name?';
$lang['title_show_userlastname'] = 'Display User\'s last name?';
$lang['title_restrict_to_group'] = 'Restrict user list to users in specified group';
$lang['restricted_to_group'] = 'Only in group %s';
$lang['title_show_to_user'] = 'Display to user?';
$lang['help_leaveempty'] = 'This field may be left empty';
$lang['help_variables_for_template'] = 'Variables For Template';
$lang['help_variables_for_computation'] = 'Variables Available';
$lang['help_php_variable_name'] = 'PHP variable';
$lang['help_submission_date'] = 'Date of Submission';
$lang['help_server_name'] = 'Your server';
$lang['help_sub_source_ip'] = 'IP address of person using form';
$lang['help_sub_url'] = 'URL of page containing form';
$lang['help_fb_version'] = 'FormBuilder version';
$lang['help_tab'] = 'Tab Character';
$lang['help_other_fields'] = 'Alternate field names can be used interchangeably (especially useful if Smarty is choking on characters outside of ASCII 32-126). <br />Other fields will be available as you add them to the form.';
$lang['help_array_fields'] = 'Yet another way of accessing field values is via $fieldname_obj, $alias_obj, or $fld_#_obj, where each field is an object containging:<br /><table>
<tr><td class="odd">name</td><td class="odd">Field Name</td></tr>
<tr><td>type</td><td>Field Type</td></tr>
<tr><td class="odd">id</td><td class="odd">Internal Field ID</td></tr>
<tr><td>value</td><td>Human-readable Value</td></tr>
<tr><td class="odd">valueArray</td><td class="odd">Array of field value(s)</td></tr></table><em>e.g.</em>, you could use "{$fld_1_obj->name} = {$fld_1_obj->value}';
$lang['help_date_format'] = 'See <a href="http://www.php.net/manual/en/function.date.php" target=_NEW>the PHP Manual</a> for formatting help.';
$lang['help_variable_name'] = 'Variable';
$lang['help_form_field'] = 'Field Represented';
$lang['link_back_to_form'] = '« フォームへ戻る';
$lang['title_create_sample_template'] = 'サンプルテンプレートの作成';
$lang['title_create_sample_html_template'] = 'サンプルHTMLテンプレートの作成';
$lang['title_create_sample_header'] = 'サンプルヘッダの作成';
$lang['help_tab_symbol'] = 'a tab character';
$lang['title_file_template'] = 'Template for one line of output file';
$lang['title_file_header'] = 'Template for the header of output file';
$lang['title_confirmation_url'] = 'URL to click for form confirmation';
$lang['title_value'] = 'Value (see Advanced Tab if you use Smarty tags)';
$lang['title_date_format'] = '日付型 (standard <a href="http://www.php.net/manual/en/function.date.php">PHP Date Formats</a>)';
$lang['title_use_wysiwyg'] = 'Use WYSIWYG editor for text Area (Admin side only)?';
$lang['title_submit_actions'] = 'Form Submission Behavior';
$lang['title_submit_labels'] = 'Submission Button Labels';
$lang['title_sortable_field'] = 'Sortable Field #%s';
$lang['title_submit_help'] = 'This page lets you customize Form Submission. It doesn\'t determine what the Form Builder does with the submitted data. You can set that up by adding "Disposition" fields to your form.';
$lang['title_start_year'] = '年の始まり';
$lang['title_end_year'] = '年の終わり';
$lang['title_default_year'] = 'デフォルト年';
$lang['title_default_year_help'] = '(Set to -1 for default year to be the current year)';
$lang['title_submit_action'] = 'After form is submitted';
$lang['title_submit_response'] = 'Response to display';
$lang['display_text'] = 'Display "Submission Template"';
$lang['redirect_to_page'] = 'サイトへリダイレクトする';
$lang['title_submit_response_help'] = 'This template is for display to the user after the form is submitted. This template does not effect emails generated or other form dispositions -- you set those templates (where appropriate) in the "advanced" tab for those disposition fields.';
$lang['title_destination_page'] = 'Destination Page';
$lang['title_require_fieldnames'] = '必須入力の項目名';
$lang['title_require_fieldnames_long'] = 'Require fields to have a name?';
$lang['title_unique_fieldnames'] = '必須入力、一意の項目名';
$lang['title_unique_fieldnames_long'] = 'Require fields to have unique names?';
$lang['title_reorder_form'] = 'Reorder Fields';
$lang['title_load_template'] = 'テンプレートの読み込み';
$lang['title_add_button_text'] = 'Add Button text';
$lang['title_del_button_text'] = 'Delete Button text';
$lang['title_string_or_number_eval'] = 'Interpret variables as being numbers or strings';
$lang['title_order'] = 'Interpretation Order';
$lang['title_order_help'] = 'If more than one Computed Field exists, they will be computed from lowest order number to highest order number';
$lang['title_compute_value'] = 'Value to compute';
$lang['title_string'] = '文字列';
$lang['title_numeric'] = '数値';
$lang['title_inline_form'] = 'Display form inline?';
$lang['title_inline_form_help'] = 'Inline means any form followup replaces the {cms_module} tag, non-inline replaces the {content} tag.';
$lang['title_field_default_value'] = 'Default value for field';
$lang['title_clear_default'] = 'Clear default on click?';
$lang['title_clear_default_help'] = 'Check this to clear the default value when the user clicks this field. Since this uses a javascript string compare, it will fail if you put single quotes in your default text. Other un-javascript-friendly characters may also cause it to fail.';
$lang['title_remove_file_from_server'] = 'Delete uploaded file from server after processing (email dispositions)';
$lang['title_field_javascript'] = 'Javascript for field';
$lang['title_field_javascript_long'] = 'Make this the complete Javascript call, including the event you want to trap, e.g., onclick="yourfn()"';
$lang['title_submit_javascript'] = 'Form Submission Javascript';
$lang['title_submit_javascript_long'] = 'Make this the complete Javascript call, including the event you want to trap, e.g., onclick="yourfn()".<br />This will probably not work well if you use the "safety script" option above.';
$lang['default_template'] = 'デフォルトテンプレート';
$lang['table_left_template'] = 'Table Template, Titles on left';
$lang['table_top_template'] = 'Table Template, Title on top';
$lang['form_template_name'] = 'テンプレートフォーム %s';
$lang['template_are_you_sure'] = 'Are you sure you want to overwrite your template with the selected template? (Even if you say OK, you will still need to save the change)';
$lang['title_bad_function'] = 'Error when computing "%s".';
$lang['no_referrer_info'] = 'No HTTP_REFERER info available (probably due to use of User Email Validation)';
$lang['validation_param_error'] = 'Validation Parameter Error. Please make sure you copy the URL from your email correctly!';
$lang['validation_response_error'] = 'Validation Repsonse Error. Please make sure you copy the URL from your email correctly!';
$lang['validation_no_field_error'] = 'Validation Repsonse Error. No email validation field in this form!';
$lang['upgrade03to04'] = 'Form Template was updated automatically as part of the version 0.3 to version 0.4 upgrade. You may need to make some fixes. If you\'re using the default form, simply replace this template with "default" using the pulldown above.';
$lang['admindesc'] = 'Add, edit and manage interactive Forms';
$lang['operators_help'] = 'If you use String evaluation, the only operation available is concatenation (+), while if you use Number evaluation you have basic, very simple math (, +, -, *, /, ).';
$lang['date_january'] = '1月';
$lang['date_february'] = '2月';
$lang['date_march'] = '3月';
$lang['date_april'] = '4月';
$lang['date_may'] = '5月';
$lang['date_june'] = '6月';
$lang['date_july'] = '7月';
$lang['date_august'] = '8月';
$lang['date_september'] = '9月';
$lang['date_october'] = '10月';
$lang['date_november'] = '11月';
$lang['date_december'] = '12月';
$lang['submission_error'] = 'Sorry! There was an error handling your form submission.';
$lang['submit_error'] = 'FormBuilder submit error: %s';
$lang['uploads_error'] = 'Error committing file to the uploads module: %s';
$lang['nouploads_error'] = 'Could not find the uploads module';
$lang['upload_attach_error'] = 'Upload/Attachment error on file %s (tmp_name: %s, of type %s)';
$lang['submission_error_file_lock'] = 'Error. Unable to obtain lock for file.';
$lang['unchecked_by_default'] = 'デフォルト: 非チェック';
$lang['checked_by_default'] = 'デフォルト: チェック';
$lang['email_default_template'] = 'FormBuilder Submission';
$lang['email_template_not_set'] = '<br/>Email Template not yet set!';
$lang['missing_cms_mailer'] = 'FormBuilder: Cannot find required module CMSMailer!';
$lang['user_approved_submission'] = 'User approved submission %s from %s';
$lang['event_info_OnFormBuilderFormSubmit'] = 'Event triggered when a FormBuilder form is submitted';
$lang['event_info_OnFormBuilderFormSubmitError'] = 'Event triggered if there is an error when a FormBuilder form is submitted';
$lang['event_info_OnFormBuilderFormDisplay'] = 'Event triggered when a FormBuilder form is displayed';
$lang['event_help_OnFormBuilderFormSubmit'] = '<p>Event triggered when a FormBuilder form is submitted.</p>
<h4>Parameters</h4>
<ul>
<li><em>form_name</em> - The form name (string)</li>
<li><em>form_id</em> - The internal form id (int)</li>
<li><em>value_<name></em> - Supply a default value to a field with the specified name.</li>
</ul> ';
$lang['event_help_OnFormBuilderFormSubmitError'] = '<p>Event triggered if there is an error when a FormBuilder form is submitted</p>
<h4>Parameters</h4>
<ul>
<li><em>form_name</em> - The form name (string)</li>
<li><em>form_id</em> - The internal form id (int)</li>
<li><em>error</em> - A list of all known errors (string)</li>
</ul> ';
$lang['event_help_OnFormBuilderFormDisplay'] = '<p>Event triggered when a FormBuilder form is displayed</p>
<h4>Parameters</h4>
<ul>
<li><em>form_name</em> - The form name (string)</li>
<li><em>form_id</em> - The internal form id (int)</li>
</ul> ';
$lang['formbuilder_params_response_id'] = 'Response ID. Used by FormBrowser';
$lang['formbuilder_params_passed_from_tag'] = 'Default field values; see module help';
$lang['formbuilder_params_field_id'] = 'Field ID for internal operations';
$lang['formbuilder_params_form_name'] = 'フォーム名';
$lang['formbuilder_params_form_id'] = 'Form ID for internal operations';
$lang['formbuilder_params_general'] = 'General parameters for internal operations';
$lang['template_variable_help'] = '<h3>Form Template Variables</h3>
<p>You can edit it to make your form layout look any way you\'d like.
To make the form work, you\'ll need to always include the {$fb_hidden} and {$submit}
tags.</p>
<p>You can access your form fields either using the $fields array or by directly accessing fields by their names (e.g., {$myfield->input} )</p>
<p>Each field has the following attributes:</p>
<table>
<tr><th>Field</th><th>Value</th></tr>
<tr><td>field->display</td><td>1 if the field should be displayed, 0 otherwise</td></tr>
<tr><td>field->required</td><td>1 if the field is required, 0 otherwise</td></tr>
<tr><td>field->required_symbol</td><td>the symbol for required fields</td></tr>
<tr><td>field->css_class</td><td>the CSS class specified for this field</td></tr>
<tr><td>field->valid</td><td>1 if this field has passed validation, 0 otherwise</td></tr>
<tr><td>field->error</td><td>Text of the validation problem, in the event that this field did not validate</td></tr>
<tr><td>field->hide_name</td><td>1 if the field name should be hidden, 0 otherwise</td></tr>
<tr><td>field->has_label</td><td>1 if the field type has a label</td></tr>
<tr><td>field->needs_div</td><td>1 if the field needs to be wrapped in a DIV (or table row, if that\'s the way you swing)</td></tr>
<tr><td>field->name</td><td>the field\'s name</td></tr>
<tr><td>field->input</td><td>the field\'s input control (e.g., the input field itself)</td></tr>
<tr><td>field->op</td><td>a control button associated with the field if applicable (e.g., the delete button for expandable text input)</td></tr>
<tr><td>field->input_id</td><td>the ID of the field\'s input (useful for <label for="">)</td></tr>
<tr><td>field->type</td><td>the field\'s data type</td></tr>
<tr><td>field->multiple_parts</td><td>1 if the field->input is actually a collection of controls</td></tr>
<tr><td>field->label_parts</td><td>1 if the collection of controls has separate labels for each control</td></tr>
</table>
<p>In certain cases, field->input is actually an array of objects rather than an input. This happens, for example, in CheckBoxGroups or RadioButtonGroups. For them, you can iterate through field->input->name and field->input->inputs.</p>
<p>Additional smarty variables that you can use include:</p>
<table>
<tr><th>Variable</th><th>Value</th></tr>
<tr><td>total_pages</td><td>number of pages for multi-page forms</td></tr>
<tr><td>this_page</td><td>number fo the current page for multi-page forms</td></tr>
<tr><td>title_page_x_of_y</td><td>displays "page x of y" for multi-page forms</td></tr>
<tr><td>css_class</td><td>CSS Class for the form</td></tr>
<tr><td>form_name</td><td>Form name</td></tr>
<tr><td>form_id</td><td>Form database ID</td></tr>
<tr><td>prev</td><td>"Back" button for multipart forms</td></tr>
<tr><td>submit</td><td>"Continue" or "Submit" button for multipart forms, adjusts automatically</td></tr>
</table>
<p>Dunno why you\'d want some of those, but there you go...</p>
';
$lang['post_install'] = '<p>Make sure to set the "Modify Forms" permissions
on users who will be administering feedback forms. Also, if you\'ll be emailing form
results, be sure to update the Configuration appropriately.</p>
<p>Please be aware that a feedback form should not be active (e.g., usable by the public) while
you are still editing the form. You should create the form, and place the tag into an active
content page only when you have finished editing. Otherwise, erroneous results could be returned.</p>
<p>Additionally, this version does not support parallel editing of forms. Please take care that
only one admin is editing a given form at a given time.</p>';
$lang['help'] = '<h3>What Does This Do?</h3>
<p>The Form Builder Module allows you to create feedback forms (in fact, it\'s a replacement of the original Feedback Form module), with the added power of database storage. With its companion module Form Browser, you can use it to create simple database applications.</p>
<p>The forms created using the Form Builder may be inserted
into templates and/or content pages. Forms may contain many kinds of inputs, and may have
validation applied to these inputs. The results of these forms may be handled in a variety of ways.</p>
<h3>How Do I Use it?</h3>
<P>Install it, and poke around the menus. Play with it. Try creating forms, and adding them to your content.
If you get stuck, chat with me on the #cms IRC channel, post to the forum, send me email, or, if you\'re
really desperate, try reading the instructions on the rest of this page.</P>
<h3>How Do I Create a Form</h3>
<p>In the CMS Admin Menu, you should get a new menu item called FormBuilder. Click on this. On the page
that gets shown, there are options (at the bottom of the list of Forms) to Add a New Form or Modify
Configuration.</p>
<h3>Adding a Form to a Page</h3>
<p>In the main FormBuilder admin page, you can see an example of the tag used to display each form. It looks
something like {cms_module module=\'FormBuilder\' form=\'sample_form\'}</p>
<p>By copying this tag into the content of a page, or into a template, will cause that form to be displayed.
In theory, you can have multiple forms on a page if you really want to. Be careful when pasting the tag
into a page\'s content if you use a WYSIWYG editor such as TinyMCE, FCKEdit, or HTMLArea. These editors may stealthily
change the quote marks (") into HTML entities ("), and the forms will not show up. Try using
single quotes (\') or editing the HTML directly.</p>
<h3>Working with Forms</h3>
<p>By clicking on a Form\'s name, you enter the Form Edit page. There are several tabs, which are described below:</p>
<h4>Main</h4>
<p>This is the main place you\'ll work on your form. Here, you give it a name, an alias (which is used to identify it for placing it in a page or template), and, optionally, a CSS class with which to wrap the whole thing.</p>
<p>Below this, if you have it enabled, is the "fast field adder" pulldown, that lets you quickly add a field to the end of your form by selecting the field type.</p>
<p>Below this is the list of fields that make up your form. More detail on this is described below.</p>
<h4>Form Submission</h4>
<p>When the form is submitted, you can either redirect the user to another page of your site, or you can present the user some message (which can contain any of the user\'s form entries, or just static text). In this tab, you select which of these approaches you wish to use, and, if you chose redirection, it allows you to pick the page to redirect users to after a successful form submission.</p>
<p>Also on this page, you can specify the labels of various submission buttons ("Previous", "next", "submit"). You can also opt to have some Javascript added to the last page of a form that will prevent multiple submissions (useful on slow servers).</p>
<h4>Form Display Options</h4>
<p>This tab allows for other form customizations, like the symbol to show for required fields.</p>
<h4>Captcha Settings</h4>
<p>If you have installed the Captcha module, this tab lets you configure the Captcha settings for your form.</p>
<h4>Form Template</h4>
<p>This is where you do your customization work of your form\'s Smarty Template. See the section called Form Template Variables below.</p>
<p>The form should default to a Custom template that documents the Smarty tags available to you.</p>
<p>Unless you\'re a Smarty expert, you probably don\'t want to mess around with this. If you are a Smarty expert, this is where you can unleash your magic.</p>
<h4>Submission Template</h4>
<p>If, in the Form Submission tab, you selected \'Display "Submission Template", this is where you can create that template. There is a display of which smarty variables are available to you, and a button to generate a sample template.</p>
<p>If you\'re a Smarty expert, you can do all manner of creative and powerful things here. If you\'re not a Smarty expert, you might just want to use the default.
</p>
<h3>Adding Fields to your Form</h3>
<p>The types of fields that are currently supported fit into four groups: standard input fields, display control fields, email-specific fields, and form result handling fields (also called Form Dispositions in places):</p>
<ul>
<li>Standard Input Fields - these are inputs that allow entry of typical form elements; text inputs, radio buttons, etc.</li>
<li>Display Control Fields - these input control how the user will see the display of the form; page breaks, static text, etc.</li>
<li>Email-specific Fields - some forms generate email, and email-specific fields can alter attributes of the emails sent.</li>
<li>Form Dispositions - These determine what happens when the user
submits the form; for each result handling field, some method of transmitting, saving, or emailing the
form contents takes place. A form may have multiple form dispositions.</li>
</ul>
<p>Form fields are assigned names. These names identify the field, not only on the screen as labels for the user,
but in the data when it\'s submitted so you know what the user is responding to. Phrasing the name like a question
is a handy way of making it clear to the user what is expected. Similarly, many fields have both Names and Values.
The Names are what gets shown to the user; the Value is what gets saved or transmitted when the user submits
the form. The Values are never seen by the user, nor are they visible in the HTML, so it\'s safe to use for
email addresses and such.</p>
<p>Some fields can have multiple values, or multiple name/value pairs. When you first create such a field,
there may not be sufficient inputs for you to specify all the values you want. To get more space for inputting
these values, use the buttons at the bottom of the page for adding options.</p>
<p>Fields can be assigned validation rules, which vary according to the type of the field. These rules help
ensure that the user enters valid data. They may also be
separately marked "Required", which will force the user to enter a response.</p>
<p>Fields also may be assigned a CSS class. This simply wraps the input in a div with that class, so as to allow
customized layouts. To use this effectively, you may need to "view source" on the generated form, and then
write your CSS.</p>
<ul>
<li>Standard Inputs
<ul><li>Text Input. This is a standard text field. You can limit the length, and apply various validation
functions to the field.</li>
<li>Text Area. This is a big, free-form text input field.</li>
<li>Checkbox. This is a standard check box.</li>
<li>Checkbox Group. This is a collection of checkboxes. The only difference between this input and a
collection of Checkbox inputs is that they are presented as a group, with one name, and can have a validation function requiring that you check one or more of the boxes in the group.</li>
<li>Radio Group. This is a collection of radio buttons. Only one of the group may be selected by the user.</li>
<li>Pulldown. This is a standard pulldown menu. It\'s really conceptually the same thing as a radio button
group, but is better when there are a large number of options.</li>
<li>Multiselect. This is a multi-select field. It\'s really conceptually the same thing as a checkbox button
group, but is better when there are a large number of options, as you can limit the number displayed on the screen at any one time.</li>
<li>State. This is a pulldown listing the States of the U.S.</li>
<li>Canadian Province. This is a pulldown listing the Canadian Provinces (Contributed by Noel McGran. Thanks!)</li>
<li>Countries. This is a pulldown listing the Countries of the world (as of July 2005).</li>
<li>Date Picker. This is a triple pulldown allowing the user to select a date.</li>
<li>Time Picker. This is a set of pulldowns allowing the user to select a time (using 12 or 24 hour clock).</li>
<li>File Upload. This is a file upload field.</li>
<li>Link (User Entered). This creates a double input field for getting a link URL and link title.</li>
<li>Text Field (Multiple). This field creates one or more text inputs with add and delete buttons, effectively giving the end user a way of creating variable-length lists.</li>
</ul></li>
<li>Email-specific Inputs
<ul><li>Email From Address Field. This allows users to provide their email address. The email generated when the form gets handled will use this address in the "From" field.</li>
<li>Email From Name Field. This allows users to provide their name. The email generated when the form gets handled will use this name in the "From" field.</li>
<li>Email Subject Field. This allows users to provide a subject for their email. The email generated when the form gets handled will use this in the "Subject" field. This may cause trouble with certain dispositions that want to control the Email Subject, so use it with caution.</li>
</ul></li>
<li>Display Control Fields<ul>
<li>-Page Break. This allows you to split your feedback form into multiple pages. Each page is
independently validated. This is good for applications like online surveys.</li>
<li>-Fieldset Start. Combined with Fieldset End, this allows you to group various fields within your form. Use this to start a given grouping.</li>
<li>-Fieldset End. Combined with Fieldset Start, this allows you to group various fields within your form. Use this to end a given grouping.</li>
<li>-Hidden Field. This allows you to embed a hidden field in your form.</li>
<li>-Static Text. This allows you to put text or a label in the middle of your form. This is useful for giving additional help text, especially if you\'re not using a Custom Template to render your form.</li>
<li>-Static Link. This allows you to put a link to a given page into your form. Optionally, you can have it autopopulate with the page where the form is embedded (useful if you\'re sending results via email).</li>
<li>-Computed Field. This allows you to embed a computed field in your form. It is not visible to the user until after the form is submitted. It allows you to do simple arithmetic or string concatenation.</li>
<li>-Unique Integer (Serial). This is an integer that increases every time someone hits your form. Your results may not be sequential, but they will increase monotonically.</li>
</ul></li>
<li>Form Handling Inputs (Dispositions)
<ul><li>*Call a User Defined Tag With the Form Results. This submits all the form results to the User-Defined Tag you specify. The UDT can handle the results however it wants. Values are passed as $param[\'field_name\'].</li>
<li>*Email Results Based on Pulldown. This is useful for web sites where comments get routed based on their subject matter, e.g., bugs get sent to one person, marketing questions to another person, sales requests to someone else, etc. The pulldown is populated with the subjects, and each gets directed to a specific email address. You set up these mappings in the when you create or edit a field of this type. If you use one of these "Director" pulldowns, the user must make a selection in order to submit the
form. This input is part of the form the user sees, although the email addresses are not made visible nor
are they embedded in the HTML.</li>
<li>*Email Results to set Address(es). This simply sends the form results to one or more email addresses that you enter when you create or edit this type of field. This field and its name are not visible in the
form that the user sees. The email addresses are not made visible nor
are they embedded in the HTML.</li>
<li>*Email to User-Supplied Address. This puts an input field in the form for the user to populate with an email address. The form results get sent to that address. Beware of Spam abuse! Active the primitive anti-spam features in the FormBuilder configuration screen.</li>
<li>*Store Results in Database. This will store the form contents in an internal database. You will always use this disposition if you use the form with FormBrowser.</li>
<li>*Redirect to Page Based on Pulldown. This allows you to redirect the form to a different site page depending on its value. If you have multiple dispositions, make sure this is used last.</li>
<li>*Validate via Email. This is a strange and powerful field. It provides the user a mandatory input for their email address. Once they submit their form, the standard form dispositions are not performed -- rather, it send the user an email with a special coded link. If they click on the link, the other form is considered "approved," and the other dispositions are all performed.</li>
<li>*Write Results to Flat File. This takes the form results and writes them into a text file. You may
select the name of the file, and set its format. These files are written to the "output" directory under the
module\'s installation directory, assuming the web server has permission to write there.</li>
<li>*Save Results to File Based on Pulldown. Like the Flat File disposition, except the value of a pull-down determines which file results get written to.</li>
<li>*Save Results to File(s) Based on Multiple Selections. Like the Flat File disposition, except the value(s) of checkboxes determines which file(s) results get written to.</li>
<li>*Email to CMS Admin User. Provides a pull-down of CMS Admin users, and directs the results as an email to the selected admin.</li>
<li>*Store Results for FormBrowser Module v.3. Stores the form results in an XML structure as a single database record. This will become the interface to Form Browser in the next release.</li>
</ul></li></li></ul>
<h3>Passing Default Values to Forms</h3>
<p>Calguy added a nice feature, which is that you can pass default field values to your form via the module tag. This allows you to have
the same form in multiple places, but with different default values. It may not work for more exotic field types, but for fields that have
a single value, you can specify like:</p>
<p>{cms_module module=\'FormBuilder\' form=\'my_form\' value_<i>FIELDNAME</i>=\'default_value\'}</p>
<p>This will set the field with <i>FIELDNAME</i> to \'default_value\'.</p>
<p>This can be problematic, as sometimes field names are unweildy or contain characters that don\'t work well with Smarty. So there is an
alternative like this:</p>
<p>{cms_module module=\'FormBuilder\' form=\'my_form\' value_fld<i>NUMBER</i>=\'default_value\'}</p>
<p>That uses field <i>NUMBER</i>, where <i>NUMBER</i> is the internal FormBuilder field id. You might wonder how you know what that id is. Simply go into the FormBuilder configuration tab,
and check "Show Field IDs"</p>
<h3>Email and Flat File Templates</h3>
<p>Many disposition types allow you to create a template for the email that is generated, or for the way the results are written to a file. If you opt not to create a template, the FormBuilder will use it\'s own best guess, which may or may not work out to your liking. You can always click on the "Create Sample Template" and then customize the results.</p>
<p>To the right, you\'ll find a legend which lists all of the variables that are available to you to use in your template. As of version 0.3, variables have two names, one based on the field name, the other based on the field ID. If you use field names that have characters outside of the ASCII 32-126 range, it will be safer to use the ID-based variables.</p>
<p><strong>Note that once you\'ve changed a template, it will no longer automatically add new fields.</strong> For this reason, it\'s usually best to create your templates as the last step of creating your form.</p>
<p>As of version 0.2.4, you can opt to send any of these emails as HTML email. There should be a checkbox at the top of the template page for this. There is also a "Create Sample HTML Template" button over in the legend area. For HTML email, the email body will also provide the default text-only values.</p>
<h3>Configuration</h3>
<p>There are some global configuration options for FormBuilder:</p>
<ul>
<li>Enable fast field add pulldown. This enables the pulldown on the Form Edit page which saves a step in the creation of new fields.</li>
<li>Hide Errors. This is set by default. Unchecking it will cause more detailed errors to be displayed if there are problems when you submit your form.</li>
<li>Require Field Names. Typically, you will want form fields to be named so you can tell which is which. However, in some cases, you might want to have nameless fields. Uncheck this if you want to allow nameless fields.</li>
<li>Unique Field Names. Typically, you will want form fields to have unique names so you can tell which is which. Uncheck this if you want to allow fields to share names.</li>
<li>Use relaxed email validation. This uses a less restrictive regular expression for validating email; e.g., x@y will be allowed, where typically x@y.tld is required.</li>
<li>Show Form Builder Version. Displays the version of FormBuilder you\'re using in a comment when the form is generated. Typically only useful when debugging.</li>
<li>Enable primitive anti-spam features. When turned on, this allows any given IP address to only generate 10 emails per hour.</li>
<li>Show Field IDs. When turned on, FormBuilder will display field ids when adding or editing a form.</li>
</ul>
<h3>Styling and CSS</h3>
<p>Paul Noone graciously provides us all with a pretty good standard CSS that you can use for forms:</p>
<pre>
/* Sample FormBuilder CSS base */
form {margin-top:0}
form, td, th, li { font-size: 100%}
form div {margin-bottom:0}
fieldset div {
margin-bottom:0.5em;
margin-left:1em;
}
fieldset div div {
margin-top:0.5em;
margin-left:1em
}
fieldset {
margin-bottom:1em;
border:1px solid #F60;
padding:0.5em
}
fieldset label {
width:auto;
}
legend {
color:#FFF;
background:#F60;
font-style:italic;
font-size:1.2em;
margin-bottom:0.5em;
padding:0.2em;
width:auto;
border:1px solid #CCC
}
textarea {
margin: 0.5em 0;
width:98%;
height: 6em
}
/* Apply this class to text/select input fields with shorter labels
to help alignment */
.short-label label {float:left; width:10em}
.short-label fieldset div input,
.short-label fieldset div select {width:16em}
/* Pretty up your Captcha image output */
.captcha {
margin:0.5em 0;
width:200px;
text-align:center
}
.captcha img {border:1px solid #F60; margin-bottom:0.5em}
.captcha input {width:196px; margin-top:0.5em}
/* Just a bit more room for the Submit button */
.submit {margin-top:0.5em}
</pre>
<h3>Form Template Variables</h3>
<h3>Form Template Variables</h3>
<p>You can edit it to make your form layout look any way you\'d like.
To make the form work, you\'ll need to always include the {$fb_hidden} and {$submit}
tags.</p>
<p>You can access your form fields either using the $fields array or by directly accessing fields by their names (e.g., {$myfield->input} )</p>
<p>Each field has the following attributes:</p>
<table>
<tr><th>Field</th><th>Value</th></tr>
<tr><td>field->display</td><td>1 if the field should be displayed, 0 otherwise</td></tr>
<tr><td>field->required</td><td>1 if the field is required, 0 otherwise</td></tr>
<tr><td>field->required_symbol</td><td>the symbol for required fields</td></tr>
<tr><td>field->css_class</td><td>the CSS class specified for this field</td></tr>
<tr><td>field->valid</td><td>1 if this field has passed validation, 0 otherwise</td></tr>
<tr><td>field->error</td><td>Text of the validation problem, in the event that this field did not validate</td></tr>
<tr><td>field->hide_name</td><td>1 if the field name should be hidden, 0 otherwise</td></tr>
<tr><td>field->has_label</td><td>1 if the field type has a label</td></tr>
<tr><td>field->needs_div</td><td>1 if the field needs to be wrapped in a DIV (or table row, if that\'s the way you swing)</td></tr>
<tr><td>field->name</td><td>the field\'s name</td></tr>
<tr><td>field->input</td><td>the field\'s input control (e.g., the input field itself)</td></tr>
<tr><td>field->op</td><td>a control button associated with the field if applicable (e.g., the delete button for expandable text input)</td></tr>
<tr><td>field->input_id</td><td>the ID of the field\'s input (useful for <label for="">)</td></tr>
<tr><td>field->type</td><td>the field\'s data type</td></tr>
<tr><td>field->multiple_parts</td><td>1 if the field->input is actually a collection of controls</td></tr>
<tr><td>field->label_parts</td><td>1 if the collection of controls has separate labels for each control</td></tr>
</table>
<p>In certain cases, field->input is actually an array of objects rather than an input. This happens, for example, in CheckBoxGroups or RadioButtonGroups. For them, you can iterate through field->input->name and field->input->inputs.</p>
<p>Additional smarty variables that you can use include:</p>
<table>
<tr><th>Variable</th><th>Value</th></tr>
<tr><td>total_pages</td><td>number of pages for multi-page forms</td></tr>
<tr><td>this_page</td><td>number fo the current page for multi-page forms</td></tr>
<tr><td>title_page_x_of_y</td><td>displays "page x of y" for multi-page forms</td></tr>
<tr><td>css_class</td><td>CSS Class for the form</td></tr>
<tr><td>form_name</td><td>Form name</td></tr>
<tr><td>form_id</td><td>Form database ID</td></tr>
<tr><td>prev</td><td>"Back" button for multipart forms</td></tr>
<tr><td>submit</td><td>"Continue" or "Submit" button for multipart forms, adjusts automatically</td></tr>
</table>
<p>Dunno why you\'d want some of those, but there you go...</p>
<h3>Known Issues</h3>
<ul>
<li>FormBuilder is not yet integrated with FrontEnd Users. It will be.</li>
<li>FormBuilder does not yet support pretty urls, although that shouldn\'t matter since the user side is pretty simple.</li>
<li>FileUpload Fields may not work correctly with multipage forms.</li>
</ul>
<h3>Troubleshooting</h3>
<ol><li> First step is to check you\'re running CMS 1.1 or later.</li>
<li> Second step is to read and understand the caveat about WYSIWYG editors up in the
section <em>Adding a Form to a Page</em>.</li>
<li> If you\'re missing fields in an email that gets generated, check the disposition field\'s template, and make sure you\'re specifying the missing fields. Seems obvious, but it\'s an easy mistake to make.</li>
<li>Uncheck the "Hide Errors" checkbox in the global options, and see what message gets displayed when you submit your form.</li>
<li> Just mess around and try clicking on links and icons and stuff. See what happens.</li>
<li> Last resport is to email me or catch me on IRC and we can go from there.</li>
</ol>
<p>This is no longer a particularly early version, but it is probably still buggy. While I\'ve done all I can
to make sure no egregious bugs have crept in, I have to admit that during early testing, this program
revealed seven cockroaches, two earwigs, a small family of aphids, and a walking-stick insect. It also
ate the neighbor\'s nasty little yap dog, for which I was inappropriately grateful.</p>
<p>The final release will include bug fixes, documentation, and unconditional love.</p>
<h3>Support</h3>
<p>This module does not include commercial support. However, there are a number of resources available to help you with it:</p>
<ul>
<li>For the latest version of this module, FAQs, or to file a Bug Report, please visit the CMS Made Simple <a href="http://dev.cmsmadesimple.org">Developer Forge</a>.</li>
<li>To obtain commercial support, please send an email to the author at <a href="mailto:sjg@cmsmodules.com"><sjg@cmsmodules.com></a>.</li>
<li>Additional discussion of this module may also be found in the <a href="http://forum.cmsmadesimple.org">CMS Made Simple Forums</a>.</li>
<li>The author can often be found in the <a href="irc://irc.freenode.net/#cms">CMS IRC Channel</a>.</li>
<li>Lastly, you may have some success emailing the author directly and grovelling for free support.</li>
</ul>
<p>Keep in mind that the author has put hundreds of hours into the development of this module. Please take the time to read the documentation before sending questions. Either that, or write your questions on financially negotiable instruments (i.e., cash).</p>
<p>As per the GPL, this software is provided as-is. Please read the text
of the license for the full disclaimer.</p>
<h3>Copyright and License</h3>
<p>Copyright © 2008, Samuel Goldstein <a href="mailto:sjg@cmsmodules.com"><sjg@cmsmodules.com></a>. All Rights Are Reserved.</p>
<p>This module has been released under the <a href="http://www.gnu.org/licenses/licenses.html#GPL">GNU Public License</a>. You must agree to this license before using the module.</p>';
$lang['changelog'] = '<ul>
<li>Version 0.5.3. 26 May 08. Bugfixes to previous set of bugfixes. Now ready for major upgrades for 0.6.</li>
<li>Version 0.5.2. 25 May 08. Bugfixes. Release in preparation for substantial reworking for 0.6</li>
<li>Version 0.5.1. 30 April 08. Bugfixes, rewrote some of the File Upload code to prevent white screen of annoyance.</li>
<li>Version 0.5. 19 April 08. Bugfixes, support for FormBrowser fixes and features, disposition type for upcoming FormBrowser version.</li>
<li>Version 0.4.4. 26 Sept 07. Bugfixes for radio button groups, fix for validation of DispositionDeliverToEmailAddressField.</li>
<li>Version 0.4.3. 18 Sept 07. Bugfixes for pulldowns using numbers, option to inline form, fixes for table-layouts provided by Ap Muthu, fix for requirability of Dispositions.</li>
<li>Version 0.4.2. 14 Sept 07. Bugfixes for XML export, RadioButton Group submission, and HTML labels.</li>
<li>Version 0.4.1. Bugfixes for File Disposition Types.</li>
<li>Version 0.4
<ul>
<li>Upped minimum CMS version to 1.1</li>
<li>Numerous Bug fixes; too many to enumerate here</li>
<li>Massive rejiggering of code to work with CMS MS 1.1 parameter sanitizing regime</li>
<li>Added field types: "TextField (Multiple)" and "Computed Field"</li>
<li>Added dispositions: "Save Results to File Based on Pulldown" and "Save Results to File(s) Based on Multiple Selections"(Calguy)</li>
<li>Added neat-o AJAX-y template-copying for Form Templates, gave versions of old table-based templates to soothe the raging masses.</li>
<li>Added ability to pass default values to form elements from module tag using value_FIELDNAME="value" syntax (Calguy)</li>
<li>Added option to display field ids in admin (Calguy)</li>
</ul>
</li>
<li>Version 0.3
<ul>
<li>Added Captcha module support.</li>
<li>Reworked labeling of form elements to be XHTML compliant</li>
<li>Added Paul Noone\'s new, improved contact form templates</li>
<li>Implementation of Email Subject Field</li>
<li>Added admin-specifiable values to hidden field type, which may contain parsable smarty tags</li>
<li>Text Area Field now allows specification of rows and cols in the admin, instead of CSS</li>
<li>Added Drag\'n\'Drop reordering of form fields.</li>
<li>Added non-blank field name and unique field name global configuration options and validation</li>
<li>Implemented templated display of form results upon submission in addition to page redirecting</li>
<li></li>
</ul>
</li>
<li>Version 0.2.4 - 09 May 2007
<p>Big release:<ul>
<li>Added "Email Form to User-Supplied Address" disposition.</li>
<li>Added "TimePicker" field type. Split "Link" field into a "User-supplied Link" field and a "Static Link" field.</li>
<li>Added HTML email option and auto-templates for all email dispositions.</li>
<li>Added primitive anti-spam features.</li>
<li>Added XML-based import and export of forms.</li>
</ul>
</p>
</li>
<li>Version 0.2.3
<p>Add the ability to call a selectable user defined tag upon disposition of the form.</p>
</li>
<li>Version 0.2.2
<p>Many thanks to Utter Design for sponsoring some changes and bugfixes, which include:
<ul>
<li>Added file upload capabilities to the email disposition</li>
<li>Add PageSetStart and PageSetEnd field types
<p>These field types allow you to create fieldsets in your form, and organise
your fields logically for the user. You can even nest fieldsets, and
associate a style with them appropriately. The default template was changed
to prevent it from wrapping a div around these types of fields.
</p>
</li>
<li>Fixed a problem with DATETIME fields on install
<p>This solves a problem when on install the response table would sometimes not get created when using adodb lite</li>
</li>
</ul>
</p>
</li>
<li>Version 0.2 - 14 November 2006. Calguy & tsw\'s bug fixes for field re-ordering and custom templates. Additional bug fixes for field labels.</li>
<li>Version 0.1 - 8 July 2006. Initial Release</li>
</ul>
';
$lang['utma'] = '156861353.1193756969.1199698276.1213318721.1213322938.6';
$lang['utmz'] = '156861353.1213322938.6.4.utmccn=(referral)|utmcsr=dev.cmsmadesimple.org|utmcct=/|utmcmd=referral';
$lang['utmb'] = '156861353';
$lang['utmc'] = '156861353';
?>
File Manager Version 1.0, Coded By Lucas
Email: hehe@yahoo.com