Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Franky

    (@liedekef)

    Do you mean checkbox fields? Or any custom field?

    Thread Starter pika28

    (@pika28)

    Plugin Author Franky

    (@liedekef)

    Ok, I’ll try to reproduce this

    Plugin Author Franky

    (@liedekef)

    Just tested with a required field and everything seems to be working as expected. Can you create a temporary event that has the problem and send me an admin account so I can check on that event (maybe copy the one currently having the prob and putting it to “private”)?

    Thread Starter pika28

    (@pika28)

    sorry, I’m having trouble understanding you. I do not speak English. I use google translation.

    If I understand correctly, you want a copy of the event? How, exactly as copy?

    Thread Starter pika28

    (@pika28)

    I disabled the REQ_ function temporarily. I just re-enable for you to test.

    Plugin Author Franky

    (@liedekef)

    Just email me a temporary admin account so I can check for myself. My email: [email protected]

    Plugin Author Franky

    (@liedekef)

    For info: #REQ_FIELD{3} should be used, and not #REQ_FIELD{03} (the 3 is just an example, the leading 0 is the problem).
    I’ll try to take the leading 0 into account as well …

    Plugin Author Franky

    (@liedekef)

    For info: the next version works around this.

    Thread Starter pika28

    (@pika28)

    Great!
    Everything is back in order.

    I replaced the {0x} with {x}.

    About my multi-value fields, I replaced the number “0” with the letter “O”. I expect the next version to replace the letter “O” with the number “0”.

    Thank you very much Franky for this excellent plugin and your customer service.

    Plugin Author Franky

    (@liedekef)

    The next version will solve that to.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Problem with checking fields #REQ_’ is closed to new replies.