PublishPress Future: WordPress-Beiträge automatisch deaktivieren

Beschreibung

Das Plugin „PublishPress Future“ ermöglicht es, ein Ablaufdatum zu Beiträgen, Seiten und anderen Inhaltstypen hinzuzufügen. Du kannst damit den Status von Beiträgen und Seiten automatisch ändern, sie löschen oder die Beitragskategorien ändern.

Hier ist ein Überblick, was Du mit PublishPress Future machen kannst:

  • Wähle Ablaufdaten für die Inhalte in jedem Post-Type.
  • Wähle Ablaufdaten in der rechten Sidebar beim Bearbeiten der Beiträge.
  • Ändere, verschiebe oder lösche Inhalt, wenn das Ablaufdatum erreicht wird.
  • Ändere Ablaufdaten mit „Quick Edit“ und „Mehrfachaktionen“.
  • Erhalte E-Mails, wenn Dein Inhalt abläuft.
  • Zeige das Ablaufdatum im Inhalt, automatisch oder mit Shortcode.

Optionen für den Ablauf von Beiträgen

Wenn Dein Beitrag abläuft, kannst Du diese Änderungen beim Inhalt ausführen:

  • Ändere den Status auf „Entwurf“
  • Lösche den Beitrag.
  • Ändere den Status auf „Papierkorb“.
  • Ändere den Status auf „Privat“.
  • Füge die Option „Sticky“ hinzu.
  • Entferne die Option „Sticky“.
  • Entferne alle Kategorien und füge neue Kategorien hinzu.
  • Behalte alle Kategorien und füge weitere Kategorien hinzu.
  • Behalte alle vorhandenen Kategorien, ausgenommen den in dieser Änderung festgelegten.

Klick hier für weitere Details über Ablaufdaten von Beiträgen.

Zeige das Ablaufdatum in Deinem Inhalt

PublishPress Future ermöglicht es, das Ablaufdatum automatisch innerhalb von Beiträgen anzuzeigen. Das Ablaufdatum wird am Ende des Beitrages angezeigt

Klick hier um die Optionen zur Anzeige im Footer zu sehen.

Du kannst Shortcodes verwenden, um das Ablaufdatum innerhalb von Beiträgen anzuzeigen. Du kannst den Shortcode mit Hilfe einiger Optionen individuell anpassen.

Klick hier um die Shortcode Optionen zu sehen.

Standard-Ablaufwerte für Post-Types

„PublishPress Future“ unterstützt jeden Beitragstyp in WordPress. Gehe zu Einstellungen > PublishPress Future > Allgemeine Einstellungen um Standardeinstellungen für jeden Beitragstyp individuell festzulegen.

Klick hier um die Standardeinstellungen zu sehen.

PublishPress Future E-Mail Nachrichten

Das Plugin „PublishPress Future“ kann E-Mail-Nachrichten senden, wenn ein Inhalt deaktiviert wird. Du kannst die E-Mails einrichten unter Einstellungen > Post Expirator > Allgemeine Einstellungen.

Klick hier um die Optionen für Benachrichtigungen zu sehen.

Details, wie Post Expirator funktioniert

Für jedes Ablauf-Ereignis wird ein individueller Cronjob geplant. Das kann helfen die Last für den Server zu reduzieren. Dieses Plugin ERFORDERT es, das WP-CRON eingerichtet ist und auf Deinem Server läuft. Einige Hoster unterstützen das nicht, deshalb überprüfe das zuerst, falls es Probleme mit dem Plugin geben sollte

Klick hier um die technischen Details des Plugins zu sehen.

Screenshots

  • Verfallsdatum zum Beitrag hinzufügen
  • Die Verfallsdaten auf der Beitragsübersicht ansehen.
  • Das Einstellungen-Fenster

Installation

In diesem Abschnitt wird beschrieben, wie du das Plugin installieren kannst und wie es arbeitet.

  1. Entpacke den Plugin-Inhalt in den /wp-content/plugins/post-expirator/-Ordner
  2. Aktiviere das Plugin mittels dem ‚Plugins‘-Menü in WordPress

