WordPress.org

Ready to get started?Download WordPress

Forums

Fast Secure Contact Form
Fast Secure Contact Form 4.0 Beta 2 - Please Test (25 posts)

  1. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

    Fast Secure Contact Form 4.0 Beta 2 is just released

    Download here:
    http://www.fastsecurecontactform.com/beta

    Fast Secure Contact Form 4.0 Beta 2 for WordPress

    After one year of hard work, Mike Challis and Ken Carlson have redeveloped the whole WordPress plugin.

    We’re looking for volunteers that currently use our WordPress plugin to test the new 4.0 Beta version. This is a beta build and could potentially have bugs that we don’t know of. Please stress test and let us know of any issues.

    = 4.0 Beta 2 Change log =
    Changes since 4.0 Beta 1:
    Version 4.0 Beta 2 08/30/2013

    Changes since 4.0 Beta 1
    ——————
    Lots of work on the Style tab:
    Added more style settings for Style of labels, field inputs, buttons, and text.
    Separated style sections into “Alignment DIVs”, and “Style of labels, field inputs, buttons, and text”

    “Alignment DIVs” settings are for adjusting the alignments of the form elements.
    You can also check “reset the alignment” to return to defaults and make the “labels on top” or “labels on left”.

    “Style of labels, field inputs, buttons, and text” are for setting style of the form labels, field inputs, buttons, and text.
    This is a great way to change label or field colors. You can add color:red; any style attributes you want.
    You can also check “reset the styles” to return to defaults.

    Fix bug: The donate box div did not minify.
    Fix bug: The Label CSS and Field CSS field options did not work on all field types.
    Fix bug: max_forms_num could get out of sync when deleting forms.
    Fix bug: setting was ignored “Enable sender information in email footer”
    Fix bug: Custom Label CSS was ignored for checkbox, checkbox-multiple, and radio fields.
    Fix bug: CSS setting ‘labels on left’ messed up checkbox, checkbox-multiple, and radio fields.
    Fix bug: CSS setting ‘labels on left’ messed up HTML before/after form field position.
    Fix bug: Field Label setting for the Reset button adds onclick= to the label.
    Fix bug: When viewing a form preview, changing the form select switches back to Edit mode.
    Fix Bug: Reply-To email header was set to incorrect address.
    “Email From” setting renamed to the more accurate “Return-path address”
    Fixed and added more error label settings.
    Moved “Enable PHP sessions” setting to the ‘Advanced’ tab.
    Split ‘Styles/Labels’ tab into a ‘Styles’ tab and a ‘Labels’ tab.
    Optimize backup file download then test with IE, FF, Chrome, Opera.
    Added form_number to the ‘fsctf_mail_sent’ action hook object array
    Added ‘Domain Protect Settings’ to the ‘Security’ settings tab
    Added setting for “Additional allowed domain names(optional)” to the ‘Security’ settings tab.
    Added show/hide details labels to field settings toggle buttons.
    Added focus to new field with message when adding New Field.
    Added setting: CSS style for form checkbox, checkbox-multiple, and radio labels. (useful to change colors).
    Updated admin and form stylesheets.
    Edited some settings labels.
    More optimized HTML indents when view source.
    Minor UI changes.

    Beta testers, please share your feedback on the plugin
    We welcome enhancement suggestions, any errors or issues you encounter.
    Please post them in this support forum.

    Please report any errors or bugs in A NEW TOPIC in this Support Forum.
    Please put BETA with your subject line, give specific details about the issue, steps needed to duplicate, and include a URL to your form page.

    Have fun!

    Mike Challis

    http://wordpress.org/plugins/si-contact-form/

  2. jensen_tw
    Member
    Posted 7 months ago #

    Has a problem in 4.0 Beta 2: after submit ,it show empty page, can not redirect correctly. my website form page http://lanchic.com/%E8%88%87%E6%88%91%E8%81%AF%E7%B9%AB/

  3. jensen_tw
    Member
    Posted 7 months ago #

    Resolve the above issue, it is a conflict from another plugin " Fast Secure Contact Form Newsletter Add-on " , when I disable this plug-in, the above problem resolved.

  4. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

  5. Malae
    Member
    Posted 7 months ago #

    Hi Mike,
    Have just installed version 4.02 beta over version 3.1.9 on one site. No problem with the installation, but lost some style settings: width and colour of text field, but now fixed. The interface is easier to negotiate. I see that the text field can still be dragged to the far right side of the screen. I asked about this issue with version 3.1.8.2 about 3 months ago, but did not get any reply.

  6. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

    Malae,
    URL to your form?

  7. Malae
    Member
    Posted 7 months ago #

    Mike,
    I don't want to broadcast the URL yet. I tried to contact you via your MCR web site, but possibly the message was blocked.

  8. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

    I am using the beta on my live site now with no trouble.
    I suggest installing the beta, and because of changes in the new beta, click reset to 'labels on top' for the alignment divs
    and then click reset "Reset the styles of labels, field inputs, buttons, and text". This will initialize the new settings on your form.

    It is suggested to only make adjustments to the styles of labels, field inputs, buttons, and text"
    For example, on my site, I only had to add width:300px;
    to these three settings to make all my input fields look the same width:
    Input text fields
    Input textarea fields
    Input select fields

    And I did have to adjust Form Div to width:99%;
    But it make these adjustments based on what you need

  9. Malae
    Member
    Posted 7 months ago #

    Thanks for the advice. The issue is not really causing much trouble, which is why I did not pursue further previously, First of all it only happens with Firefox and Chrome, but I would like to stop it happening. I will try your suggestions with both versions and advise.

  10. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

    Malae, those settings are only in the 4.0 version, I am not updating 3.xx anymore

  11. Malae
    Member
    Posted 7 months ago #

    Mike,
    I reset the form on ver. 4.02 and played with the settings again for a couple of hours, but still cannot resolve the issue. I searched for this issue on other forms and found someone else had had the same problem and described it in detail. There was a solution posted that apparently worked for another form, using {overflow:auto; resize:both;}, but I couldn't find how to apply it to your form. Perhaps you could take a look.
    URL: http://wordpress.org/support/topic/contact-form-7-textarea-max-width

  12. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

    It looks like you would need to add overflow:auto; resize:none; to the Input textarea fields style setting
    You do not need the curly brackets
    Let me know if it worked

  13. Malae
    Member
    Posted 7 months ago #

    Yes, I was going to try that and you will be happy to know that it works in the beta version. This is installed on a site that is still under development.
    My active site still has ver. 3.1.9 and is more important until I switch to ver. 4. I am happy to report that the code also works here too in the CSS style inside form input fields.

  14. jmanko
    Member
    Posted 7 months ago #

    I love the ability to copy settings from one form to another. Can you add the capability to copy form settings from one site to another site in a multisite installation? That would be a huge help.

  15. kchayka
    Member
    Posted 7 months ago #

    I really, really wish you gave us the option to do away with ALL inline styles and use our own external stylesheet. Whenever I erase values in the Styles tab it just reassigns the defaults rather than clearing them out altogether. It can be a challenge to get a consistent look and feel with custom template styles. I find inline styles rather cumbersome to work with and they add a lot of unnecessary code.

    I also wish there were easier ways to override styles for specific fields. I have a particular radio group that requires unique styling for each radio control. In v3.1.9 there were <span> tags around the input and its associated label, which allowed me to do what I needed, but which seems to have been eliminated in v4. Can you please at least bring these span tags back?

    Thanks for your work on this plugin. I do like how the new interface is organized.

  16. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

    kchayka, thanks for your suggestions. Please refer to a recent topic on the same subject. I proposed a change that will be worked on soon. Keep in mind that I have to have backwards compatibility with users who do not need new features.
    http://wordpress.org/support/topic/beta-cant-remove-inline-styles

    The span tags were removed because they were causing problems where the text would not wrap.

  17. kchayka
    Member
    Posted 7 months ago #

    Sounds perfect for how to apply stylesheets, but I'm not sure I understand the issue with span tags. Everything can be styled to wrap or not, be inline or block, float left/right/none, clear, etc., and usually with a minimum of extra markup.

    That is, if you know how to use CSS effectively, which I do. I understand about backward compatibility but being able to use CSS to its full potential should not be thwarted because of it. And responsive design really does require it.

    I look forward to the version with stylesheet options. thanks!

  18. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

    kchayka, why do you require the span?

    Before it was like this
    <span style="white-space:nowrap;"><input type="radio" bla bla ... ><span>

    What do you need?

  19. kchayka
    Member
    Posted 7 months ago #

    What I need is to contain a radio button with its associated label and style them as a unit:
    <span><input type="radio" id="si_contact_ex_field..."><label for="si_contact_ex_field...">text</label></span>

    For my purposes, the inline style on the span is not needed, I just need each input/label pair in a separate container. My external CSS does the rest.

  20. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

    Yes that should be doable. I might not be able to work on it until Saturday.
    Would you mind sending ma a link so I can see what you do with it?
    If you don't want to post the URL here, use my contact form
    http://www.fastsecurecontactform.com/contact

  21. cocobongo
    Member
    Posted 7 months ago #

    some issues:

    - Duplicate name not allowed: this is good, but even if I change the tag, the problem persists, so there must be a way to add a custom label.
    - can't edit email label or any other label from the default fields

    - UX/UI issues:

    - most of the times, after changing something, I'm led to click on the only visible button, which is "delete".
    - Also, have to open every field to delete it, maybe just add the delete button on closed state and take it off on edition mode changing it by a "save" button?
    - this is something I always felt as an important issue: to give each field its own ID, or at least a class (ID is way better). I don't mean labels or inputs, but the main div for the field. That way, it's easier to control it via CSS. While for most projects is good as it is right now, for complex forms it's a pretty big issue.
    - radio buttons: unless I want to use the default, it's really troublesome to manage their styles and positioning, spent 30 minutes to achieve something I usually do in 10 seconds. By only having IDs and/or classes, this would be solved in a snap, hence why I ask for them

    Everything else is great as usual, fields re-ordering is a real time saver. And sorry about being so anal on UX/UI but that's my main area of expertise so that's what jumps to me at first glance! Either way, many thanx for this great plugin! :D

  22. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

    cocobongo,
    You cannot have duplicate field names or field tags by design.

    thanks for the suggestions in field edits, the beta download was just updated with these changes:
    added Save Changes button to field details on the Fields tab
    added (standard field) note next to standard field names on the Fields tab.
    added note “Standard field names can be changed on the Labels tab.” to the field details on the Fields tab
    added standard field note will indicate if a (standard field name was changed on the Labels tab).
    added a couple more filters.
    If you have changed a standard field label, it will display the changed label in bold on the Fields tab.

    About your style suggestions. Please refer to a recent topic on the same subject. I proposed a change that will be worked on soon.
    http://wordpress.org/support/topic/beta-cant-remove-inline-styles

  23. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

    cocobongo,
    in this example, where do you want ID to be?

    <div class="fscf-clear">
      <div class="fscf-field-left">
        <div style="text-align:left; padding-top:5px;">
          <label style="text-align:left;" for="si_contact_name10">Name:<span style="text-align:left;">*</span></label>
        </div>
        <div style="text-align:left;">
          <input style="text-align:left; margin:0;" type="text" id="si_contact_name10" name="full_name" value=""  size="40" />
        </div>
      </div>
    </div>
  24. cocobongo
    Member
    Posted 7 months ago #

    it would be great if <div class="fscf-clear"> could have an ID :)

    and many thanx for taking a look :)

  25. Mike Challis
    Member
    Plugin Author

    Posted 7 months ago #

Reply

You must log in to post.

About this Plugin

About this Topic

Tags

No tags yet.