• Resolved keeslina

    (@keeslina)


    Hi,

    Thanks for the great plugin.
    I have two requests:
    1. The wrapper div ( wp-block-silkypress-input-field ) does not seem to wrap the field.
    <div class="wp-block-silkypress-input-field custom-class"></div>
    <div class="silkypress-input-field-area">

    Can you please fix this, so i can add styling to the content of the wrapper?
    2. can you please remove the word (optional) from the input label, or wrap it in a span or something so I can remove it using CSS ?



Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter keeslina

    (@keeslina)

    In addition to my previous request:

    • the wrapper bug i mentioned does not occur when using a select field. It does when using a checkbox field
    • If have activated ‘Show on Order page (in dashboard)’ . However, it does not show up in the order table ( /wp-admin/admin.php?page=wc-orders ). It does show up on the order page itself
    Plugin Author Diana Burduja

    (@diana_burduja)

    Hello @keeslina,

    the wrapper thing is not a bug. There are technical reasons related to the internal workings of blocks in general as to why the “wp-block-silkypress-input-field” div doesn’t wrap the “silkypress-input-field-area” div. It has nothing to do with type of the input field (select vs checkbox), but with the WooCommerce implementation of the parent block (some parent blocks allow inner blocks, others not; that is why some “silkypress-input-field-area” divs are wrapped in “wp-block-silkypress-input-field”, while others are not).

    I’m afraid you’ll have to apply the styling directly to the “silkypress-input-field-area” div, when necessary.

    The “Show on Order page” option also works exactly as described (see screenshot nr. 5 on the description page, or this screenshot). Notice that the wording says “Show on Order page” and not “Show in the Order table”.

    I’ll wrap the ” (optional)” text in a span in a future plugin release.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.