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
Describe the bug
When an existing user checks out to renew a level or checks out for a new level the value for the custom user field previously entered is not set as the field value and if the user completes checkout without entering these values again their previous values entered are removed. This results in losing the custom user field metadata previously stored for that user.
To Reproduce
Steps to reproduce the behavior:
For a user that has a membership level that is due for renewal go to the user's account page and click on the "Renew" link
On the checkout page inspect the custom user field that is created in pods and note that the field value is now empty instead of filled with the value stored in the usermeta table.
Complete checkout without entering a new value.
Check user meta table for the relevant user id and meta keys and note that the meta value for these are now empty
Expected behavior
If a custom user field has a value that value should populate the related custom user field at checkout.
Isolating the problem (mark completed items with an [x]):
I have deactivated other plugins and confirmed this bug occurs when only Paid Memberships Pro plugin is active.
This bug happens with a default WordPress theme active, or Memberlite.
I can reproduce this bug consistently using the steps above.
pods-server-software: nginx/1.16.0
pods-user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0
pods-session-save-path: undefined
pods-session-save-path-exists: No
pods-session-save-path-writable: No
pods-session-max-lifetime: 1440
pods-opcode-cache-apc: No
pods-opcode-cache-memcached: No
pods-opcode-cache-opcache: Yes
pods-opcode-cache-redis: No
pods-object-cache-apc: No
pods-object-cache-apcu: No
pods-object-cache-memcache: No
pods-object-cache-memcached: No
pods-object-cache-redis: No
pods-memory-current-usage: 10.639M / 40M
pods-memory-current-usage-real: 12.000M
pods-network-wide: No
pods-install-location: path-to/wp-content/plugins/pods/
pods-developer: No
pods-tableless-mode: No
pods-relationship-table-enabled: Yes
pods-relationship-table-status: 0
pods-light-mode: No
pods-strict: No
pods-allow-deprecated: Yes
pods-api-cache: Yes
pods-shortcode-allow-evaluate-tags: No
pods-sessions: Disable sessions
pods-can-use-sessions: No
pods-settings-types_only: No
pods-settings-watch_changed_fields: No
pods-settings-metadata_integration: Yes
pods-settings-metadata_override_get: No
The text was updated successfully, but these errors were encountered:
Describe the bug
When an existing user checks out to renew a level or checks out for a new level the value for the custom user field previously entered is not set as the field value and if the user completes checkout without entering these values again their previous values entered are removed. This results in losing the custom user field metadata previously stored for that user.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If a custom user field has a value that value should populate the related custom user field at checkout.
Isolating the problem (mark completed items with an [x]):
WordPress Environment
version: 6.2.2
site_language: en_US
user_language: en_US
timezone: +00:00
permalink: /%postname%/
https_status: true
multisite: false
user_registration: 1
blog_public: 1
default_comment_status: open
environment_type: local
user_count: 81
dotorg_communication: true
[ wp-active-theme ]
name: Memberlite (memberlite)
version: 4.5.4.1
author: Stranger Studios
author_website: https://www.strangerstudios.com
parent_theme: none
theme_features: core-block-patterns, widgets-block-editor, menus, automatic-feed-links, title-tag, custom-logo, post-thumbnails, wp-block-styles, align-wide, responsive-embeds, html5, post-formats, custom-background, editor-color-palette, customize-selective-refresh-widgets, custom-header, infinite-scroll, widgets
theme_path: path-to/wp-content/themes/memberlite
auto_update: Disabled
[ wp-plugins-active ]
Paid Memberships Pro: version: 2.11.2, author: Paid Memberships Pro, Auto-updates disabled
Paid Memberships Pro - Pods Add On: version: 1.0.2, author: Paid Memberships Pro, Auto-updates disabled
Pods - Custom Content Types and Fields: version: 2.9.16, author: Pods Framework Team, Auto-updates disabled
[ wp-server ]
server_architecture: Windows NT 10.0 AMD64
httpd_software: nginx/1.16.0
php_version: 8.1.9 64bit
php_sapi: cgi-fcgi
max_input_variables: 4000
time_limit: 1200
memory_limit: 256M
max_input_time: 600
upload_max_filesize: 300M
php_post_max_size: 1000M
curl_version: 7.77.0 OpenSSL/1.1.1q
suhosin: false
imagick_availability: false
pretty_permalinks: true
htaccess_extra_rules: false
[ wp-database ]
extension: mysqli
server_version: 8.0.16
client_version: mysqlnd 8.1.9
max_allowed_packet: 16777216
max_connections: 151
[ pods ]
pods-server-software: nginx/1.16.0
pods-user-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/115.0
pods-session-save-path: undefined
pods-session-save-path-exists: No
pods-session-save-path-writable: No
pods-session-max-lifetime: 1440
pods-opcode-cache-apc: No
pods-opcode-cache-memcached: No
pods-opcode-cache-opcache: Yes
pods-opcode-cache-redis: No
pods-object-cache-apc: No
pods-object-cache-apcu: No
pods-object-cache-memcache: No
pods-object-cache-memcached: No
pods-object-cache-redis: No
pods-memory-current-usage: 10.639M / 40M
pods-memory-current-usage-real: 12.000M
pods-network-wide: No
pods-install-location: path-to/wp-content/plugins/pods/
pods-developer: No
pods-tableless-mode: No
pods-relationship-table-enabled: Yes
pods-relationship-table-status: 0
pods-light-mode: No
pods-strict: No
pods-allow-deprecated: Yes
pods-api-cache: Yes
pods-shortcode-allow-evaluate-tags: No
pods-sessions: Disable sessions
pods-can-use-sessions: No
pods-settings-types_only: No
pods-settings-watch_changed_fields: No
pods-settings-metadata_integration: Yes
pods-settings-metadata_override_get: No
The text was updated successfully, but these errors were encountered: