Announcement

Collapse
No announcement yet.

EmporiumPlus Custom Customer Fields Interface module failing

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    EmporiumPlus Custom Customer Fields Interface module failing

    The EmporiumPlus Custom Customer Fields Interface module appears to be failing. I have had a couple of stores now tell me that they are not receiving the data from the fields. One reason this module was "popular" was its ability to make custom fields required WITHOUT having to jump through coding hoops. It was just a simple hidden input field. The module used to also easily include the data from the fields in the Customer and Merchant Notification emails. I don't think opening a support ticket will do any good because Bill's modules are not being updated. A stupid simple replacement is desperately needed.
    Leslie Kirk
    Miva Certified Developer
    Miva Merchant Specialist since 1997
    Previously of Webs Your Way
    (aka Leslie Nord leslienord)

    Email me: [email protected]
    www.lesliekirk.com

    Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr

    #2
    While not 100% easy, or completely browser independent (I think the total would be 95-98% on most sites...see here https://www.w3schools.com/tags/att_input_required.asp) you could just use the Required attribute in the input field.

    <input type="text" name="petfav" value="" required>

    Just make sure you are using a html5 doctype on the page.
    Bruce Golub
    Phosphor Media - "Your Success is our Business"

    Improve Your Customer Service | Get MORE Customers | Edit CSS/Javascript/HTML Easily | Make Your Site Faster | Get Indexed by Google | Free Modules | Follow Us on Facebook
    phosphormedia.com

    Comment


      #3
      Originally posted by Bruce - PhosphorMedia View Post
      While not 100% easy, or completely browser independent (I think the total would be 95-98% on most sites...see here https://www.w3schools.com/tags/att_input_required.asp) you could just use the Required attribute in the input field.

      <input type="text" name="petfav" value="" required>

      Just make sure you are using a html5 doctype on the page.
      Yeah, it didn't seem to play nicely with other required fields. I would have to put the code in place but it wasn't ideal.
      Leslie Kirk
      Miva Certified Developer
      Miva Merchant Specialist since 1997
      Previously of Webs Your Way
      (aka Leslie Nord leslienord)

      Email me: [email protected]
      www.lesliekirk.com

      Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr

      Comment


        #4
        On a side note, that I have just encountered - I may be throwing Bill's module under the bus prematurely. I'm working on trying to use the default Order Custom fields and they don't seem to be included in the confirmation emails when originally sent. If I go in and resend these emails, the custom field data is included in these emails. This is maddening...
        Leslie Kirk
        Miva Certified Developer
        Miva Merchant Specialist since 1997
        Previously of Webs Your Way
        (aka Leslie Nord leslienord)

        Email me: [email protected]
        www.lesliekirk.com

        Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr

        Comment


          #5
          ok, that's because of the fulfillment module installation order. The Order fulfillment email modules run before Bill's module can fire and load up the info.

          this also happens with built in custom order fields. i don't know how you work around Bills module, but if I recall correctly the work around with built ins custom is to manually write the basket to order fields on the OPAY screen.
          Bruce Golub
          Phosphor Media - "Your Success is our Business"

          Improve Your Customer Service | Get MORE Customers | Edit CSS/Javascript/HTML Easily | Make Your Site Faster | Get Indexed by Google | Free Modules | Follow Us on Facebook
          phosphormedia.com

          Comment


            #6
            Originally posted by Bruce - PhosphorMedia View Post
            but if I recall correctly the work around with built ins custom is to manually write the basket to order fields on the OPAY screen.
            If the information is being displayed on the INVC would that mean it is being written on the OPAY screen?

            Leslie Kirk
            Miva Certified Developer
            Miva Merchant Specialist since 1997
            Previously of Webs Your Way
            (aka Leslie Nord leslienord)

            Email me: [email protected]
            www.lesliekirk.com

            Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr

            Comment


              #7
              Originally posted by lesliekirk View Post

              If the information is being displayed on the INVC would that mean it is being written on the OPAY screen?
              I don't think you can make that conclusion. The INVC screen collects its information after ALL of the Fulfillment modules have run. So, Bill's module (in this case) has completed its tasks. In the case of the emails, it hasn't so that data doesn't appear in the emails. I think the only work around is to either (if possible) get bills module to fire on the OSEL/OPAY transition or switch to built in customs. Even with built ins, this can occur if the site was upgraded from an older version where the template email modules are installed BEFORE the custom field modules. (At least that's my take--i've had this issue with built ins on sites that have been around since Merchant2.)
              Bruce Golub
              Phosphor Media - "Your Success is our Business"

              Improve Your Customer Service | Get MORE Customers | Edit CSS/Javascript/HTML Easily | Make Your Site Faster | Get Indexed by Google | Free Modules | Follow Us on Facebook
              phosphormedia.com

              Comment


                #8
                Originally posted by Bruce - PhosphorMedia View Post

                I don't think you can make that conclusion. The INVC screen collects its information after ALL of the Fulfillment modules have run. So, Bill's module (in this case) has completed its tasks. In the case of the emails, it hasn't so that data doesn't appear in the emails. I think the only work around is to either (if possible) get bills module to fire on the OSEL/OPAY transition or switch to built in customs. Even with built ins, this can occur if the site was upgraded from an older version where the template email modules are installed BEFORE the custom field modules. (At least that's my take--i've had this issue with built ins on sites that have been around since Merchant2.)
                I had shifted gears on this thread to comment that I'm having this issue trying to use the "default" code. It's the default code I have been referring to in my last reply. Your comment begs the question - would an updated copy of the email templates help? If so, where would one find them (I think I asked this question in another thread that related specifically to issues I'm having using the Order Custom Field and the data not showing up in the emails.)

                Again, it would be nice to have templates with code similar to how Bill showed us how to implement his modules, to "unimplement" them.
                Leslie Kirk
                Miva Certified Developer
                Miva Merchant Specialist since 1997
                Previously of Webs Your Way
                (aka Leslie Nord leslienord)

                Email me: [email protected]
                www.lesliekirk.com

                Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr

                Comment

                Working...
                X