The 'PHP memory limit' requirement is displayed twice, because panopoly_core_requirements() adds it as a separate requirement instead of overwriting $requirements['php_memory_limit'].

CommentFileSizeAuthor
#5 1988596-php-memory-limit-5.patch1.69 KBpopulist
#1 PHP_memory_limit.png33.07 KBpancho
#1 panopoly_core-PHP_memory_limit-1988596-1.patch1.4 KBpancho

Comments

pancho’s picture

pancho
Location UTC+2 🇪🇺 EU
commented
StatusFileSize
new panopoly_core-PHP_memory_limit-1988596-1.patch1.4 KB
new PHP_memory_limit.png33.07 KB

Screenshot and patch.

pancho’s picture

pancho
Location UTC+2 🇪🇺 EU
commented
Status: Active » Needs review
populist’s picture

populist commented

I believe this was changed as a result of #1953428: Panopoly Core + Hook Requirements, but perhaps that was in error.

pancho’s picture

pancho
Location UTC+2 🇪🇺 EU
commented
Assigned: Unassigned » pancho

Hmm, I remember it worked when I wrote this patch which in fact just reverts #1953428: Panopoly Core + Hook Requirements.
I'm gonna check this tomorrow or so.

populist’s picture

populist commented
StatusFileSize
new 1988596-php-memory-limit-5.patch1.69 KB

Here is a patch that sets the PHP memory limit on a global basis. It needs to work around the Array problem seen #1953428: Panopoly Core + Hook Requirements, but I think does so just fine. This will need a bit more testing around install, but here it is for others to check out. The trick was not redefining the $requirements['php_memory_limit'] array since module_invoke() will aggregate the data making it unreadable by system_status().

lsolesen’s picture

lsolesen commented
Issue summary: View changes
Status: Needs review » Reviewed & tested by the community

The patch in #5 successfully removes the extra memory requirement.

mrfelton’s picture

mrfelton commented
Status: Reviewed & tested by the community » Needs work

With this patch applied I don't see the PHP memory requirement status entry at all.