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
I am experiencing a compatibility issue between the Ultimate Member plugin and the WP-Stateless plugin on my WordPress site.
Issue:
When WP-Stateless is activated in Stateless Mode, users cannot upload a profile photo using the Ultimate Member profile editor. The upload dialog appears, but the "Apply" button remains inactive, preventing the photo from being saved. When I deactivate WP-Stateless, the upload works without issues.
Environment Details:
WordPress Version: 6.7.1
Ultimate Member Version: 2.9.1
WP-Stateless Version: 4.1.2
WP-Stateless Mode: Stateless
Hosting: Google Cloud
Troubleshooting Done:
I confirmed the issue is resolved when WP-Stateless is deactivated.
I did not test other WP-Stateless modes (e.g., CDN, Backup) because I am concerned about potential performance decreases. However, I can test these if necessary.
Could you please assist me with resolving this issue? I would like to maintain performance and the benefits of Stateless Mode while ensuring Ultimate Member’s functionality works as expected.
Dear Support Team,
I am experiencing a compatibility issue between the Ultimate Member plugin and the WP-Stateless plugin on my WordPress site.
Issue:
When WP-Stateless is activated in Stateless Mode, users cannot upload a profile photo using the Ultimate Member profile editor. The upload dialog appears, but the "Apply" button remains inactive, preventing the photo from being saved. When I deactivate WP-Stateless, the upload works without issues.
Environment Details:
Troubleshooting Done:
Could you please assist me with resolving this issue? I would like to maintain performance and the benefits of Stateless Mode while ensuring Ultimate Member’s functionality works as expected.
Looking forward to your guidance.
Best regards,
Ibrahem Elzalabany
https://medelevus.com
The text was updated successfully, but these errors were encountered: