New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Plugin to show or hide portions of a Page or Post based on specific date/time characteristics. | You have to log in to add a translation. | Details |
Original untranslated
Plugin to show or hide portions of a Page or Post based on specific date/time characteristics.
You have to log in to edit this translation. |
|||
| ↑ | Timed Content | You have to log in to add a translation. | Details |
Original untranslated |
|||
| Example: you set a rule to start on January 1, 2013 with daily repetetion. To get all the possible dates for that rule until today and a few weeks in the future this would mean to calculate more than ten(!) years or 3650 values until today. But most likely you don't want to see the dates from 10 years ago but the values how they will be now and some repetitions into the future. | You have to log in to add a translation. | Details | |
Original untranslated
Example: you set a rule to start on January 1, 2013 with daily repetetion. To get all the possible dates for that rule until today and a few weeks in the future this would mean to calculate more than ten(!) years or 3650 values until today. But most likely you don't want to see the dates from 10 years ago but the values how they will be now and some repetitions into the future.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| For hourly intervals: start at current date minus 1 day↵ For daily intervals: start at current date minus 7 days↵ For weekly intervals: start at current date minus 21 days↵ For monthly intervals: start at current date minus 80 days↵ For yearly intervals: start at current date minus 380 days | You have to log in to add a translation. | Details | |
Original untranslated
For hourly intervals: start at current date minus 1 day↵
For daily intervals: start at current date minus 7 days↵
For weekly intervals: start at current date minus 21 days↵
For monthly intervals: start at current date minus 80 days↵
For yearly intervals: start at current date minus 380 days
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Since it makes no sense to get all values of the past, the projected dates/times will not display all available dates but will limit the start date to the current date minus a certain value depending on the interval. | You have to log in to add a translation. | Details | |
Original untranslated
Since it makes no sense to get all values of the past, the projected dates/times will not display all available dates but will limit the start date to the current date minus a certain value depending on the interval.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Projected dates/times seem to be fixed to a certain start date - why? | You have to log in to add a translation. | Details | |
Original untranslated
Projected dates/times seem to be fixed to a certain start date - why?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| <code>debug</code> - If <code>true</code>, adds some debugging statements to the web page as HTML comments. If <code>when_hidden</code>, the debugging statements are added only when the content is hidden. Defaults to <code>false</code>. | You have to log in to add a translation. | Details | |
Original untranslated
<code>debug</code> - If <code>true</code>, adds some debugging statements to the web page as HTML comments. If <code>when_hidden</code>, the debugging statements are added only when the content is hidden. Defaults to <code>false</code>.
CommentFound in description list item. You have to log in to edit this translation. |
|||
| An example showing use of the <code>[timed-content-client]</code> shortcode. The "alarm clock" button on the editor menubar brings up a dialog box to help build the Timed Content shortcodes. | You have to log in to add a translation. | Details | |
Original untranslated
An example showing use of the <code>[timed-content-client]</code> shortcode. The "alarm clock" button on the editor menubar brings up a dialog box to help build the Timed Content shortcodes.
CommentScreenshot description. You have to log in to edit this translation. |
|||
| If you want to use Timed Content with Gutenberg you have to add a "Classic" block. There is no way to show or hide other content blocks with Timed Content. | You have to log in to add a translation. | Details | |
Original untranslated
If you want to use Timed Content with Gutenberg you have to add a "Classic" block. There is no way to show or hide other content blocks with Timed Content.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| To be sure, you should check your existing rules and shortcodes if you upgraded from a version below 2.50. | You have to log in to add a translation. | Details | |
Original untranslated
To be sure, you should check your existing rules and shortcodes if you upgraded from a version below 2.50.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Existing shortcodes and rules containing dates in the format mm/dd/yyyy should still work, but when editing rules the date value is converted to the new format. | You have to log in to add a translation. | Details | |
Original untranslated
Existing shortcodes and rules containing dates in the format mm/dd/yyyy should still work, but when editing rules the date value is converted to the new format.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| In versions prior to 2.50 the date/time format was not handled very well which caused quite some confusion. Therefore version 2.50 now uses a fixed format similar to ISO 8601: yyyy-mm-dd HH:MM | You have to log in to add a translation. | Details | |
Original untranslated
In versions prior to 2.50 the date/time format was not handled very well which caused quite some confusion. Therefore version 2.50 now uses a fixed format similar to ISO 8601: yyyy-mm-dd HH:MM
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Using Timed Content in Gutenberg | You have to log in to add a translation. | Details | |
Original untranslated
Using Timed Content in Gutenberg
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Old rules after updating to version 2.50 | You have to log in to add a translation. | Details | |
Original untranslated
Old rules after updating to version 2.50
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Extract the contents of the package to the <code>/wp-content/plugins/timed-content</code> directory | You have to log in to add a translation. | Details | |
Original untranslated
Extract the contents of the package to the <code>/wp-content/plugins/timed-content</code> directory
CommentFound in installation list item. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.