Skip to:
Content

bbPress.org

Opened 3 years ago

Closed 3 years ago

#3017 closed defect (fixed)

"Out of memory" error on WP 4.7 on deactivation

Reported by: slaFFik Owned by: johnjamesjacoby
Milestone: 2.5.11 Priority: normal
Severity: major Version: 2.2
Component: API - Roles/Capabilities Keywords:
Cc:

Description

WordPress 4.7-beta2-39148 running Twenty Fifteen theme.

Fatal error: Out of memory (allocated 178257920) (tried to allocate 262144 bytes) in \wp-content\plugins\bbpress\includes\core\capabilities.php on line 463

Change History (6)

#1 @slaFFik
3 years ago

  • Summary changed from Out of memory errror on WP 4.7 when deactivating bbPress to "Out of memory" error on WP 4.7 on deactivation

#2 @johnjamesjacoby
3 years ago

  • Component changed from Tools - Warnings/Notices to API - Roles/Capabilities
  • Milestone changed from Awaiting Review to 2.6
  • Owner set to johnjamesjacoby
  • Version set to 2.2

This should get fixed for both 2.6 and the 2.5 branch.

I've narrowed it down, and will be committing fixes for shortly.

#3 @johnjamesjacoby
3 years ago

In 6118:

Roles: Fix infinite loops from load order changes in WordPress 4.7.

  • Do not translate "role names" which are actually role IDs
  • Add dummy function so literal role names are part of the pomo dictionary
  • Introduce common/locale.php for future localization code
  • Introduce roles variable to main bbPress class, and store loaded roles there
  • Introduce bbp_translate_user_role() to help with outputting literal role names in the proper language

See #3017. For trunk (2.6)

#4 @johnjamesjacoby
3 years ago

In 6120:

Roles: Fix infinite loops from load order changes in WordPress 4.7.

  • Do not translate "role names" which are actually role IDs
  • Add dummy function so literal role names are part of the pomo dictionary
  • Introduce common/locale.php for future localization code
  • Introduce bbp_translate_user_role() to help with outputting literal role names in the proper language

See #3017. 2.5 branch (for 2.5.11)

#5 @johnjamesjacoby
3 years ago

  • Milestone changed from 2.6 to 2.5.11

Thanks again @slaFFik.

This issue should now be resolved.

#6 @johnjamesjacoby
3 years ago

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.