Issue with “Add Bulk Directions” parser

  • Behrouz

    (@nwm2006)


    2 weeks, 1 day ago

    Hi,

    I found an issue with the Add Bulk Directions feature. When I paste directions containing Cooked shortcodes, such as

    [cooked-timer minutes=”10″]…<span data-placeholder-token=”true” class=”text-token-text-primary cursor-text rounded-sm”>[/cooked-timer]</span> the text gets cut off at [cooked-timer minutes= and everything after that is missing. Regular text works fine. Could you please check why the bulk directions parser is truncating the shortcode?

    By the way, thanks for this great feature, this is a must have and help us alot.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author XjSv

    (@xjsv)

    2 weeks, 1 day ago

    @nwm2006 Very interesting, I missed that scenario during testing.

    I will definitely fix this in the next release. Thanks for bringing it up.

    Plugin Author XjSv

    (@xjsv)

    2 weeks, 1 day ago

    @nwm2006 Could you paste the test that you are pasting into the Bulk directions again?

    From what you pasted I see this:

    [cooked-timer minutes=”10″]…<span data-placeholder-token=”true” class=”text-token-text-primary cursor-text rounded-sm”>[/cooked-timer]</span>

    I just want to make sure that I am getting that correctly because it seems a little weird. For example if you break it down it looks like this:

    [cooked-timer minutes=”10″]

    <span>

    [/cooked-timer]

    </span>

    With a span being opened inside cooked-timer and being closed outside. I think it should be:

    [cooked-timer minutes=”10″]

    <span></span>

    [/cooked-timer]

    Let me know, maybe it was just a typo.

    Thread Starter Behrouz

    (@nwm2006)

    2 weeks, 1 day ago

    Yes, that was a typo!
    Even this [cooked-timer minutes=”5″]5 Minutes[/cooked-timer] would trigger the issue.

    • This reply was modified 2 weeks, 1 day ago by Behrouz.
    Plugin Author XjSv

    (@xjsv)

    2 weeks ago

    @nwm2006 Sorry I never responded to you. I have fixed this issue and it will be released in v1.17.0

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

  • 4 replies
  • 2 participants
  • Last reply from: XjSv
  • Last activity: 2 weeks ago
  • Status: not resolved