Jens Kuerschner

{sc_start}post_title{sc_end} translates into the shortcode [post_title /].

If there is a shortcode “post_title”, which returns some text, this text would then be used for the title.

With the post title?

This would be impossible unless you have a short code set up on your side with the same name.

Yes, this is not supported by default.

It is unofficially possible to use the result of a short code inside the short code. If whatever you set is no short code returning proper data it won’t work.

When using the PRO version, meta fields and acf are supported in a more stable and official way. Even there, post title is not available (we might add it – this is a good feedback!). You could create a meta field with your post title however.

1. You cannot use double quotes inside the value as they would break the html scheme. You can use single quotes for the nested shortcode
2. there is unofficial support for YYYYMMDDThhmm or similar. However, transforming it on your side to the official format would be the most stable solution.

you need to use the shortcode function. see https://www.advancedcustomfields.com/resources/shortcode/

{sc_start} represents the beginning “[” of it. {sc_end} the “/]”.

https://www.ads-software.com/support/topic/acf-shortcodes-integration/

Same question with code example.

Hi Nico,

Even the plugin does not explicitly support any combination with third party plugins, it is possible to use a shortcode inside the shortcode that comes with this plugin.

You can check other recent posts for some samples.

In doubt, you can share your code here to get some help.

Best, Jens

Ok. This is somehow good. It means that there is no complete break of the widget. The other shortcode simply does not return the correct format.

You could use the wpdts-custom shortcode separately ([wpdts-custom format='Y-m-d' next='TUE 18:00']) to see what it prints. It needs to match the shown format.

We just released a new patch version (2.3.8), which adds more sanitization to the shortcode-in-shortcode. This should ensure there does not get any breaking code infused by the shortcode.

I tried to reproduce. The only thing I found: Could it be that there is a line break in your code? This breaks any shortcode!

Maybe you can share a screenshot?

It works on my side. Usually issues occur when you copy+paste stuff from A to B and quotation marks become special characters in between. Or you add a line break inside your shortcode. Also try to add the debug option to see more hints.

Here is my setup, which works fine:

• This reply was modified 3 months, 4 weeks ago by Jens Kuerschner.

If you add the “debug” attribute, what does it tell you?

Have you a page, where I can have a look at the not appearing button?

Closing this as it seemed to be resolved.

Optimized it with the latest version.

Check the documentation again, as we added some more explanation there as well. Closing this for now. Feel free to open a new issue if necessary! ??

The problem is, that with this option, the opening button gets rendered in a new context with another parent element. You ::parts selector does no longer match.

We will push a patch soon to make this easier to handle.

For the very moment, you could do something like this:

add-to-calendar-button::part(atcb-button),
atcb-btn-1-modal-host::part(atcb-button) {
}

Hi there,

Try to use the “forceOverlay”. This should fix it as it renders everything on the very top.