We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 18219
    • 826 Posts
    Why use the caractere ].
    Can you replace with ` into the code ?
    In other snippet, the parameters use the caractere ` to delimit the value. huh
      Marc
      I'm French... Sorry for my bad English, I use ' Google Translator' or other... but that remains that tools wink
      • 1764
      • 680 Posts
      I finally got around to uploading the newest version of the snippet. You can find links in the original post.

      I have to abmit that I was a bit rushed to get this out and it may still have some issues with Notices but I have been using it in a production environment for a while now and it should be pretty stable.

      There are a lot of added features and hopefully I’ll be able to give some instructions on how to use them later. For the time being you should be able to look at the Properties and figure out what they are and how to use them.

      One other warning. I’ve changed some of the parameter names in the updated release so you’r old snippet calls won’t work without a couple changes (example: form_name is now form_chunk, to is now data_email_address and required is now form_required).

      Please let me know if you have any problems, quesitons or requests.
        • 1764
        • 680 Posts
        Let me also give one quick disclaimer for those who ran into this thread looking for a simple forms solution: this is probably not the solution for you. This snippet is designed for experienced developers who are already comfortable creating HTML forms.

        The purpose behind this snippet is to save as much time as possible in the form development process without restricting your capabilities in any way. With this snippet you are not limited in the HTML, CSS, Javascript or anythig else you want to use to create your form, you can even use a WYSIWYG editor. You can have custom submission confirmation pages, emails, custom data send emails and you can use placeholders and snippets in any of these to allow you even more flexibility.

        I may eventially write a form generator that would create HTML forms to work with this snippet but for the time being the HTML is up to you and FormProcessor will take care of pretty much everythnig else.
          • 18219
          • 826 Posts
          Thank adam.

          I test the innovations and goes up you my impressions this day
            Marc
            I'm French... Sorry for my bad English, I use ' Google Translator' or other... but that remains that tools wink
            • 6726
            • 7,075 Posts
            Thanks for the update and clarification.

            Just a thing people : don’t just download and start playing with the snippet (like I did rolleyes ), read the documentation first => it’s pretty clear and gives a good idea how to start with FormProcessor.

            For those who want to give extra care toward forms validation and accessibility, I advise you to read this article from webstandards.org : Accessible HTML/XHTML Forms. You’ll also learn much about forms if you begin with them. Very nice tutorial....

            Believe me, it will save you time and eventually it will save time for Adam grin

            And by the way, GREAT snippet, I still have to wrap my head around this one but this is yet another distinctive snippet (few CMS have this at all, let alone with such flexibility : placeholders are definitely nice to use... other marketing ammos, nice, nice laugh )

              .: COO - Commerce Guys - Community Driven Innovation :.


              MODx est l'outil id
              • 18219
              • 826 Posts
              Hi adam,

              An error in the code (in the documentation):
              [!FormProcessor? &form_chunk=`ExampleForm` &data_email_addreess=`your_email@your_domain.com` &form_required=`Name,Message`!]

              &data_email_addreess = &data_email_address

              So, the code is still not interpreted by the parser. In the window of previsualisation, the fields appear. With the posting of the page, not of result.

              I do not know where this problem comes of interpretation of the parser.

              In any case, congratuation for this snippet. It is well commented on and documentation is well done. I took again for the moment only the example given in documentation. I will personalize when I obtain good results.

                Marc
                I'm French... Sorry for my bad English, I use ' Google Translator' or other... but that remains that tools wink
                • 1876
                • 835 Posts
                Hi

                It’s ok to me when I change adreess in adress

                Good job, Thank’s

                Aour
                  • 18219
                  • 826 Posts
                  When I change `[!` by `[[` and `!]` by `]]`, I obtain the good result.
                  To what that can come?

                  I acknowledge that I am new in put Modx I thought that the difference between the placeholder was the setting only in cache. Did I make a false handling?
                    Marc
                    I'm French... Sorry for my bad English, I use ' Google Translator' or other... but that remains that tools wink
                    • 1764
                    • 680 Posts
                    Thanks for catching that addrEEss thing, it’s fixed now.

                    Quote from: Marc at Jan 27, 2006, 03:58 AM

                    When I change `[!` by `[[` and `!]` by `]]`, I obtain the good result.
                    To what that can come?

                    I acknowledge that I am new in put Modx I thought that the difference between the placeholder was the setting only in cache. Did I make a false handling?

                    Yes the only difference between [!!] and [[]] should be caching. In fact the parser turns all of the [!!]s into [[]] before it parses them. I’m not sure exactly why that would be causing a problem but you can always use [[]] and uncheck the cahceable chekbox in the document.
                      • 18219
                      • 826 Posts
                      Quote from: aNoble at Jan 27, 2006, 07:11 AM

                      ...
                      Yes the only difference between [!!] and [[]] should be caching. In fact the parser turns all of the [!!]s into [[]] before it parses them. I’m not sure exactly why that would be causing a problem but you can always use [[]] and uncheck the cahceable chekbox in the document.
                      I haved testing with check and uncheck the cacheable chekbox, it’s a same result.
                      I think that that could come from the system of Utf-8 encoding undecided

                      The problem is a aillor and does not relate to the snippet. I will use the typo who functions for the moment.
                      I prefer to advance on the form and to parameter it correctly. wink
                        Marc
                        I'm French... Sorry for my bad English, I use ' Google Translator' or other... but that remains that tools wink

                      This discussion is closed to further replies. Keep calm and carry on.