You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,13 +21,13 @@ Behat requires a Pantheon site. Once you've created the site, you'll need [insta
21
21
22
22
## Workflow
23
23
24
-
Development and releases are structured around two branches, `main` and `release`. The `main` branch is the source and destination for feature branches.
24
+
Development and releases are structured around two branches, `develop` and `main`. The `develop` branch is the source and destination for feature branches.
25
25
26
-
We prefer to squash commits (i.e. avoid merge PRs) from a feature branch into `main` when merging, and to include the PR # in the commit message. PRs to `main` should also include any relevent updates to the changelog in readme.txt. If a feature constitutes a minor or major version bump, that version update should be discussed and made as part of approving and merging the feature into `main`.
26
+
We prefer to squash commits (i.e. avoid merge PRs) from a feature branch into `develop` when merging, and to include the PR # in the commit message. PRs to `develop` should also include any relevent updates to the changelog in readme.txt. If a feature constitutes a minor or major version bump, that version update should be discussed and made as part of approving and merging the feature into `develop`.
27
27
28
-
`main` should be stable and usable, though will be few commits ahead of the public release on wp.org.
28
+
`develop` should be stable and usable, though will be few commits ahead of the public release on wp.org.
29
29
30
-
The `release` branch matches the latest stable release deployed to [wp.org](wp.org).
30
+
The `main` branch matches the latest stable release deployed to [wp.org](https://wordpress.org).
By default the session lifetime is set to 0, which is until the browser is closed.
36
36
37
-
To override this use the `pantheon_session_expiration` filter before the Native PHP Sessions plugin is loaded. For example a small Must-use plugin (a.k.a. mu-plugin) could contain:
37
+
To override this use the `pantheon_session_expiration` filter before the WordPress Native PHP Sessions plugin is loaded. For example a small Must-use plugin (a.k.a. mu-plugin) could contain:
38
38
39
39
<?php
40
40
function my_session_expiration_override() {
@@ -87,9 +87,7 @@ If you see an error like "Fatal error: session_start(): Failed to initialize sto
87
87
To fix, create a new file at `wp-content/mu-plugins/000-loader.php` and include the following:
88
88
89
89
<?php
90
-
if (file_exists(WP_PLUGIN_DIR . '/wp-native-php-sessions/pantheon-sessions.php')) {
This mu-plugin will load WP Native PHP Sessions before all other plugins, while letting you still use the WordPress plugin updater to keep the plugin up-to-date.
95
93
@@ -100,13 +98,6 @@ Adds a WP-CLI command to add an index to the sessions table if one does not exis
100
98
101
99
## Changelog ##
102
100
103
-
### 1.4.4 (September 17, 2025) ###
104
-
* Compatibility: Supports PHP 8.4
105
-
* Increases minimum supported PHP version to 7.4
106
-
* Increases minimum supported WordPress version to 5.3
107
-
* Update plugin name in README files and main plugin file to "Native PHP Sessions" [[#312](https://github.com/pantheon-systems/wp-native-php-sessions/pull/312)]
108
-
* Update Troubleshooting section in README to be more defensive in mu-plugin [[#308](https://github.com/pantheon-systems/wp-native-php-sessions/pull/308)]
109
-
110
101
### 1.4.3 (November 13, 2023) ###
111
102
* Fixed a PHP warning when running the `pantheon session add-index` command on a single site installation. [[#285](https://github.com/pantheon-systems/wp-native-php-sessions/pull/285)]
0 commit comments