Doesn't appear to do anything different than before?

Hi there

WordPress won’t allow you to nest shortcodes with the same name. Please see the codex for more information.

Yes, I realize that… They need to fix the core regexp codebase to accommodate nesting same-named shortcodes. I have a thread over on the suggestions / feedback forum relating to it.

Sorry, I guess I’d assumed that was what this plugin was designed to address through some kind of workaround. Perhaps I misunderstood the purpose of this plugin? If so, my apologies…

If not, can’t Wikipedia already nest shortcodes w/o a plugin?

For instance with Arconix Shortcodes:

[accordions]

[accordion title=”Accordion 1″]

[toggle title=”Title 1″]Text 1[/toggle]

[/accordion]

[accordion title=”Accordion 2″]

[toggle title=”Title 2″]Text 2[/toggle]

[/accordion]

[/accordions]

Seems to function fine.

Or was the general nesting of [shortcodes] (apparently w/o same-name nesting support) an new addition of its own in recent versions?

Perhaps the reason why this plugin doesn’t list as having been updated to 3.5.1 compatibility (unnecessary after native support in some version 3.x.x)? Dunno.

Anyway, sorry if I misread the intended purpose… My bad. ??

Cheers,
~MG

Hi MG

Our plugin just ensures that the standard WP functionality is enabled – it doesn’t enhance it.

By the way, in your accordion example above, “accordion” and “accordions” are different shortcodes so you’re not actually nesting the same shortcodes.

Regards
^Mike

I’m aware that different shortcodes nest & same shortcodes currently have a problem nesting.

Yes, that was kind of the point I was trying to illustrate. WP currently seems to handle “different” tag nesting fine w/o a separate plugin? ??

And actually the main point was that you could nest a toggle (one type of shortcode) inside an accordion (totally different kind) and both would work.

But, true, as you say, the Accordion “tag” is actually two set of slightly different tags, one to define the entire structure and one to define specific collapsible/expandable contents.

Anyway, sounds like this plugin doesn’t quite do what I was hoping for. Didn’t read quite closely enough. Sounded good on the face of it. Just the wrong nuance…. C’est la vie! Will continue advocating for them to fix the core codebase so we don’t have to keep looking for kludges to “work around” the deficiency WRT same-name nesting.

Best,
~MG