Rezensionen

30. November 2022 1 Antwort
I used Publish Press Future to unpublish posts within my home page's "Latest News" section. Here's how: I used the Content Views plugin to organize and display the posts within this section. Then for each post, I can set its expiration date and time. When the time arrives, the post goes to Draft mode, meaning it simply disappears from public view, but it's still available for admins to reuse. The website owner loves not having to log in to remove these event posts from the home page. The documentation was easy to follow. The ability to expire posts like this should be a part of core WordPress.
24. November 2022 1 Antwort
Work excellent, super practical for many situations! Keep the great job on this plugin!
3. November 2022 1 Antwort
We are a church with many events and news items always flowing onto the website. We can't live without this plugin!!! Otherwise we would never be able to keep track of how to expire all those posts when needed. Occasionally we even have news items that need to start and end on certain days. This plugin allows us to set and forget, and it manages the post automatically. We have found it very reliable as well. Great job!
Alle 131 Rezensionen lesen

Mitwirkende & Entwickler

„PublishPress Future: WordPress-Beiträge automatisch deaktivieren“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

„PublishPress Future: WordPress-Beiträge automatisch deaktivieren“ wurde in 17 Sprachen übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „PublishPress Future: WordPress-Beiträge automatisch deaktivieren“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

[2.8.0] – 08 Nov, 2022

  • ADDED: Add translations for ES, FR, IT languages, #297;
  • FIXED: Fix the expire date column in WooCommerce products list, #276;
  • CHANGED: Removed the „None“ option from default expiration dates. If a site is using it, the default value is now „Custom“ and set for „+1 week“, #274;
  • FIXED: Improve output escaping on a few views, #235;
  • FIXED: Improve input sanitization, #235;
  • FIXED: Add argument swapping on strings with multiple arguments, #305;
  • FIXED: Expiration settings not working on Classic Editor, #274;
  • FIXED: Fixed remaining message „Cron event not found!“ for expirations that run successfully, #288;
  • CHANGED: The code was partially refactored improving the code quality, applying DRY and other good practices;
  • CHANGED: Deprecated some internal functions: postexpirator_activate, postexpirator_autoload, postexpirator_schedule_event, postexpirator_unschedule_event, postexpirator_debug, _postexpirator_get_cat_names, postexpirator_register_expiration_meta, postexpirator_expire_post, expirationdate_deactivate;
  • CHANGED: Deprecated the constant: PostExpirator_Facade::PostExpirator_Facade => PublishPressFuture\Modules\Expirator\CapabilitiesAbstract::EXPIRE_POST;
  • CHANGED: Deprecated the constant POSTEXPIRATOR_DEBUG;
  • CHANGED: Deprecated the method PostExpirator_Facade::set_expire_principles;
  • CHANGED: Deprecated the method PostExpirator_Facade::current_user_can_expire_posts;
  • CHANGED: Deprecated the method PostExpirator_Facade::get_default_expiry;
  • CHANGED: Deprecated the method PostExpirator_Util::get_wp_date;
  • CHANGED: Deprecated the class PostExpiratorDebug;
  • CHANGED: Deprecated the constants: POSTEXPIRATOR_VERSION, POSTEXPIRATOR_DATEFORMAT, POSTEXPIRATOR_TIMEFORMAT, POSTEXPIRATOR_FOOTERCONTENTS, POSTEXPIRATOR_FOOTERSTYLE, POSTEXPIRATOR_FOOTERDISPLAY, POSTEXPIRATOR_EMAILNOTIFICATION, POSTEXPIRATOR_EMAILNOTIFICATIONADMINS, POSTEXPIRATOR_DEBUGDEFAULT, POSTEXPIRATOR_EXPIREDEFAULT, POSTEXPIRATOR_SLUG, POSTEXPIRATOR_BASEDIR, POSTEXPIRATOR_BASENAME, POSTEXPIRATOR_BASEURL, POSTEXPIRATOR_LOADED, POSTEXPIRATOR_LEGACYDIR;

