Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest => v4.0 #729

Merged
merged 67 commits into from
Mar 28, 2024
Merged

Latest => v4.0 #729

merged 67 commits into from
Mar 28, 2024

Conversation

balexey88
Copy link
Contributor

  • NEW - use custom database tables to store GCS file data. This increases plugin performance and will be used for future improvements.
  • NEW - added filter wp_stateless_get_file, retrieves the GCS file data, should be used instead of getting sm_cloud postmeta directly.
  • NEW - added filter wp_stateless_get_file_sizes, retrieves the GCS file data for image sizes, should be used instead of getting sm_cloud postmeta directly.
  • NEW - added filter wp_stateless_get_file_meta, retrieves all GCS file meta data, should be used instead of getting sm_cloud postmeta directly.
  • NEW - added filter wp_stateless_get_file_meta_value, retrieves the GCS file meta data by meta_key, should be used instead of getting sm_cloud postmeta directly.
  • NEW - added setting allowing to change email for WP-Stateless notifications.
  • NEW - added new Settings tab Addons, which contains the list of WP-Stateless Addons, which replace Compatibilities.
  • NEW - added new Settings tab Status, which contains status and health information related to Google Cloud Storage and WP-Stateless.
  • NEW - CLI command wp stateless migrate to list and operate data optimizations.
  • NEW - configuration constant WP_STATELESS_POSTMETA allows to read the GCS file data from postmeta instead of the new custom database tables.
  • NEW - configuration constant WP_STATELESS_BATCH_HEALTHCHECK_INTERVAL defines an interval in minutes for periodical health checks of a batch background process (like data optimization).
  • COMPATIBILITY - BuddyBoss Compatibility replaced with WP-Stateless – BuddyBoss Platform Addon.
  • COMPATIBILITY - Elementor Compatibility replaced with WP-Stateless – Elementor Website Builder Addon.
  • COMPATIBILITY - Gravity Form Compatibility does not support older version of Gravity Forms (< 2.3).
  • ENHANCEMENT - Allow dismissing notices in Admin Panel only for logged in users.
  • ENHANCEMENT - Updated wp-background-processing library from from 1.0.2 to 1.1.1.
  • ENHANCEMENT - Updated phpseclib 3.0.34 to 3.0.37.
  • FIX - proper use of infinite timeout in set_time_limit function to avoid issues with PHP 8.1 and above #704.

planv and others added 30 commits June 20, 2023 18:09
Remove Compatibilities (moved to external addons).
Addon compatibilities are enabled by default.
Update changlogs and readmes.
Dynamic image support is part of the core.
Google App Engine compatibility is part of the core.
Fix issue with Image upload in Statless mode on Google App Engine.
Fix - prevent dulicating messages in Admin Panel.
Fix - 'View stateless meta' link remove when not in Media Library.
If some posts are deleted from database, this function can be called
with a null post, which is caught and throws an error in php 8.3
Make the argument nullable and check it.
balexey88 and others added 27 commits January 18, 2024 16:42
fix: defensively check for null post in add_fields() for php 8.3
Cleanup build files. Add security scan for PHP
Improve security while processing AJAX requests in Admin Panel
set_time_limit should be set to zero for unlimited
@balexey88 balexey88 requested a review from planv March 28, 2024 20:33
Copy link
Contributor

@planv planv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

@balexey88 balexey88 merged commit c69f356 into v4.0 Mar 28, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants