RegEx for processing WordPress shortcode

Question

I am trying to find a suitable regex for processing WordPress shortcodes. Created an expression but it doesn't process all conditions.

Expression

\[feature([^\]]*)\]([^\]]*)\[\/feature\]

Example text

[feature title="Call us at" width="4" icon="fa-thumbs-up"]my phone is[/feature]

// shortcodes without linebrakes between
[feature title="Call us at" width="4" icon="fa-thumbs-up"]my phone is[/feature][feature title="Call us at" width="4" icon="fa-thumbs-up"]my phone is[/feature]


// with nested shortcode inside attributes


[feature title="Call us at [phone]" width="4" icon="fa-thumbs-up"]my phone is [other][/feature]


[feature title="Call us at [phone] sfdfasd" width="4" icon="fa-thumbs-up"]my phone is [other] dssafsd[/feature]

First two example works but for the nested shortcodes regex fails.

Here is the link for you to play with https://regex101.com/r/zA4iH4/7

In WordPress you don't parse the shortcodes yourself use the Shortcode API and understand that there are limitations with nested shortcodes — Dean Taylor
– Dean Taylor, Commented Dec 21, 2015 at 10:54

Community · Accepted Answer · 2020-06-20 09:12:55Z

1

Specifically if you check the documentation for shortcodes you will find Attribute values must never contain the following characters:

Square braces: [ ]
Quotes: " '

So your sample text above is not strictly valid for WordPress and you will likely have other issues.

As long as you don't have nested [feature...] tags (where a [feature] is inside a [feature]) and no square braces in attributes:

Regular Expression

\[feature([^\]]*)\]([\s\S]*?)\[\/feature\]

Human Readable

// \[feature([^\]]*)\]([\s\S]*?)\[\/feature\]
// 
// Options: Case insensitive; ^$ don’t match at line breaks
// 
// Match the character “[” literally «\[»
// Match the character string “feature” literally (case insensitive) «feature»
// Match the regex below and capture its match into backreference number 1 «([^\]]*)»
//    Match any character that is NOT a “]” «[^\]]*»
//       Between zero and unlimited times, as many times as possible, giving back as needed (greedy) «*»
// Match the character “]” literally «\]»
// Match the regex below and capture its match into backreference number 2 «([\s\S]*?)»
//    Match a single character present in the list below «[\s\S]*?»
//       Between zero and unlimited times, as few times as possible, expanding as needed (lazy) «*?»
//       A “whitespace character” (any Unicode separator, tab, line feed, carriage return, vertical tab, form feed) «\s»
//       Any character that is NOT a “whitespace character” (any Unicode separator, tab, line feed, carriage return, vertical tab, form feed) «\S»
// Match the character “[” literally «\[»
// Match the character “/” literally «\/»
// Match the character string “feature” literally (case insensitive) «feature»
// Match the character “]” literally «\]»

edited Jun 20, 2020 at 9:12

CommunityBot

11 silver badge

answered Dec 21, 2015 at 11:35

Dean Taylor

42.4k3 gold badges33 silver badges53 bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Sisir Over a year ago

It is not working when there is any nested shortcode inside attributes.

Dean Taylor Over a year ago

Added support matched pair double quotes used for parameters, although it should be noted that WordPress explicitly doesn't support use of shortcodes in parameter / attribute values.

Dean Taylor Over a year ago

Specifically if you check the documentation for shortcodes you will find Attribute values must never contain the following characters: Square braces: [ ] and Quotes: " '

Dean Taylor Over a year ago

Updated answer to remove updated regular expression as it would not be strictly valid for WordPress.

Sisir Over a year ago

yes, you are correct. Putting shortcodes inside attribute values is bad practice until WP core supports it! Thanks!

|

Collectives™ on Stack Overflow

RegEx for processing WordPress shortcode

1 Answer 1

Regular Expression

Human Readable

6 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Regular Expression

Human Readable

6 Comments

Your Answer

Sign up or log in

Post as a guest

Related