[2.7.8] – 17 Oct, 2022

  • CHANGED: Rename „Category“ in the expiration options to use a more generic term: „Taxonomy“;
  • CHANGED: Fixed typo in the classical metabox (classical editor);
  • FIXED: Fix bulk edit when expiration is not enabled for the post type, #281;
  • FIXED: Fix custom taxonomies support, #50;

[2.7.7] – 14 Jul, 2022

  • ADDED: Add post meta „expiration_log“ with expiration log data when post expires;
  • FIXED: Can’t bulk edit posts if hour or minutes are set to 00, #273;
  • FIXED: When the post expires to draft we don’t trigger the status transition actions, #264;

[2.7.6] – 13 Jun, 2022

  • FIXED: Fix fatal error on cron if debug is not activated, #265;

[2.7.5] – 09 Jun, 2022

  • FIXED: Fix undefined array key „hook_suffix“ warning, #259;
  • FIXED: Double email sending bug confirmed bug, #204;

[2.7.4] – 07 Jun, 2022

  • CHANGED: Add library to protect breaking site when multiple instances of the plugin are activated;
  • CHANGED: Invert order of the debug log, showing now on ASC order;
  • CHANGED: Make bulk edit date fields required, #256;
  • FIXED: Fix unlocalized string on the taxonomy field (Thanks to Alex Lion), #255;
  • FIXED: Fix default taxonomy selection for Post Types in the settings, #144;
  • FIXED: Fix typo in the hook name ‚postexpirator_schedule‘ (Thanks to Nico Mollet), #244;
  • FIXED: Fix bulk editing for WordPress v6.0, #251;
  • FIXED: Fix the Gutenberg panel for custom post types created on PODS in WordPress v6.0, #250;

[2.7.3] – 27 Jan 2022

  • FIXED: Fix the selection of categories when setting a post to expire, #220;

[2.7.2] – 25 Jan 2022

  • ADDED: Added the event GUID as tooltip to each post in the Current Cron Schedule list on the Diagnostics page, #214;
  • CHANGED: Added more clear debug message if the cron event was not scheduled due to an error;
  • CHANGED: Refactored the list of cron schedules in the Diagnostics tab adding more post information, #215;
  • CHANGED: Removed the admin notice about the plugin renaming;
  • FIXED: Fix the Expires column in the posts page correctly identifying the post ID on cron event with multiple IDs, #210;
  • FIXED: Fix wrong function used to escape a html attributes on a setting page;
  • FIXED: Fix missed sanitization for some data on admin pages;
  • FIXED: Fix some false positives given by PHPCS;
  • FIXED: Fix expiration data processing avoid to process for deactivated posts;
  • FIXED: Fix a typo in the diagnostics settings tab;
  • FIXED: Fix the checkbox state for posts that are not set to expire, #217;

[2.7.1] – 12 Jan 2022

  • ADDED: Add visual indicator to the cron event status in the settings page, #155;
  • ADDED: Add small help text to the Expires column icon to say if the event is scheduled or not;
  • ADDED: Add additional permission check before loading the settings page;
  • ADDED: Add CLI command to expire a post, #206;
  • CHANGED: Remove the plugin description from the settings page, #194;
  • CHANGED: Deprecated a not used function called „expirationdate_get_blog_url“;
  • CHANGED: Updated the min required WP to 5.3 due to the requirement of using the function ‚wp_date‘;
  • FIXED: Fix PHP error while purging the debug log, #135;
  • FIXED: Fix composer’s autoloader path;
  • FIXED: Code cleanup. Removed comments and dead code;
  • FIXED: Fixed the block for direct access to view files;
  • FIXED: Added check for is_admin before checking if the user has permission to see the settings page;
  • FIXED: Avoid running sortable column code if not in the admin;
  • FIXED: Cross-site scripting (XSS) was possible if a third party allowed html or javascript into a database setting or language file;
  • FIXED: Fix the URL for the View Debug Log admin page, #196;
  • FIXED: Removed unopened span tag from a form;
  • FIXED: Added a secondary admin and ajax referer check when saving expiration post data;
  • FIXED: Fix the option „Preserve data after deactivating the plugin“ that was not saving the setting, #198;
  • FIXED: Fix the post expiration function to make sure a post is not expired if the checkbox is not checked on it, #199;
  • FIXED: Fix the post expiration meta not being cleanup after a post expires, #207;
  • FIXED: Fix the post expiration checkbox status when post type is set configured to check it by default;

