Opened 19 months ago
Closed 15 months ago
#9207 closed defect (bug) (fixed)
Improve WP Playground compatibility
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 15.0.0 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Build/Test Tools | Keywords: | has-patch |
| Cc: |
Description
I've found various issues:
In BP Nouveau: Activity items action buttons are not styled the right way looks like the bp_current_component() is not set during the Ajax context.
In BP Legacy: a "Deleted" template error notice is always displayed.
this query SELECT object_id FROM wp_bp_xprofile_meta WHERE object_type = 'field' AND meta_key = 'signup_position' ORDER BY CONVERT(meta_value, SIGNED) ASC generates an error : General error: 1 no such column: SIGNED.
It's not possible to upload Avatars (error is Upload Failed! Error was: Please upload only these file types: JPG, JPEG, JPE, GIF, PNG, WEBP.) or cover images (error is Upload Failed! Error was: Specified file failed upload test.).
I need to investigate further.
As WP Playground is putting WordPress in a subdirectory I believe it’s problematic. When testing using wp-now npm package I don’t get most of these errors.
Change History (5)
This ticket was mentioned in PR #389 on buddypress/buddypress by @imath.
15 months ago
#2
- Keywords has-patch added
#3
@
15 months ago
- Milestone changed from Awaiting Contributions to 15.0.0
Let's try to finally use WP Playground to let users preview BuddyPress from the plugin directory!
This will help us prove: BuddyPress is working with any supported WordPress versions. Visiting our Plugin Reviews motivated me about this move.
To fix WP Playground issues, I suggest to:
wp_get_referer()is not set which explains why BP URI globals are not set into Ajax context by WP Playground.$_COOKIE['bp-message']if its value is set todeleted. It looks like the cookie is not deleted but its value is set todeletedonce it's removed by BuddyPress.SIGNEDconversion or casting SQL issue, it looks like it's a SQLlite issue that will be hard to cope with: see https://wordpress.org/support/topic/wordpress-meta-query-not-working/ I used a workaround to get rid of it for now.Trac ticket: https://buddypress.trac.wordpress.org/ticket/9207