[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f9--jwimD_bMTFMXsRQYSgVKBuea-pU-HsYuKpVxh2iY":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":16,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":38,"analysis":145,"fingerprints":173},"schedule-your-content","Schedule Your Content","1.0","Jatinder Pal Singh","https:\u002F\u002Fprofiles.wordpress.org\u002Fj_p_s\u002F","\u003Cp>Schedule your content plugin can help you in showing content within your wordpress blog for a specific period. You can decide when to start showing content and when to stop showing content.\u003Cbr \u002F>\nThis plugin uses shortcodes which can be written within the post content or page content or in text widget also. This plugin uses 4 parameters to schedule your content.\u003Cbr \u002F>\nshortcode: [scheduler] Here is your content[\u002Fscheduler]\u003Cbr \u002F>\nParameters: start_date, start_time, end_date, end_time\u003C\u002Fp>\n\u003Cp>Date must be in YYYY-MM-DD format and time must be in 24-hour format.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Here is the simple example where you schedule your content for specific period:\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>[scheduler start_date=’2012-05-13′ start_time=’06:30′ end_date=’2012-06-13′ end_time=’09:30′]\u003Cbr \u002F>\nThis is scheduled Content.\u003Cbr \u002F>\n[\u002Fscheduler]\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Here is the example where you want to schedule your content daily within 9am to 10am.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>[scheduler start_date=” start_time=’09:00′ end_date=” end_time=’10:00′]\u003Cbr \u002F>\nThis is scheduled Content.\u003Cbr \u002F>\n[\u002Fscheduler]\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Here is the example when you want your content should be expired on specific date and time.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>[scheduler start_date=” start_time=” end_date=’2012-05-16′ end_time=’10:00′]\u003Cbr \u002F>\nThis is scheduled Content.\u003Cbr \u002F>\n[\u002Fscheduler]\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Here is the example when you want to start showing your content on specific date and time and do not want it to be expired.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>[scheduler start_date=’2012-05-12′ start_time=’10:00′ end_date=’2099-05-16′ end_time=”]\u003Cbr \u002F>\nThis is scheduled Content.\u003Cbr \u002F>\n[\u002Fscheduler]\u003C\u002Fp>\n","Now you decide when to show what within your POST or PAGE or TEXT Widget content. Easy to use shortcode",10,2750,90,4,"2012-05-14T20:10:00.000Z","",[18,19,20,21,22],"content","page","post","schedule","time","http:\u002F\u002Fwww.appinstore.com\u002Fschedule-your-content\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fschedule-your-content.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":32,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":35,"avg_patch_time_days":36,"trust_score":25,"computed_at":37},"j_p_s","jsphstls",7,540,87,30,"2026-04-04T10:36:13.260Z",[39,60,82,104,126],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":49,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":53,"requires_php":16,"tags":54,"homepage":58,"download_link":59,"security_score":25,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"scheduled-contnet-by-streama","Scheduled Content","2.1","Danny159","https:\u002F\u002Fprofiles.wordpress.org\u002Fdanny159\u002F","\u003Cp>After installing and activating the plugin you can use the shortcode [schedule]. You can pass upto 4 parameters, the date and the time to show the content and the date and time the content will expired and disappear from your page or post. You have to pass at least one parameter from the scheduled or expired.\u003C\u002Fp>\n\u003Cp>Sample –\u003C\u002Fp>\n\u003Cp>[schedule on=’2014-12-01′ at=”10:01″ expon=’2014-12-01′ expat=”13:15″]\u003Cbr \u002F>\nthe content you want to hide here\u003Cbr \u002F>\n[\u002Fschedule]\u003C\u002Fp>\n\u003Cp>The 4 parameters are “on”, “at”, “expon” and “expat”.\u003Cbr \u002F>\n“on” accepts a date, until that date is arrived the content will be hidden.\u003Cbr \u002F>\n“at” accepts a time. Time has to be set in 24hrs format. (date should be yy-mm-dd if you only pass time)\u003Cbr \u002F>\n“expon” accepts a date, the content will disappear from the page on this date.\u003Cbr \u002F>\n“expat” accepts a time. Time has to be set in 24hrs format. (date should be yy-mm-dd if you only pass time)\u003C\u002Fp>\n\u003Cp>The time is compared with your blog’s time zone settings, if you set your time zone to local time zone it would be easy for you. Go to “General” settings of your wordpress dashboard, under “Time Zone” you can set the time zone you prefer.\u003C\u002Fp>\n\u003Cp>Shortcodes will also run inside this shortcode!!\u003C\u002Fp>\n","Scheduled content enables you to schedule portions of a post or page and\u002For set an expiery date for that content.",60,3619,100,6,"2014-05-08T13:44:00.000Z","3.9.40","3.5",[18,19,55,56,57],"posts","scheduled-content","timed","http:\u002F\u002Fthatblogger.co\u002Fscheduled-content-wordpress-plugin\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fscheduled-contnet-by-streama.2.1.zip",{"slug":61,"name":62,"version":63,"author":64,"author_profile":65,"description":66,"short_description":67,"active_installs":68,"downloaded":69,"rating":49,"num_ratings":70,"last_updated":71,"tested_up_to":72,"requires_at_least":73,"requires_php":74,"tags":75,"homepage":80,"download_link":81,"security_score":49,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"yahman-add-ons","YAHMAN Add-ons","0.9.30","YAHMAN","https:\u002F\u002Fprofiles.wordpress.org\u002Fback2nature\u002F","\u003Cp>Page views,Google Adsense,Analytics,Social,Profile,Table of contents,Related Posts,sitemap,SEO,JSON-LD structured data,Open Graph protocol(OGP),Blog card,Twitter timeline,Facebook timeline,Carousel Slider etc…\u003C\u002Fp>\n","YAHMAN Add-ons has Multiple functions.",1000,95737,2,"2025-04-08T23:10:00.000Z","6.8.5","4.9.8","5.4",[76,77,78,79],"pageviews","popular-posts","table-of-contents","twitter-timeline","https:\u002F\u002Fdev.back2nature.jp\u002Fen\u002Fyahman-add-ons\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fyahman-add-ons.0.9.30.zip",{"slug":83,"name":84,"version":85,"author":86,"author_profile":87,"description":88,"short_description":89,"active_installs":90,"downloaded":91,"rating":49,"num_ratings":92,"last_updated":93,"tested_up_to":72,"requires_at_least":94,"requires_php":95,"tags":96,"homepage":102,"download_link":103,"security_score":49,"vuln_count":26,"unpatched_count":26,"last_vuln_date":27,"fetched_at":28},"last-modified-timestamp","Last Modified Timestamp","1.0.6","Evan Mattson","https:\u002F\u002Fprofiles.wordpress.org\u002Faaemnnosttv\u002F","\u003Cp>This plugin adds information to the admin interface about when each post\u002Fpage was last modified (including custom post types!).\u003C\u002Fp>\n\u003Cp>Enhanced areas:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Page\u002Fpost admin tables – added \u003Ccode>Last Modified\u003C\u002Fcode> column which is also sortable.\u003C\u002Fli>\n\u003Cli>Page\u002Fpost edit screen (\u003Ccode>post.php\u003C\u002Fcode>) – added \u003Ccode>Last modified on: *timestamp*\u003C\u002Fcode> to \u003Ccode>Publish\u003C\u002Fcode> meta box.\u003C\u002Fli>\n\u003Cli>Admin messages after editing a page\u002Fpost – ie: \u003Ccode>Post updated. *timestamp* View Post\u003C\u002Fcode>,\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>No options currently available, but the output can be fully customized with filters and the shortcode can be easily customized using attributes!\u003C\u002Fp>\n\u003Ch3>Gutenberg, WordPress 5, and Beyond\u003C\u002Fh3>\n\u003Cp>This plugin does not yet enhance the new editor provided by Gutenberg and introduced as the default editor in WordPress 5.0. No plans exist to add support for this although it may be added in the future.\u003Cbr \u002F>\nOther areas of wp-admin enhanced by the plugin still work, as does the classic editor.\u003C\u002Fp>\n","Adds the last modified time to the admin interface as well as a [last-modified] shortcode to use on the front-end.",8000,83937,28,"2025-08-16T22:01:00.000Z","4.6","5.3",[97,98,99,100,101],"last-modified","modified-time","page-modified","post-modified","updated-at","https:\u002F\u002Fgithub.com\u002Faaemnnosttv\u002Flast-modified-timestamp","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flast-modified-timestamp.1.0.6.zip",{"slug":105,"name":106,"version":107,"author":108,"author_profile":109,"description":110,"short_description":111,"active_installs":112,"downloaded":113,"rating":49,"num_ratings":114,"last_updated":115,"tested_up_to":116,"requires_at_least":94,"requires_php":117,"tags":118,"homepage":122,"download_link":123,"security_score":49,"vuln_count":124,"unpatched_count":26,"last_vuln_date":125,"fetched_at":28},"bulk-datetime-change","Bulk Datetime Change","1.18","Katsushi Kawamori","https:\u002F\u002Fprofiles.wordpress.org\u002Fkatsushi-kawamori\u002F","\u003Cp>Bulk change date\u002Ftime for posts.\u003C\u002Fp>\n\u003Ch4>Changeable\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Posts.\u003C\u002Fli>\n\u003Cli>Pages.\u003C\u002Fli>\n\u003Cli>Medias.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Picker for date\u002Ftime\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Work with \u003Ca href=\"http:\u002F\u002Fxdsoft.net\u002Fjqplugins\u002Fdatetimepicker\u002F\" rel=\"nofollow ugc\">DateTimePicker\u003C\u002Fa>. jQuery plugin select date\u002Ftime.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Logs\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Displays the last 100 logs.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>How it works\u003C\u002Fh4>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002Ft6ZX51qVQ0c?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\n","Bulk change date\u002Ftime for posts.",7000,53844,8,"2025-11-25T21:39:00.000Z","6.9.4","8.0",[119,120,121,55,22],"date","media","pages","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fbulk-datetime-change\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbulk-datetime-change.1.18.zip",1,"2021-10-26 00:00:00",{"slug":127,"name":128,"version":129,"author":130,"author_profile":131,"description":132,"short_description":133,"active_installs":134,"downloaded":135,"rating":136,"num_ratings":137,"last_updated":138,"tested_up_to":116,"requires_at_least":139,"requires_php":16,"tags":140,"homepage":142,"download_link":143,"security_score":49,"vuln_count":124,"unpatched_count":26,"last_vuln_date":144,"fetched_at":28},"timed-content","Timed Content","2.97","Arno Welzel","https:\u002F\u002Fprofiles.wordpress.org\u002Fawelzel\u002F","\u003Cp>The Timed Content plugin allows users to specify that a portion of a Page or Post should appear\u002Fbe visible or disappear\u002Fbe invisible based on given time characteristics. You can also make portions of a Post or Page be visible at certain dates and times; you can even set up a schedule!\u003C\u002Fp>\n\u003Cp>The plugin adds the following:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A “client-side” shortcode that allows the marking of content to appear or disappear after a given time interval; a “fade” effect is included.  This functionality is intended to be used for special effects only, as content marked in this manner is still visible in the HTML source and, therefore, not a secure method of hiding content.\u003C\u002Fli>\n\u003Cli>Two “server-side” shortcodes that allow the marking of content to be visible only during specified date\u002Ftime intervals.  This functionality \u003Cstrong>can\u003C\u002Fstrong> be used as a secure method of hiding content, because the marked content will be included in the Page\u002FPost \u003Cstrong>only\u003C\u002Fstrong> when viewed in the specified date\u002Ftime intervals.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>A TinyMCE dialog is included to help users build the shortcodes. See the Screenshots tab for more info.\u003C\u002Fp>\n\u003Ch3>Examples\u003C\u002Fh3>\n\u003Cpre>\u003Ccode>[timed-content-client show=\"1:00\"]Show me after one minute.  Since we don't want a fade-in, we can leave it out of the \"show\" attribute completely.[\u002Ftimed-content-client]\n\n[timed-content-client show=\"1:00:1000\"]Show me after one minute with a 1000 millisecond (1 second) fade-in.[\u002Ftimed-content-client]\n\n[timed-content-client hide=\"1:00:1000\"]Hide me after one minute with a 1000 millisecond (1 second) fade-out.[\u002Ftimed-content-client]\n\n[timed-content-client show=\"1:00:500\" hide=\"5:00:2000\"]Show me after one minute with a 500 millisecond (a half-second) fade-in, then hide me after five minutes with a 2000 millisecond (2 seconds) fade-out.[\u002Ftimed-content-client]\n\n[timed-content-server show=\"2013-09-13 20:30:00 -0600\"]Show me starting at 8:30 PM Central Standard Time on September 13th, 2013. I will not be displayed before then.[\u002Ftimed-content-server]\n\n[timed-content-server hide=\"2013-09-13 20:30:00 America\u002FChicago\"]Hide me starting at 8:30 PM Central Daylight Time (i.e., the same timezone as Chicago) on September 13th, 2013.  I will not be displayed after then[\u002Ftimed-content-server]\n\n[timed-content-server show=\"2013-09-13 20:30:00 -0600\" hide=\"2013-09-13 21:30:00 -0600\"]Show me starting at 8:30 PM Central Standard Time on September 13th, 2013, then hide me an hour later. I will not be displayed before or after then.[\u002Ftimed-content-server]\n\n[timed-content-rule id=\"164\"]Display me based on the settings for the Timed Content Rule whoseID is 164.[\u002Ftimed-content-rule]\u003Ch3>Usage\u003C\u002Fh3>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>NOTE: All shortcodes can be built using the TinyMCE dialog.  When in doubt, use the dialog to create correctly formed shortcodes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The timed-content-client shortcode\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[timed-content-client show=\"mm:ss:fff\" hide=\"mm:ss:fff\"]Example Text[\u002Ftimed-content-client]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cul>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> – Specifies the time interval after loading the web page when the marked content should be displayed. The attribute consists of three parts,\u003Cbr \u002F>\nseparated by colons: \u003Ccode>mm\u003C\u002Fcode> – minutes, \u003Ccode>ss\u003C\u002Fcode> – seconds, and \u003Ccode>fff\u003C\u002Fcode> – if greater than \u003Ccode>0\u003C\u002Fcode>, a fade-in effect lasting \u003Ccode>fff\u003C\u002Fcode> milliseconds is applied.\u003C\u002Fli>\n\u003Cli>\u003Ccode>hide\u003C\u002Fcode> – Specifies the time interval after loading the web page when the marked content should be hidden. The attribute consists of three parts,\u003Cbr \u002F>\nseparated by colons: \u003Ccode>mm\u003C\u002Fcode> – minutes, \u003Ccode>ss\u003C\u002Fcode> – seconds, and \u003Ccode>fff\u003C\u002Fcode> – if greater than \u003Ccode>0\u003C\u002Fcode>, a fade-out effect lasting \u003Ccode>fff\u003C\u002Fcode> milliseconds is applied.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Both attributes are optional, but at least one attribute must be included. Leading zeros (0) are optional. The shortcode’s behaviour depends on which attributes are used:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> only – Marked content is initially not visible, then appears \u003Ccode>mm\u003C\u002Fcode> minutes and \u003Ccode>ss\u003C\u002Fcode> seconds after loading with a \u003Ccode>fff\u003C\u002Fcode> millisecond fade-in.\u003C\u002Fli>\n\u003Cli>\u003Ccode>hide\u003C\u002Fcode> only – Marked content is initially visible, then disappears \u003Ccode>mm\u003C\u002Fcode> minutes and \u003Ccode>ss\u003C\u002Fcode> seconds after loading with a \u003Ccode>fff\u003C\u002Fcode> millisecond fade-out.\u003C\u002Fli>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> and \u003Ccode>hide\u003C\u002Fcode> – Marked content is initially not visible, then appears according to the values set in \u003Ccode>show\u003C\u002Fcode>, then disappears according to the values set in \u003Ccode>hide\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Your users must have JavaScript enabled for this shortcode to work.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The timed-content-server shortcode\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[timed-content-server show=\"datetime\" hide=\"datetime\" debug=\"true|false|when_hidden\"]Example Text[\u002Ftimed-content-server]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cul>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> – Specifies the date\u002Ftime when the marked content should start being included on the web page.\u003C\u002Fli>\n\u003Cli>\u003Ccode>hide\u003C\u002Fcode> – Specifies the date\u002Ftime after which the marked content should stop being included on the web page.\u003C\u002Fli>\n\u003Cli>\u003Ccode>debug\u003C\u002Fcode> – If \u003Ccode>true\u003C\u002Fcode>, adds some debugging statements to the web page as HTML comments. If \u003Ccode>when_hidden\u003C\u002Fcode>, the debugging statements are added only when the content is hidden. Defaults to \u003Ccode>false\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The date and time are expected to be yyyy-mm-dd HH:MM (similar to ISO 8601), for example \u003Ccode>2019-04-07 15:30\u003C\u002Fcode> for April 7, 2019, 15:30. For backward compatiblity old “human readable” date formats should also work, but these should not be used any longer!\u003C\u002Fp>\n\u003Cp>In addition you can provide a timezone in the date\u002Ftime parameter either as name or as offset like \u003Ccode>2019-04-07 15:30 America\u002FChicago\u003C\u002Fcode> or \u003Ccode>2019-04-07 15:30 +0200\u003C\u002Fcode>. If you do not provide a timezone, the WordPress timezone setting will be used as default.\u003C\u002Fp>\n\u003Cp>Both \u003Ccode>show\u003C\u002Fcode> and \u003Ccode>hide\u003C\u002Fcode> attributes are optional, but at least one attribute must be included. The shortcode’s behaviour depends on which attributes are used:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> only – Marked content is outputted only after the date\u002Ftime set here.\u003C\u002Fli>\n\u003Cli>\u003Ccode>hide\u003C\u002Fcode> only – Marked content is outputted only before the date\u002Ftime set here.\u003C\u002Fli>\n\u003Cli>\u003Ccode>show\u003C\u002Fcode> and \u003Ccode>hide\u003C\u002Fcode> – Marked content is outputted only during the time period defined by the \u003Ccode>show\u003C\u002Fcode> and \u003Ccode>hide\u003C\u002Fcode> attributes.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>The timed-content-rule shortcode\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[timed-content-rule id=\"{rule_id}|{rule_name}\"]Example Text[\u002Ftimed-content-rule]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can find the correct shortcode from the Timed Content Rules overview page, or use the TinyMCE dialog.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Testing server side rules\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>For testing the behaviour of server side rules at specific times, you may use the GET parameter \u003Ccode>tctest\u003C\u002Fcode> in an URL, followed by date and time in the format \u003Ccode>YYYY-MM-DD+hh:mm:ss\u003C\u002Fcode>. This works only you are logged in with a user which has the right to edit the displayed page or post. For example: \u003Ccode>http:\u002F\u002Fmysite.example?tctest=2018-02-10+19:16:00\u003C\u002Fcode> will show the content as if it was February 10, 2018 at 19:16.\u003C\u002Fp>\n\u003Ch3>Developer Documentation\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Action hooks\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_action( \"timed_content_server_show\", \"{function_name}\", {priority_level}, 4 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Fired when the \u003Ccode>[timed-content-server]\u003C\u002Fcode> shortcode is encountered \u003Cem>AND\u003C\u002Fem> the content is to be displayed based on the shortcode’s show\u002Fhide attributes.  Functions using this hook should accept the following arguments in order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$post_id\u003C\u002Fcode> – the ID of the currently displayed Post\u002FPage\u003C\u002Fli>\n\u003Cli>\u003Ccode>$show\u003C\u002Fcode> – the value of the \u003Ccode>show\u003C\u002Fcode> attribute. If not set, defaults to “1970-Jan-01 00:00:00 +000”\u003C\u002Fli>\n\u003Cli>\u003Ccode>$hide\u003C\u002Fcode> – the value of the \u003Ccode>hide\u003C\u002Fcode> attribute. If not set, defaults to “2038-Jan-19 03:14:07 +000”\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>$content\u003C\u002Fcode> – The content enclosed by the shortcode\u003C\u002Fp>\n\u003Cp>add_action( “timed_content_server_hide”, “{function_name}”, {priority_level}, 4 );\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Fired when the \u003Ccode>[timed-content-server]\u003C\u002Fcode> shortcode is encountered \u003Cem>AND\u003C\u002Fem> the content is to be hidden based on the shortcode’s show\u002Fhide attributes.  Functions using this hook should accept the following arguments in order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$post_id\u003C\u002Fcode> – the ID of the currently displayed Post\u002FPage\u003C\u002Fli>\n\u003Cli>\u003Ccode>$show\u003C\u002Fcode> – the value of the \u003Ccode>show\u003C\u002Fcode> attribute. If not set, defaults to “1970-Jan-01 00:00:00 +000”\u003C\u002Fli>\n\u003Cli>\u003Ccode>$hide\u003C\u002Fcode> – the value of the \u003Ccode>hide\u003C\u002Fcode> attribute. If not set, defaults to “2038-Jan-19 03:14:07 +000”\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>$content\u003C\u002Fcode> – The content enclosed by the shortcode\u003C\u002Fp>\n\u003Cp>add_action( “timed_content_rule_show”, “{function_name}”, {priority_level}, 3 );\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Fired when the \u003Ccode>[timed-content-rule]\u003C\u002Fcode> shortcode is encountered \u003Cem>AND\u003C\u002Fem> the content is to be displayed based on the Timed Content Rule’s properties.  Functions using this hook should accept the following arguments in order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$post_id\u003C\u002Fcode> – the ID of the currently displayed Post\u002FPage\u003C\u002Fli>\n\u003Cli>\u003Ccode>$rule_id\u003C\u002Fcode> – the ID of the Timed Content Rule being called. Use \u003Ccode>get_post_meta( $rule_id )\u003C\u002Fcode> to get the Rule’s properties.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>$content\u003C\u002Fcode> – The content enclosed by the shortcode\u003C\u002Fp>\n\u003Cp>add_action( “timed_content_rule_hide”, “{function_name}”, {priority_level}, 3 );\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Fired when the \u003Ccode>[timed-content-rule]\u003C\u002Fcode> shortcode is encountered \u003Cem>AND\u003C\u002Fem> the content is to be hidden based on the Timed Content Rule’s properties.  Functions using this hook should accept the following arguments in order:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$post_id\u003C\u002Fcode> – the ID of the currently displayed Post\u002FPage\u003C\u002Fli>\n\u003Cli>\u003Ccode>$rule_id\u003C\u002Fcode> – the ID of the Timed Content Rule being called. Use \u003Ccode>get_post_meta( $rule_id )\u003C\u002Fcode> to get the Rule’s properties.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$content\u003C\u002Fcode> – The content enclosed by the shortcode\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Filter hooks\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>timed_content_filter\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Filter for any content enclosed by a Timed Content shortcode.  Implements the same filters as \u003Ccode>the_content\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wptexturize\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>convert_smilies\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>convert_chars\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>wpautop\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>prepend_attachment\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ccode>do_shortcode\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>timed_content_filter_override\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Replaces the \u003Ccode>timed_content_filter\u003C\u002Fcode> with another pre-existing filter to use for any content enclosed by a Timed Content shortcode.  Any function hooked into this filter must return the name of a filter (as a string).\u003C\u002Fp>\n","Plugin to show or hide portions of a Page or Post based on specific date\u002Ftime characteristics.",6000,219287,92,41,"2025-12-02T23:43:00.000Z","3.8",[141,21,127],"marketing-tool","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Ftimed-content\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftimed-content.2.97.zip","2023-01-24 00:00:00",{"attackSurface":146,"codeSignals":157,"taintFlows":164,"riskAssessment":165,"analyzedAt":172},{"hooks":147,"ajaxHandlers":148,"restRoutes":149,"shortcodes":150,"cronEvents":156,"entryPointCount":124,"unprotectedCount":26},[],[],[],[151],{"tag":152,"callback":153,"file":154,"line":155},"scheduler","jps_schduler","schedule-your-content.php",11,[],{"dangerousFunctions":158,"sqlUsage":159,"outputEscaping":161,"fileOperations":26,"externalRequests":26,"nonceChecks":26,"capabilityChecks":26,"bundledLibraries":163},[],{"prepared":26,"raw":26,"locations":160},[],{"escaped":26,"rawEcho":26,"locations":162},[],[],[],{"summary":166,"deductions":167},"Based on the provided static analysis and vulnerability history, the 'schedule-your-content' plugin v1.0 exhibits a generally strong security posture for this version. The absence of dangerous functions, file operations, external HTTP requests, and the exclusive use of prepared statements for SQL queries are excellent indicators of secure coding practices. Furthermore, the 100% output escaping and the lack of any recorded vulnerabilities or CVEs significantly bolster its security reputation. \n\nHowever, a notable concern arises from the absence of nonce and capability checks across all identified entry points, including the single shortcode. While the attack surface is currently small (only one shortcode), this lack of authentication and authorization validation represents a potential security weakness. If this shortcode were to handle any user-supplied input that affects site functionality or displays sensitive information, it could be susceptible to various attacks like Cross-Site Request Forgery (CSRF) or unauthorized access. \n\nIn conclusion, while the plugin's current version demonstrates diligent secure coding in many areas and benefits from a clean vulnerability history, the complete omission of nonce and capability checks on its entry points is a critical oversight that requires immediate attention to mitigate potential risks. This is a significant weakness that needs to be addressed in future versions or through updates.",[168,170],{"reason":169,"points":114},"Missing Nonce checks on shortcode",{"reason":171,"points":114},"Missing Capability checks on shortcode","2026-03-16T23:41:51.053Z",{"wat":174,"direct":179},{"assetPaths":175,"generatorPatterns":176,"scriptPaths":177,"versionParams":178},[],[],[],[],{"cssClasses":180,"htmlComments":181,"htmlAttributes":182,"restEndpoints":183,"jsGlobals":184,"shortcodeOutput":185},[],[],[],[],[],[186],"[scheduler"]