[2.7.0] – 02 Dec 2021

  • ADDED: Add new admin menu item: Future, #8;
  • CHANGED: Rename the plugin from Post Expirator to PublishPress Future, #14;
  • CHANGED: Add the PublishPress footer and branding, #68;
  • CHANGED: Separate the settings into different tabs, #97, #98;
  • CHANGED: Rename the „General Settings“ tab to „Default“, #99;
  • FIXED: Fix the 1hr diff between expiration time when editing and shown in post list, #138;
  • FIXED: Post Expirator is adding wrong expiry dates to old posts, #160;
  • FIXED: Post Expirator is setting unwanted expire time for posts, #187;

[2.6.3] – 18 Nov 2021

  • ADDED: Add setting field for choosing between preserve or delete data when the plugin is deactivated, #137;
  • FIXED: Fix the timezone applied to time fields, #134;
  • FIXED: Add the timezone string to the time fields, #134;
  • FIXED: Fix the selected expiring categories on the quick edit panel, #160;
  • FIXED: Fix E_COMPILER_ERROR when cleaning up the debug table, #183;
  • FIXED: Fix translation and localization of date and time, #150;

[2.6.2] – 04 Nov 2021

  • FIXED: Fix fatal error: Call to a member function add_cap() on null, #167;
  • FIXED: Fix hierarchical taxonomy selection error for multiple taxonomies, #144;
  • FIXED: Fix PHP warning: use of undefined constant – assumed ‚expireType‘, #617;
  • FIXED: Fix translation of strings in the block editor panel, #163;
  • FIXED: Fix category not being added or removed when the post expires, #170;
  • FIXED: Fix PHP notice: Undefined variable: merged, #174;
  • FIXED: Fix category-based expiration for custom post types in classic editor, #179;
  • FIXED: Fix expiration date being added to old posts when edited, #168;

[2.6.1] – 27 Oct 2021

  • ADDED: Add post information to the scheduled list for easier debugging, #164;
  • ADDED: Add a review request after a specific period of usage, #103;
  • ADDED: Improve the list of cron tasks, filtering only the tasks related to the plugin, #153;
  • FIXED: Fix category replace not saving, #159;
  • FIXED: Fix auto enabled settings, #158;
  • FIXED: Fix expiration data and cron on Gutenberg style box, #156, #136;
  • FIXED: Fix the request that loads categories in the Gutenberg style panel, #133;
  • FIXED: Fix the category replace not working with the new Gutenberg style panel, #127;
  • FIXED: Fix the default options for the Gutenberg style panel, #145;

[2.6.0] – 04 Oct 2021

  • ADDED: Add specific capabilities for expiring posts, #141;

[2.5.1] – 27 Sep 2021

  • FIXED: Default Expiration Categories cannot be unset, #94;
  • FIXED: Tidy up design for Classic Editor version, #83;
  • FIXED: All posts now carry the default expiration, #115;
  • FIXED: Error with 2.5.0 and WordPress 5.8.1, #110;
  • FIXED: Do not show private post types that don’t have an admin UI, #116;

[2.5.0] – 08 Aug 2021

  • ADDED: Add „How to Expire“ to Quick Edit, #62;
  • ADDED: Support for Gutenberg block editor, #10;
  • ADDED: Set a default time per post type, #12;
  • CHANGED: Settings UI enhancement, #14;
  • FIXED: Appearance Widgets screen shows PHP Notice, #92;
  • FIXED: Stop the PublishPress Future box from appearing in non-public post types, #78;
  • FIXED: Hide metabox from Media Library files, #56;

