WordPress.org

Plugin Directory

Schedule Post Changes: Unpublish, Delete, Change Status, Trash, Change Categories and Tags with PublishPress Future

Schedule Post Changes: Unpublish, Delete, Change Status, Trash, Change Categories and Tags with PublishPress Future

Beschreibung

Mit dem PublishPress Future-Plug-in kannst Du automatische Änderungen an Beiträgen, Seiten und anderen Inhaltstypen planen. An einem von Dir gewählten Datum kann PublishPress Future Deinen Beitrag löschen, den Status ändern, die Beitragskategorien aktualisieren oder andere Änderungen vornehmen.

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

  • Wähle Daten, um die Veröffentlichung Deiner Beiträge rückgängig zu machen.
  • Ändere, verschiebe oder lösche Inhalt, wenn das Ablaufdatum erreicht wird.
  • Kategorien hinzufügen oder entfernen.
  • Ändere Ablaufdaten mit „Quick Edit“ und „Mehrfachaktionen“.
  • Erhalte E-Mails, sobald das Ablaufdatum eintritt.
  • Zeige das Ablaufdatum im Inhalt, automatisch oder mit Shortcode.
  • Kontrolliere Beitragsänderungen über Integrationen mit Advanced Custom Fields und anderen Plugins (verfügbar in der Pro-Version).
  • Importiere Änderungen über ein Plugin wie WP All Import (verfügbar in der Pro-Version).

PublishPress Future Pro

Upgrade auf PublishPress Future Pro
Dieses Plugin ist die kostenlose Version des PublishPress Future-Plugins. Die Pro-Version enthält alle Funktionen, die Du zum Planen von Änderungen an Deinen WordPress-Inhalten benötigst. Klicke hier, um jetzt das beste Premium-Plugin für die Planung von WordPress-Inhaltsaktualisierungen zu kaufen!

Optionen für zukünftige Aktionen bei Beiträgen

Mit PublishPress Future kannst Du Aktionen konfigurieren, die automatisch mit Deinen Inhalten ausgeführt werden. Hier sind die Änderungen, die Du für Deine Beiträge auswählen kannst:

  • Ä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.
  • Verschiebe den Beitrag in einen benutzerdefinierten Status (verfügbar in der Pro-Version).

Klicke hier für weitere Details über das Planen von Beitragsänderungen.

Zeige das Aktionsdatum in Deinem Inhalt

PublishPress Future ermöglicht es Dir, das Ablaufdatum oder ein Aktionsdatum 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 geändert wird. Du kannst die E-Mails einrichten unter Einstellungen > PublishPress Future > Allgemeine Einstellungen.

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

Integrationen mit anderen Plugins

In PublishPress Future Pro ist es möglich, Änderungen an Deinen Beiträgen basierend auf Metadaten zu planen. Dadurch ist es möglich, PublishPress Future mit anderen Plugins zu integrieren. Du kannst beispielsweise im Plugin „Advanced Custom Fields“ ein Datumsfeld erstellen und dieses verwenden, um das Datum für zukünftige Aktionen zu steuern.

Wenn Du eine Integration verwendest, gibt es fünf Arten von Daten, die Du in PublishPress Future aktualisieren kannst:

  • Aktionsstatus: Dieses Feld gibt an, ob die Aktion aktiviert werden soll.
  • Aktionsdatum: In diesem Feld wird das geplante Datum für die Aktion gespeichert.
  • Aktionstyp: In diesem Feld wird der Typ der Aktion gespeichert, die ausgeführt wird.
  • Taxonomie-Name: Der Taxonomiename, der bei der Auswahl von Begriffen verwendet wird.
  • Taxonomie-Begriffe: Eine Liste der Begriffs-IDs, die von der Aktion verwendet werden.

Klicke hier, um zu sehen, wie Du Future mit anderen Plugins integrieren kannst.

Importiere die zukünftigen Aktionen

PublishPress Future Pro unterstützt Importe aus externen Datenquellen. Du kannst Beiträge importieren und automatisch zukünftige Aktionen erstellen, die diesen Beiträgen zugeordnet sind.

Der beste Ansatz ist die Verwendung der Metadaten-Planungsfunktion. Wenn Du ein Plugin wie WP All Import verwendest, kannst Du die Importtabellen mit den Feldern abgleichen, die Du in der Metadaten-Planungsfunktion ausgewählt hast.

