Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
i get the following error in my dblog whenever i try to edit a page, and the edit page reloads as a whitescreen...
array_unique(): The argument should be an array in /Web/www/WWWRoot/sites/all/modules/boost/boost.module on line 760.
anyone else ever encounter this?
Comment | File | Size | Author |
---|---|---|---|
#5 | boost-673874.patch | 733 bytes | mikeytown2 |
#2 | boost-673874.patch | 838 bytes | mikeytown2 |
Comments
Comment #1
chadd CreditAttribution: chadd commentedi saw that the line 760 was in the parent/children flushing function, so i disabled that and the error went away.
Comment #2
mikeytown2 CreditAttribution: mikeytown2 commentedComment #3
mikeytown2 CreditAttribution: mikeytown2 commentedcommitted
Comment #4
brianmercer CreditAttribution: brianmercer commentedI'm getting
in version 1.18. Is this related?
Comment #5
mikeytown2 CreditAttribution: mikeytown2 commenteddifferent array; related bug.
Comment #6
mikeytown2 CreditAttribution: mikeytown2 commentedcommitted
Comment #8
chadd CreditAttribution: chadd commentederror:
array_unique(): The argument should be an array in /Web/www/WWWRoot/sites/all/modules/boost/boost.module on line 806.
disabled the "Clear all cached pages in a menu on an insert/update/delete operation:" setting and the error stopped being logged in watchdog.
Comment #9
mikeytown2 CreditAttribution: mikeytown2 commented@chadd
Try the latest dev, its fixed in there. I need to release 1.19 soon...
Comment #10
mikeytown2 CreditAttribution: mikeytown2 commentedComment #12
asb CreditAttribution: asb commented> Try the latest dev, its fixed in there. I need to release 1.19 soon...
Please *do* release 6.x-1.19 ;)
Greetings, -asb
Comment #13
mikeytown2 CreditAttribution: mikeytown2 commentedthis is the main release blocker for 1.19 #764494: boost-gzip-cookie-test redirection. Once I get this issue solved, I would feel confidant for a 1.19 release.
Comment #14
sillygwailoComment #16
Anonymous (not verified) CreditAttribution: Anonymous commentedDid you just forget or is there anything else we might be able to help you out with to get this fix released?
Comment #17
mikeytown2 CreditAttribution: mikeytown2 commentedAt work we heavily rely on boost; still working on some issues with it. This week is pretty low key so I hope to be able to push out a new version for the new year. Fixing 3 issues we had with views is helping our sites run a lot smoother.
#1001542: $view->set_display($display_id); returns TRUE for displays that do not exist.
#988680: Memory leak with $view->pre_execute() & $view->attach_displays()
#853864: views_get_default_view() - race conditions and memory usage
Long story short been busy with other things; here's the list for Release Blockers; I'm sure I'm missing one.
http://drupal.org/project/issues/search/boost?issue_tags=1.19%20Release%...
Comment #18
Zoltán Balogh CreditAttribution: Zoltán Balogh commentedsubscribe
Comment #19
loze CreditAttribution: loze commentedsubscribe
Comment #20
GaëlGsubscribe