[2.4.4] – 22 Jul 2021

  • FIXED: Fix conflict with the plugin WCFM, #60;
  • FIXED: Fix the Category: Remove option, #61;

[2.4.3] – 07 Jul 2021

  • ADDED: Expose wrappers for legacy functions, #40;
  • ADDED: Support for quotes in Default expiry, #43;
  • CHANGED: Bulk and Quick Edit boxes default to current date/year, #46;
  • FIXED: Default expiry duration is broken for future years, #39;
  • FIXED: Translation bug, #5;
  • FIXED: Post expiring one year early, #24;

[2.4.2]

  • FIXED: Bulk edit does not change scheduled event bug, #29;
  • FIXED: Date not being translated in shortcode, #16;
  • FIXED: Bulk Edit doesn’t work, #4;

[2.4.1]

  • FIXED: Updated deprecated .live jQuery reference.

[2.4.0]

  • FIXED: Fixed PHP Error with PHP 7.

[2.3.1]

  • FIXED: Fixed PHP Error that snuck in on some installations.

[2.3.0]

  • ADDED: Email notification upon post expiration. A global email can be set, blog admins can be selected and/or specific users based on post type can be notified.
  • ADDED: Expiration Option Added – Stick/Unstick post is now available.
  • ADDED: Expiration Option Added – Trash post is now available.
  • ADDED: Added custom actions that can be hooked into when expiration events are scheduled / unscheduled.
  • FIXED: Minor HTML Code Issues

[2.2.2]

  • FIXED: Quick Edit did not retain the expire type setting, and defaulted back to „Draft“. This has been resolved.

[2.2.1]

  • FIXED: Fixed issue with bulk edit not correctly updating the expiration date.

[2.2.0]

  • ADDED: Quick Edit – setting expiration date and toggling post expiration status can now be done via quick edit.
  • ADDED: Bulk Edit – changing expiration date on posts that already are configured can now be done via bulk edit.
  • ADDED: Added ability to order by Expiration Date in dashboard.
  • ADDED: Adjusted formatting on defaults page. Multiple post types are now displayed cleaner.
  • Fix: Minor Code Cleanup

[2.1.4]

  • Fix: PHP Strict errors with 5.4+
  • Fix: Removed temporary timezone conversion – now using core functions again

[2.1.3]

  • Fix: Default category selection now saves correctly on default settings screen

[2.1.2]

  • New: Added check to show if WP_CRON is enabled on diagnostics page
  • Fix: Minor Code Cleanup
  • Security: Added form nonce for protect agaisnt possible CSRF
  • Security: Fixed XSS issue on settings pages

[2.1.1]

  • New: Added the option to disable post expirator for certain post types if desired
  • Fix: Fixed php warning issue cause when post type defaults are not set

[2.1.0]

  • New: Added support for heirarchical custom taxonomy
  • New: Enhanced custom post type support
  • Fix: Updated debug function to be friendly for scripted calls
  • Fix: Change to only show public custom post types on defaults screen
  • Fix: Removed category expiration options for ‚pages‘, which is currently unsupported
  • Fix: Some date calls were getting „double“ converted for the timezone pending how other plugins handled date – this issue should now be resolved

[2.0.1]

  • CHANGED: Old option cleanup
  • Removes old scheduled hook – this was not done completely in the 2.0.0 upgrade

[2.0.0]

  • New: Improved debug calls and logging
  • New: Added the ability to expire to a „private“ post
  • New: Added the ability to expire by adding or removing categories. The old way of doing things is now known as replacing categories
  • New: Revamped the expiration process – the plugin no longer runs on an minute, hourly, or other schedule. Each expiration event schedules a unique event to run, conserving system resources and making things more efficient
  • New: The type of expiration event can be selected for each post, directly from the post editing screen
  • New: Ability to set defaults for each post type (including custom posts)
  • New: Renamed expiration-date meta value to _expiration-date
  • New: Revamped timezone handling to be more correct with WordPress standards and fix conflicts with other plugins
  • New: ‚Expires‘ column on post display table now uses the default date/time formats set for the blog
  • Fix: Removed kses filter calls when then schedule task runs that was causing code entered as unfiltered_html to be removed
  • Fix: Updated some calls of date to now use date_i18n
  • Fix: Most (if not all) php error/warnings should be addressed
  • Fix: Updated wpdb calls in the debug class to use wpdb_prepare correctly
  • Fix: Changed menu capability option from „edit_plugin“ to „manage_options“