Klicke hier, um zu sehen, wie Du Daten für zukünftige Aktionen importierst.

Details, wie das Ändern von Beiträgen 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.

Protokolle für alle Deine Beitragsänderungen

Mit PublishPress Future Pro kannst Du alle Beitrags-Updates detailliert protokollieren. PublishPress Future zeichnet mehrere wichtige Datenpunkte für alle Aktionen auf:

  • Der Post, für den die Aktion ausgeführt wurde.
  • Details of the post update.
  • Wann die Änderung am Beitrag vorgenommen wurde.

Klicke hier, um mehr über die Protokollfunktion zu erfahren.

Beziehe PublishPress und erhalten die Pro Plugins

Die Pro-Versionen der PublishPress-Plugins sind ihre Investition wert. Die Pro-Versionen haben zusätzliche Funktionen und schnelleren Support. Klicke hier, um PublishPress beizutreten.

Schließe Dich PublishPress an und erhalte Zugriff auf diese neun Pro-Plugins:

Zusammen bilden diese Plugins eine Sammlung leistungsstarker Publishing-Tools für WordPress. Wenn Du einen professionellen Workflow in WordPress erstellen musst, mit Moderation, Revisionen, Berechtigungen und mehr … dann solltest Du PublishPress ausprobieren.

Fehlerberichte

Über Fehlerberichte für PublishPress Future freuen wir uns in unserem Repository auf GitHub. Bitte beachte, dass GitHub kein Support-Forum ist und dass Probleme, die nicht korrekt als Bugs definiert sind, geschlossen werden.

Screenshots

  • Du kannst zukünftige Aktionsdaten in der rechten Seitenleiste auswählen, wenn Du einen Beitrag bearbeitest. Dies funktioniert mit Gutenberg, dem klassischen Editor und den meisten Pagebuilder-Plugins.
  • Du kannst Aktionsdaten mit den Modi „Quick Edit“ und „Massenbearbeitung“ ändern. Auf diese Weise kannst Du schnell automatische Aktionen zu so vielen Beiträgen hinzufügen, wie Du benötigst.
  • Mit PublishPress Future kannst Du Inhalte ändern, entfernen oder vollständig löschen, wenn das geplante Datum erreicht ist.
  • Das PublishPress Future-Plug-in kann Dir E-Mail-Benachrichtigungen senden, wenn automatische Aktionen für Deine Inhalte ausgeführt werden.
  • Mit PublishPress Future kannst Du Aktionsdaten für Beiträge, Seiten, WooCommerce-Produkte, LearnDash-Klassen oder andere benutzerdefinierte Beitragstypen auswählen.
  • Mit PublishPress Future kannst Du das geplante Datum automatisch in Deinen Artikeln anzeigen. Das Aktionsdatum wird am Ende Deines Beitrags hinzugefügt. Du kannst auch Shortcodes verwenden, um das Aktionsdatum anzuzeigen und die Ausgabe anzupassen.
  • Das PublishPress Future-Plug-in erstellt ein Protokoll aller geänderten Beiträge. Auf diese Weise kannst Du alle automatischen Aktionen für Deine Posts detailliert protokollieren.
  • PublishPress Future Pro unterstützt benutzerdefinierte Status, wie sie von WooCommerce bereitgestellt werden. Das bedeutet, dass Pro-Benutzer ihre Inhalte so einstellen können, dass sie in jeden beliebigen Status in WordPress geändert werden.

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

FAQ

Kann ich Änderungen an WooCommerce-Produkten planen?

Ja, mit dem PublishPress Future-Plug-in kannst Du automatische Änderungen an Beiträgen, Seiten und anderen Inhaltstypen, einschließlich WooCommerce-Produkten, planen. Um diese Funktion zu aktivieren, gehe zu Future > Post-Typen. Setze im Bereich „Produkt“ ein Häkchen bei „Aktiv“.

Klick für weitere Details zu WooCommerce Änderungen

Kann ich Änderungen an Elementor-Beiträgen planen?

