• Resolved skybod

    (@skybod)


    I’m not sure how to explain this so here’s a screenshot

    View post on imgur.com

    Whatever is happening here has an effect on the appearance, but it’s still working fine.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Aurovrata Venet

    (@aurovrata)

    the Grid UI editor tries to build a grid display from the HTML structure in the HTML text editor.

    If this HTML structure does not match the default cell element, it simply displays a textarea field for you to continue editing the modified cell. So this is normal and not a bug.

    However, looking at your screenshot, I don’t see any obvious HTML structure change, and I reckon the matching script is getting thrown off my the & sign and possibly some other characters.

    I will run a few tests on my server and get back to you.

    Thread Starter skybod

    (@skybod)

    I changed the & to and without any effect, so I deleted the rows behaving as shown and redefined them. It looks OK now.

    Plugin Author Aurovrata Venet

    (@aurovrata)

    so I deleted the rows behaving

    ah too bad… it would have been useful to paste the row here so I could copy it to my form and see if I could reproduce the error ??

    Thread Starter skybod

    (@skybod)

    <div class="field "><label>Date & Time Of Visit <em>*</em></label>[text* covid_date_time class:coviddatetime]
            <p class="info-tip ">Note: Monday & Tuesday closed.</p>
          </div>
    <div class="field "><label>Dining? <em>*</em></label>[checkbox* checkbox-430 label_first use_label_element exclusive default:2 "Yes " "No "]
            <p class="info-tip "></p>
          </div>
    
    <div class="field "><label>Your Message</label>[textarea your-message x5]
            <p class="info-tip "></p>
          </div>
    
    <div class="field "><label></label>[submit "Send Booking "]
            <p class="info-tip "></p>
    Plugin Author Aurovrata Venet

    (@aurovrata)

    looking at the screenshot again, I figured that it was the space in front of the <label> element that was throwing off the matcher. I have fixed this in the regex. Since it’s a minor bug, I will release it the upcoming 4.0 release scheduled for the start of next month.

    Thread Starter skybod

    (@skybod)

    Cheers.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Strange behavior in the plugin form creator’ is closed to new replies.