This is a major update of the core functions of this plugin. All current plugins and settings should be upgraded to the new formats and work as expected. Any posts currently schedule to be expirated in the future will be automatically upgraded to the new format.

[1.6.2]

  • Added the ability to configure the post expirator to be enabled by default for all new posts
  • Changed some instances of mktime to time
  • Fixed missing global call for MS installs

[1.6.1]

  • Added option to allow user to select any cron schedule (minute, hourly, twicedaily, daily) – including other defined schedules
  • Added option to set default expiration duration – options are none, custom, or publish time
  • Tweaked error messages, removed clicks for reset cron event
  • Switched cron schedule functions to use „current_time(‚timestamp‘)“
  • FIXED: Cleaned up default values code
  • FIXED: Code cleanup – php notice

[1.6]

  • ADDED: Added debugging
  • Replaced „Upgrade“ tab with new „Diagnostics“ tab
  • CHANGED: Various code cleanup
  • FIXED: Fixed invalid html
  • FIXED: Fixed i18n issues with dates
  • Fixed problem when using „Network Activate“ – reworked plugin activation process
  • Reworked expire logic to limit the number of sql queries needed

[1.5.4]

  • CHANGED: Cleaned up deprecated function calls

[1.5.3]

  • Fixed bug with sql expiration query (props to Robert & John)

[1.5.2]

  • Fixed bug with shortcode that was displaying the expiration date in the incorrect timezone
  • Fixed typo on settings page with incorrect shortcode name

[1.5.1]

  • Fixed bug that was not allow custom post types to work

[1.5]

  • Moved Expirator Box to Sidebar and cleaned up meta code
  • Added ability to expire post to category

[1.4.3]

  • Fixed issue with 3.0 multisite detection

[1.4.2]

  • Added post expirator POT to /languages folder
  • Fixed issue with plugin admin navigation
  • Fixed timezone issue on plugin options screen

[1.4.1]

  • Added support for custom post types (Thanks Thierry)
  • Added i18n support (Thanks Thierry)
  • Fixed issue where expiration date was not shown in the correct timezone in the footer
  • Fixed issue where on some systems the expiration did not happen when scheduled

[1.4]

  • Fixed compatability issues with WordPress – plugin was originally coded for WPMU – should now work on both
  • Added ability to schedule post expiration by minute
  • Fixed timezone – now uses the same timezone as configured by the blog

Achtung: Nach dem Updaten kann es nötig werden die Cron-Zeitpläne zurückzusetzen. Geplante Beiträge werden nicht upgedatet, sie werden gemäß der alten Zeitzoneneinstellung gelöscht. Wenn du sie updaten willst, musst die Verfallszeit manuell anpassen.

[1.3.1]

  • Fixed sporadic issue of expired posts not being removed

[1.3]

  • Expiration date is now retained across all post status changes
  • Modified date/time format options for shortcode postexpirator tag
  • Added the ability to add text automatically to the post footer if expiration date is set

[1.2.1]

  • Fixed issue with display date format not being recognized after upgrade

[1.2]

  • Changed wording from „Expiration Date“ to „Post Expirator“ and moved the configuration options to the „Settings“ tab.
  • ADDED: Added shortcode tag [postexpirator] to display the post expiration date within the post
  • ADDED: Added new setting for the default format
  • Fixed bug where expiration date was removed when a post was auto saved

[1.1]

  • Expired posts retain expiration date

[1.0]

  • ADDED: Initial Release