WPIntell

Source evidence

Shortcode broken after 2.4 update

We’re Open! · support · 2025-10-21T06:57:00+00:00

mixedsentiment
mediumseverity
0.45relevance
5replies
Evidence onlycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

1 / 1 rows with source links

100.0% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

0 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
studio_m resolved
Hello, I’m using the following shortcode: [open_text update="immediate"]%if_open_now% The office is currently open until %today_end% today.%else% %if_open_later% The office is currently closed, but will open at %today_next%. %else% The office is closed today %if_open_tomorrow%, , but will be open again tomorrow from %tomorrow_start%.%else% %space%and will also be closed tomorrow. %end%%end%%end%[/open_text] This used to work great up until version 2.3. After updating to version 2.4 though, the time is not displayed any more. Reverting back to 2.3 fixes the issue. @studiomondiale Thanks for sharing this with me. There were changes made to the code here, so I’ll use your example to isolate the problem and produce a fix in the next release. @studiomondiale I found the issue in the current version of the plugin. There will be a fix included in the next version: 2.5 later today. Just to confirm, the issue is specific to this replacement text only: [open_text]Open next: %today_next%[/open_text] So, if you did see anything else affected please let me know? I just did some testing and can confirm: It appears to only affect %today_next% @studiomondiale Fixed in version 2.5 This does indeed fix it, thanks!

Comments

5 shown
Noah Hearle 2025-10-21T15:26:00+00:00

@studiomondiale Thanks for sharing this with me. There were changes made to the code here, so I’ll use your example to isolate the problem and produce a fix in the next release.

Noah Hearle 2025-11-03T16:24:00+00:00

@studiomondiale I found the issue in the current version of the plugin. There will be a fix included in the next version: 2.5 later today. Just to confirm, the issue is specific to this replacement text only: [open_text]Open next: %today_next%[/open_text] So, if you did see anything else affected please let me know?

studio_m 2025-11-04T14:06:00+00:00

I just did some testing and can confirm: It appears to only affect %today_next%

Noah Hearle 2025-11-04T22:25:00+00:00

@studiomondiale Fixed in version 2.5

studio_m 2025-11-05T12:05:00+00:00

This does indeed fix it, thanks!