Ja, mit dem PublishPress Future-Plug-in kannst Du automatische Änderungen an Beiträgen, Seiten und anderen Inhaltstypen, einschließlich WooCommerce-Produkten, planen. Um diese Funktion zu aktivieren, gehe zu Future > Post-Typen. Aktiviere das Kontrollkästchen „Aktiv“ für den Beitragstyp, den Du mit Elementor verwendest.

Klick für weitere Details zu Elementor-Beiträge Änderungen

Rezensionen

11. April 2024 1 Antwort
I love future so much, I am thankful everyday that it exists. That said, I wish that it is possible to have Publishpress Future automatically add a „noindex“ meta tag to a page at a certain date.Francis
31. März 2024 1 Antwort
Plugin is getting better. It also takes care the auto drafted posts, which is great. The only small criticism would be that I don’t need to be notified of the deletion of auto drafts. Thanks!!
29. Februar 2024 1 Antwort
Works very good for me ! In addition, the support is very responsive even for free users. I had once trouble to display posts and pages lists in backend but it was my mistake as I used a delay time written in French where it is documented to use only English (Always properly read the friendly doc).
15. Februar 2024 1 Antwort
Perfecto. Cumple con su función, es facil de configurar. Gracias por el aporte!!
Alle 156 Rezensionen lesen

Mitwirkende & Entwickler

„Schedule Post Changes: Unpublish, Delete, Change Status, Trash, Change Categories and Tags with PublishPress Future“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

„Schedule Post Changes: Unpublish, Delete, Change Status, Trash, Change Categories and Tags with PublishPress Future“ wurde in 19 Sprachen übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „Schedule Post Changes: Unpublish, Delete, Change Status, Trash, Change Categories and Tags with PublishPress Future“ in deine Sprache.

Interessiert an der Entwicklung?

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

Änderungsprotokoll

[3.3.1] – 19 Mar, 2024

  • ADDED: Add validation for the date and time offset in the settings page, #683;
  • ADDED: Add form validation to the settings panel;
  • ADDED: Add form validation to the metabox panel;
  • ADDED: Add a date preview to the date/time offset setting field;
  • CHANGED: The actions to move posts to another status where grouped in a single action, with a dropdown to select the status, #668;
  • CHANGED: The actions „draft“, „private“ and „trash“ are deprecated in favor of „change-status“, #668;
  • CHANGED: The metadata hash key has now a prefix „_“ marking it as a private key, #695;
  • CHANGED: Improved the name of some actions;
  • CHANGED: Change the label of the field to select terms when „Replace all terms“ is selected, #664;
  • FIXED: Make it impossible to choose dates in the past, #443;
  • FIXED: Enter key submits quick-edit panel when selecting a taxonomy term, #586;
  • FIXED: The name of the taxonomy in the actions field is now updated in the settings panel when the taxonomy is changed, #676;
  • FIXED: Possible to add an action using an empty category setting, #587;
  • FIXED: Fix language files for ES, IT, FR, #685;
  • FIXED: Fix inconsistent text in the filter for „Pending“ actions, #673;
  • FIXED: Improve the message when no actions are found: „No Future Actions“, #666;

[3.3.0] – 28 Fev, 2024

  • ADDED: Add new filter for filtering the list of post types supported by the plugin: publishpressfuture_supported_post_types, #677;
  • ADDED: Add new filter for choosing to hide or not the Future Action in the post editors: publishpressfuture_hide_metabox, #69;
  • ADDED: Add new filter for filtering the post metakeys in the post model: publishpressfuture_action_meta_key, #69;
  • ADDED: Add new method medataExists to the PublishPress\Future\Framework\WordPress\Models\PostModel class;
  • ADDED: Add support to a hash in the the post meta pp_future_metadata_hash, to identify if the future action’s post meta has changed or was scheduled by metadata (fully availale only on PRO);
  • CHANGED: Deprecated the filter postexpirator_unset_post_types in favor of the new filter publishpressfuture_supported_post_types, allowing not only remove, but add new post types to the list of supported post types, #677;
  • CHANGED: The list of post types in the settings page now also shows the non-public post types that are not built in on WordPress, #677;
  • CHANGED: Remove the X and Facebook icons from the footer in the admin pages, #667;
  • CHANGED: Updated the URLs on the plugin’s footer, #667;
  • CHANGED: Minor change in the description of the setting that controls the activation/deactivation future action for the post type;
  • CHANGED: The metadata _expiration-date-status now can be specified as 1 or '1' and not only 'saved', #69;
  • CHANGED: The action publishpress_future/run_workflow is now depreacated in favor of publishpressfuture_run_workflow;
  • FIXED: Fix language files for ES, IT, FR, #665;
  • FIXED: Fix error when a term does not exists, #675;
  • FIXED: Add new interface for NoticeFacade: NoticeInterface;
  • REMOVED: Remove the legacy action postExpiratorExpire. This action will not trigger the future actions anymore;
  • REMOVED: Remove the legacy action publishpressfuture_expire. This action will not trigger the future actions anymore;

