Arno Welzel

I’m sorry, but I can not really help here. The result of this code should be ok – but it may be, that this code runs after the output buffer for the current request was already handled. I could not tell it without having a look to the complete website installation and a debugger for it. But this is out of scope in this support forum, sorry.

Well – shortcodes are in fact just text. So you can just create shortcodes as text and insert them this way. There is no need to use any menu at all.

For example:

[timed-content-server show="2024-12-20 00:00" hide="2024-12-20 23:59"]

Your content here to be visible from 2024-12-20 00:00 to 2024-12-20 23:59 (using the timezone of your WordPress installation).

[/timed-content-server]

However – in one single shortcode you can only add one single “show” and “hide” option. It is not possible to have multiple times in one shortcode. But of course you can use multiple shortcodes one after another, like this – for example with two days, but the idea should be clear:

[timed-content-server show="2024-12-20 00:00" hide="2024-12-20 23:59"]

Your content here to be visible from 2024-12-20 00:00 to 2024-12-20 23:59 (using the timezone of your WordPress installation).

[/timed-content-server][timed-content-server show="2024-12-24 00:00" hide="2024-12-24 23:59"]

Your content here to be visible from 2024-12-24 00:00 to 2024-12-24 23:59 (using the timezone of your WordPress installation).

[/timed-content-server]

I am sorry, but having multiple dates in one shortcode or server side rule is not possible yet. I may add this for a future update.

Then I don’t know how to solve this, sorry.

I am sorry – but I don’t know how to help with this. The plugin works fine on many other websites (including my own sites) and I never had this issue, so I don’t know what is going wrong. Did you check, that the sender address in the plugin settings is configured properly? If you don’t want to use the WordPress default sender, you must put a valid e-mail address there which is accepted as sender by your mail server.

Yes, the plugin will use whatever is configured since technically it would be much more trouble for any plugin to send e-mails without the WordPress mail functions.

The plugin uses wp_mail(), also see https://github.com/arnowelzel/comment-reply-email-notification/blob/main/classes/CommentReplyEmailNotification.php#L254 and the WP developer documentation at https://developer.www.ads-software.com/reference/functions/wp_mail/.

If this function does not work at all in the plugin, the only way to find out is to check the logs of your server(s) – there is no other way, sorry.

The only thing I can suggest is to debug the whole process – check every log (including the mail service you use).

The plugin uses the regular WordPress mail functionality and it works without any issue I can not imagine what could go wrong, if WordPress itself sends e-mails properly, sorry.

What you may try is client side shortcodes to show the links after a delay, for example like this, since the video takes 8 seconds:

[timed-content-client show="0:08"]
... your content with links here ...
[/timed-content-client]

However – keep in mind, that the loading time of the video may not always be exactly the same! For some visitors a delay of 8 seconds may work, but others may need more like 10 or 12 seconds. So the results may vary, just give it a try.

A better approach would be, if AWB would provide some kind of JavaScript call back, so it can trigger a custom function as soon as the video is finished. Then you could set the links with CSS visibility:hidden by default and let the JavaScript function change the style to visibility:visible when the video ends. This could also be combined with a animation to fade the links in (maybe using opacity and not visibility). Also see here how to build animations in CSS as seen here: https://www.w3schools.com/css/css3_animations.asp

• This reply was modified 2 months ago by Arno Welzel. Reason: Fixed formatting of code example

Version 2.90 now uses the WordPress timezone as default for new rules and if the shortcode does not contain a timezone in the show/hide parameters. So you don’t need to update existing shortcodes. Hope this helps.

Screenshots are here: https://www.ads-software.com/plugins/timed-content/#screenshots

And server side rules (not shortcodes – rules!) always have a timezone, you can not create them without a timezone setting.

However for a shortcode you have to add the timezone as parameter and this will be done, when you use the shortcode creation tool in a “classic” content block within Gutenberg or using the classic editor.

Anyway – I’ll see what I can do to use the WordPress timezone setting as default when a shortcode does not have a timezone parameter added.

For server side rules, Timed Content does not use UTC.

Also see the screenshots in the plugin description. In a shortcode the timezone will be added like this:

[timed-content-server hide="2013-09-13 20:30:00 America/Chicago"]

The same applies to rules which you use by ID. They also contain a timezone setting.

For client side rules, only date/time will be used as they are in the browser since the shortcode will be interpreted using JavaScript in the browser and thus the local timezone of the client applies.

• This reply was modified 3 months, 1 week ago by Arno Welzel.

Thanks for your feedback about this.

I have a donate information in some of my other plugins, but not in this one yet.

For donations you can use PayPal: https://www.paypal.com/paypalme/arnowelzel – thank you!

This is a known limitation. Unfortunately it is not that simple:

First of all you need to be aware, that server side rules will only modify the content before it gets send to the browser. So there is no client side script at all which could do the automatic reload. And even the client side rules do not reload anything but only show or hide existing content dynamically using CSS properties.

Every server side rule short code would have to include a JavaScript where the server tells the client, how long it takes until the current rule may require a page reload to reflect changes. However the calculation of this time span is not that simple. But I see, what I can do.

Edit: At least you must be aware that visitors may get confused if the scrolled down a page and suddenly the whole page gets reloaded – since a partial reload is not possible.

• This reply was modified 3 months, 4 weeks ago by Arno Welzel.

Neither my plugin nor PhotoSwipe does care for any cookies, so your issue may be some other plugin or the template you use which does not work correct, when there is a specific client setting active.

As I already said: just must check the log of the webserver for server side error, there is no other way to find the problem.

I don’t see any error here – at the moment the page referred in your post loads without issue and PhotoSwipe opens as expected.

Whenever you have a server side “page does not load” error, you have to check the log of your webserver for error messages. Usually PHP errors on server side will show up there.

Edit: is there a reason why you use PhotoSwipe 4 and not the current version 5? Version 4 has major issues with newer iPhone devices and should not be used for new websites. It’s only there for backwards compatibility but you should consider changing the version 5 as soon as possible.

• This reply was modified 4 months ago by Arno Welzel.