[3.2.0] – 25 Jan, 2024

  • ADDED: Add the possibility to use non hierarchical taxonomies, #285;
  • ADDED: Add new future action to remove all taxonomy terms of a post, #652;
  • ADDED: Add new action hook publishpressfuture_saved_all_post_types_settings to allow developers to trigger an action when the Post Types settings are saved;
  • CHANGED: Deprecate the constant PublishPress\Future\Modules\Settings\SettingsFacade::DEFAULT_CUSTOM_DATE and replaced it with ::DEFAULT_CUSTOM_DATE_OFFSET;
  • CHANGED: Moved the date and time format settings fields to the Display tab, #605;
  • CHANGED: Added description to the taxonomy setting field in the Post Types tab, #641;
  • CHANGED: Moved the Post Types settings tab to the first position, #619;
  • CHANGED: Simplify the name of actions on taxonomy related actions, adding the actual name of the taxonomy, #294;
  • CHANGED: Change the text on the Status column in the Future Actions list, from „Pending“ to „Scheduled“, #661;
  • CHANGED: Fixed typos and improved the text in the Post Types settings tab, #659;
  • CHANGED: The list of supported post types in the settings page only shows public post types, and non-public that are built-in and show the UI;
  • FIXED: Fix consistency on radio buttons alignment on the settings page;
  • FIXED: Hides the legacy cron event field from Diagnostics and Tools settings tab if no legacy cron event is found;
  • FIXED: Fix the „Change Status to Trash action“ on custom post types, #655;
  • FIXED: Added back support for reusable blocks, #200;
  • FIXED: Updated the language files, #653;
  • FIXED: Fix error 404 when activating future action on a post type that has no taxonomy registered, #662;

[3.1.7] – 04 Jan, 2024

  • FIXED: Fix compatibility with plugins like „Hide Categories and Products for Woocommerce“, making sure terms are not hidden in the taxonomy field, #639;
  • FIXED: Fix the terms select field in the settings page, expanding it on focus, #638;
  • FIXED: Fix the fatal error when hook add_meta_boxes didn’t receive a WP_Post instance as parameter, #640;
  • FIXED: Fix issue with the „NaN“ categories in the classic editor, #647;
  • FIXED: Fix issue with accents on the taxonomy field in the settings, #642;

[3.1.6] – 20 Dec, 2023

  • ADDED: Add a new setting to select the time format in the date picker component, #626;
  • CHANGED: Stick the library woocommerce/action-scheduler on version 3.7.0, so we don’t force WP min to 6.2;
  • CHANGED: Min WP version is now 6.1, #627;
  • CHANGED: The field to select terms now expands when the user focus on it, not requiring to type a search text, #633;
  • CHANGED: Increase the limit of items displayed i nthe the field to select terms. It shows up to 1000 items now, #633;
  • FIXED: Fix support for WP between 6.1 and 6.4, #625;
  • FIXED: Fix the search of posts in the posts lists, #620;
  • FIXED: Fix classic meta box when using Classic Editor plugin with the classic editor as default, #624;
  • FIXED: Fix default date for new posts, #623;
  • FIXED: Fix the quick edit form and future action column for pages, #618;
  • FIXED: Fix support to custom taxonomies that are not showed in the Rest API, #629;

[3.1.5] – 14 Dec, 2023

  • FIXED: Fix array_map(): Argument must be of type array, string given, #606;
  • FIXED: Remove broken and invalid setting to use classic metabox, #604;
  • FIXED: Prevent a PHP warning in the posts screen if the selected term do not exists anymore, #612;
  • FIXED: Update the ES, IT and FR translations, #609;

[3.1.4] – 13 Dec, 2023

  • ADDED: Taxonomy term field now supports adding a new term by typing a new value;
  • ADDED: Add a button to toggle the calendar on the future action panels. Quick/Bulk edit are collapsed by default, #583;
  • ADDED: Display the taxonomy name in the future action panels instead of showing „Taxonomy“, #584;
  • CHANGED: Refactor all the future action panels to use the same React components, fixing the inconsistency between the panels, #572;
  • CHANGED: Removed external dependency of the React Select library, using now the WordPress internal library;
  • CHANGED: In the Action field on Post Type settings, the taxonomy related actions are only displayed if the post type has any term registered;
  • CHANGED: Change the order of fields in the future action panels, moving action and taxonomy at the beginning
  • CHANGED: The method ExpirationScheduler::schedule now automatically converts the date to UTC before scheduling the action;
  • CHANGED: The action publishpressfuture_schedule_expiration now receives the date in the local site timezone;
  • CHANGED: Update the library woocommerce/action-scheduler from 3.6.4 to 3.7.0;
  • CHANGED: Future action data stored in the args column on the table _ppfuture_action_args is now camelCase;
  • CHANGED: Change the Database Schema check to verify and display multiple errors at once. The Fix Database should fix them all;
  • DEPRECATED: Deprecate the calss Walker_PostExpirator_Category_Checklist;
  • DEPRECATED: Deprecate the function postexpirator_get_post_types, moving the logic to the model PostTypesModel;
  • FIXED: Fix fatal error when clicking on „Post Types“ tab in the settings when using PT-Br language, #567;
  • FIXED: Stop hardcoding the DB engine when creating the table for action arguments, #565 [Thanks to @dave-p];
  • FIXED: Simple quotes were not being removed from the future action date offset setting, #566;
  • FIXED: Update Spanish, Franch and Italian translations, #551;
  • FIXED: Improved data sanitization on the plugin, #571;
  • FIXED: Fix consistency on data saved on post meta from different editors, quick-edit and bulk-edit. Specially related to the post meta „_expiration-date-options“, #573;
  • FIXED: Strange years value in the date selection, #568;
  • FIXED: Fix the action „Remove selected term“ for authors role, #550;
  • FIXED: Fix the post type settings page not loading the saved settings after a page refresh triggered by the save button, #576;
  • FIXED: Fix PHP warning: Creation of dynamic property $hooks in NoticeFacade.php, #580;
  • FIXED: Fix call to undefined function …Expirator\Adapters\as_has_scheduled_action, #574
  • FIXED: Fix PHP warning: Class …Expirator\Models\DefaultDataModel not found in …legacy/deprecated.php, #582;
  • FIXED: Update the X/Twitter icon on the footer of admin pages, #583;
  • FIXED: Fix the use of custom taxonomies on the future action panels, #585;
  • FIXED: Fix call to the method `manageUpgrade on …Core\Plugin;
  • FIXED: Fix action for deleting posts without sending to trash, #593;
  • FIXED: Fix action that sends a port to trash, to trigger the expected actions, #597;
  • FIXED: Fix empty cells on Actions table when Pro plugin is uninstalled and Free is activated, #595;
  • REMOVED: Internal function postexpirator_add_footer was removed, and the footer is now handled in the ContentController class;
  • REMOVED: Internal function postexpirator_get_footer_text was removed;

[3.1.3] – 09 Nov, 2023

  • FIXED: Fix JS error Cannot read properties of undefined (reading ‘length’) on the block editor, #561;

[3.1.2] – 07 Nov, 2023

  • CHANGED: Update the library woocommerce/action-scheduler from 3.6.3 to 3.6.4;
  • FIXED: Fix compatibility with WP 6.4 removing dependency of lodash, #555;

[3.1.1] – 11 Oct, 2023

  • ADDED: Add new bulk action for posts to update future action scheduler based on post’s metadata, #538;
  • DEPRECATED: Deprecate class PublishPress\Future\Core\DI\ContainerNotInitializedException;
  • DEPRECATED: Deprecate class PublishPress\Future\Core\DI\ServiceProvider;
  • DEPRECATED: Deprecate interface PublishPress\Future\Core\DI\ServiceProviderInterface;
  • FIXED: Fix compatibility with 3rd party plugins that import posts, #538;
  • FIXED: Fix JS error when admin user has no permissions, #533 (Thanks to @raphaelheying);
  • FIXED: Fix missed post link on the email notification, or actions log, when the post is deleted, #507;
  • FIXED: Fix plugin activation hook not running on plugin activation, #539;
  • REMOVED: Remove tooltip from the „Expires“ column in the posts list, #511;

[3.1.0] – 06 Sep, 2023

  • FIXED: Fix compatibility with Composer-based installations, using prefixed libraries, #522;
  • FIXED: Fix notice about using FILTER_SANITIZE_STRING on PHP 8, #525;
  • CHANGED: Remove the file define-base-path.php. The constant PUBLISHPRESS_FUTURE_BASE_PATH is deprecated and is now defined in the main plugin file;
  • CHANGED: Internal dependencies moved from vendor to lib/vendor, #522;
  • CHANGED: Replaced Pimple library with a prefixed version of the library to avoid conflicts with other plugins, #522;
  • CHANGED: Replaced Psr/Container library with a prefixed version of the library to avoid conflicts with other plugins, #522;
  • CHANGED: Change min PHP version to 7.2.5. If not compatible, the plugin will not execute;
  • CHANGED: Change min WP version to 5.5. If not compatible, the plugin will not execute;
  • CHANGED: Updated internal libraries to the latest versions;
  • CHANGED: Changed the priority of the hook plugins_loaded on the main plugin file from 10 to 5, #522;
  • CHANGED: Removed the vendor-locator-future library. Internal vendor is now on a fixed path, lib/vendor, #522;
  • CHANGED: Deprecated constant PUBLISHPRESS_FUTURE_VENDOR_PATH in favor of PUBLISHPRESS_FUTURE_LIB_VENDOR_PATH;
  • CHANGED: Update Action Scheduler library to 3.6.2;
  • CHANGED: Update the .pot and .mo files;

[3.0.6] – 26 Jul, 2023

  • FIXED: Fix JavaScript error on the block editor: Uncaught TypeError: Cannot read properties of undefined (reading ‚indexOf‘), #517;
  • FIXED: Fix fatal error on content with shortcode: Call to undefined method …ExpirablePostModel::getExpiratigetExpirationDateAsUnixTimeonDate(), #516;

[3.0.5] – 25 Jul, 2023

  • ADDED: Add a setting field to control the style of the Future Action column on posts lists (Advanced tab), #482;
  • FIXED: Fix the message that prevented to select terms for a future action, #488;
  • FIXED: Fix the taxonomy field in the Post Types settings page, that was not visible unless you select a taxonomy related default action, #496;
  • FIXED: Fix the space after the „reset“ button on the calendar field, in the block editor, #465;
  • FIXED: Fix error displayed when trying to deactivate the plugin with „Preserve data after deactivating the plugin“ as „Delete data“, #499;
  • FIXED: Fix DB error when trying to create the action args table, due to DESCRIBE query on a table that do not exists yet, #450;
  • FIXED: Fix default expiration date time for post type on different timezones;
  • FIXED: Fix date and time on block editor with different timezones, #498;
  • FIXED: Fix missed title and post type info in emails or logs when the post is deleted, #507;
  • FIXED: Notice: Undefined variable: gmt_schedule_display_string, in the columns in the Future Action screens, #504;
  • FIXED: Update ES, FR, and IT translations, #509;
  • CHANGED: Improve the label for the terms field in the block editor panel, #483;
  • CHANGED: Merge the settings tabs „Diagnostics“ and „Tools“, #501;
  • CHANGED: Update the .pot file;
  • CHANGED: Renamed the settings tab „Defaults“ to „General“;
  • CHANGED: Added some instructions comments to translators;
  • CHANGED: The default date interval for global and post type settings now only accepts EN format, $495;
  • CHANGED: Add log message when date time offset is invalid when trying to schedule a future action;
  • CHANGED: Change the date format on „Scheduled Date“ column in the Future Actions list to use the site timezone and not GMT date. GMT date is now displayed on the tooltip;
  • CHANGED: Changed text and buttons labels on Diagnostics and Tools settings tab, #506;
  • CHANGED: Add method getExpirationDateAsUnixTime to the ExpirablePostModel class;
  • CHANGED: Changed method getTitle on ExpirablePostModel to return title from args if post is not found anymore;
  • CHANGED: Changed method getPostType on ExpirablePostModel to return post type from args if post is not found anymore;
  • DEPRECATED: The methods getDefaultDate and getDefaultDateCustom on SettingsFacade class are deprecated;

[3.0.4] – 04 Jul, 2023

  • FIXED: Fix „Save changes“ notification on block editor when post is not edited, #449;
  • FIXED: Fix unchecked category on classic editor when editing a post with future action enabled, #481;
  • FIXED: Update French translation, #473;
  • FIXED: Fix the plugin initialization to properly load the plugin text domain, and CLI commands;
  • FIXED: Fix the start of the week on the calendar, honoring the site setting, #484;
  • FIXED: Fix the taxonomy field for custom post types;
  • FIXED: Fix consistency in the message in the block editor, compared to classic editor, when no taxonomy is selected;
  • FIXED: Update the .pot file;
  • CHANGED: The name of the block editor component changed from postexpirator-sidebar to publishpress-future-action, #449;
  • CHANGED: Update the Action Scheduler library from 3.6.0 to 3.6.1;
  • REMOVED: Remove internal function postexpirator_init;

[3.0.3] – 20 Jun, 2023

  • FIXED: Error on the block editor: The „postexpirator-sidebar“ plugin has encountered an error and cannot be rendered, #475;
  • FIXED: Error message in the future action column: Action scheduled but its definition is not available anymore, #474;
  • CHANGED: Update message when future action data is corrupted for the post;

[3.0.2] – 19 Jun, 2023

  • FIXED: Fix warning displayed in the classic editor if a taxonomy is not properly selected, #453;
  • FIXED: Fix typo in a message when a taxonomy is not properly selected;
  • FIXED: Fix a blank post type label in the Arguments column in the Actions Log list when a post type is not registered anymore;
  • FIXED: FIx error message in the Future Action column if the action is not found anymore, #454;
  • FIXED: Fix default date/time offset, #455;
  • FIXED: Fix label „Action“ on a few screens, #458;
  • FIXED: Fix broken screen due by a long select field in Classic Editor, #458;
  • FIXED: Fix Future action ordering not working on „Posts“ screen, #462;
  • FIXED: Update .pot file and some translation strings;

[3.0.1] – 15 Jun, 2023

  • ADDED: Add diagnostic check for DB schema in the Settings page;
  • CHANGED: Changed privacy for method PublishPress\Future\Framework\WordPress\Models\PostModel::getPostInstance from private to protected;
  • FIXED: Restore future action data on post meta fields, #452;
  • FIXED: Fix PHP warning about undefined index ‚categoryTaxonomy‘;
  • FIXED: Fix auto-enabled future action on new posts, #447;
  • FIXED: Fix default future action type on custom post types;
  • FIXED: First letter of future actions log is not capitalized on some messages in the popup view;
  • FIXED: Fix log message when actions related to taxonomy terms run;

[3.0.0] – 13 Jun, 2023

  • ADDED: Add Dutch translation files, #429;
  • CHANGED: Namespace has been changed from PublishPressFuture to PublishPress\Future;
  • CHANGED: Functions, autoload, class aliases and class loading have been moved into a hook for the action plugins_loaded with priority 10;
  • CHANGED: Post expiration queue migrated from WP Cron to Action Scheduler library from WooCommerce, #149;
  • CHANGED: Deprecate hook „publishpressfuture_expire“ in favor of „publishpress_future/run_workflow“. New hook has two arguments: postId and action, #149;
  • CHANGED: Changed the label „Type“ to „Action“ in the bulk edit field;
  • CHANGED: Change the capability checked before authorizing API usage. Changed from edit_posts to publishpress_future_expire_post;
  • CHANGED: Added the old post status in the log message when the post expires changing status;
  • CHANGED: Change the text of options in the bulk edit field, for more clearance;
  • CHANGED: Change text of Post Types settings tab;
  • CHANGED: FIXED: Replace „Expiry“ with „Actions“, #392;
  • FIXED: Fix PHP warning about undefined index ‚terms‘, #412;
  • FIXED: Fix error on block editor: can’t read „length“ of undefined;
  • FIXED: Fix escaping on a few admin text;
  • FIXED: Fix text and positions of expiration fields in the bulk edit form;
  • FIXED: Fix email notifications, #414;
  • FIXED: Fix PHP Fatal error: Uncaught TypeError: gmdate(): Argument #2 ($timestamp) must be of type ?int, #413;
  • FIXED: All the expirations scheduled to the future run if we call „wp cron events run –all“, #340;
  • FIXED: Deactivation of the plugin does not remove the cron jobs and settings, #107;
  • FIXED: Can we make the cron schedule more human-readable, #231;
  • FIXED: Expiration actions related to taxonomy are not working if default way to expire is not taxonomy related, #409;
  • FIXED: Database error on a new site install, #424;
  • FIXED: Bulk Edit Text doesn’t match Quick Edit, #422;
  • FIXED: Expiration Email Notification is not working, #414;
  • FIXED: Capital case for statuses, #430;
  • FIXED: Make sure all files has protection against direct access, #436;
  • FIXED: Fix fatal error sending expiration email, #434, #433;

[2.9.2] – 28 Feb, 2023

  • FIXED: List of actions in the post type settings is not filtered by post types, #400;
  • FIXED: Include Statuses as a Default option, #395;
  • FIXED: Remove legacy screenshots from the plugin root dir;
  • FIXED: Fix i18n issues, #401;

[2.9.1] – 23 Feb, 2023

  • FIXED: Fix location of wordpress-banners style CSS when started by the Pro plugin, #393;

[2.9.0] – 23 Feb, 2023

  • ADDED: Add new filter for filtering the expiration actions list: publishpressfuture_expiration_actions;
  • ADDED: Add new constant PUBLISHPRESS_FUTURE_BASE_PATH to define the base path of the plugin;
  • ADDED: Added hooks to extend settings screen;
  • ADDED: Added ads and banners for the Pro plugin;
  • CHANGED: Refactored the UI for the Post Types settings screen closing the fields if not activated, #335, #378;
  • CHANGED: Refactored the services container to be used by the Pro plugin;
  • CHANGED: Changed the order of some settings field in the Post Types settings screen;
  • FIXED: Fix hook transition_post_status running twice, #337;
  • FIXED: Fix bug with choosing a taxonomy change as a default, #335;
  • FIXED: Updated FR and IT translations, #336 (thanks to @wocmultimedia);
  • FIXED: HTML escaping for a field on the settings screen;
  • FIXED: Fix the expiration date column date format;
  • FIXED: Fix option to clear data on uninstall, removing the debug table;
  • FIXED: Combining Multiple Cron Events #149;

[2.8.3] – 10 Jan, 2023

  • ADDED: Add new filters for allowing customizing the expiration metabox and the email sent when post is expired, #327 (thanks to Menno);
  • CHANGED: Changed pattern of expiration debug log messages to describe the action in a clearer way and add more details;
  • CHANGED: Changed the label and description of the setting field for default date and time expiration offset, #310;
  • FIXED: Remove debug statement, #326;
  • FIXED: Fix text for default date/time expiration setting description;
  • FIXED: Fix PHP 8 error and remove extract functions, #328;
  • FIXED: Simplify setting to set default expiration date/time interval, removing invalid „none“ option, #325;
  • FIXED: Simplify unscheduling removing duplicated code, #329;
  • FIXED: Fix PHP warning and fatal error when post’s expiration categories list is not an array, #330;

[2.8.2] – 20 Dec, 2022

  • FIXED: Fix taxonomy expiration, #309;
  • FIXED: Fix TypeError in ExpirablePostModel.php: array_unique(): Argument #1 ($array) must be of type array, #318;

[2.8.1] – 08 Dec, 2022

  • FIXED: Fix PHP warning: attempt to read property „ID“ on null in the „the_content“ filter, #313;
  • FIXED: Fix PHP warning: undefined array key „properties“ in class-wp-rest-meta-fields.php, #311;
  • FIXED: Update language files to ES, FR and IT (thanks to @wocmultimedia), #308;

[2.8.0] – 08 Nov, 2022

  • ADDED: Add translations for ES, FR, IT languages, #297;
  • 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;
  • 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;
  • FIXED: Fix the expire date column in WooCommerce products list, #276;
  • 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;

[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 …