Posted by chadd on January 4, 2010 at 4:06pm
10 followers
| Project: | Boost |
| Version: | 6.x-1.18 |
| Component: | Caching logic |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
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?
Comments
#1
i saw that the line 760 was in the parent/children flushing function, so i disabled that and the error went away.
#2
#3
committed
#4
I'm getting
array_unique() [<a href='function.array-unique'>function.array-unique</a>]: The argument should be an array in /usr/local/drupal/modules/boost/boost.module on line 806.in version 1.18. Is this related?
#5
different array; related bug.
#6
committed
#7
Automatically closed -- issue fixed for 2 weeks with no activity.
#8
error:
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.
#9
@chadd
Try the latest dev, its fixed in there. I need to release 1.19 soon...
#10
#11
Automatically closed -- issue fixed for 2 weeks with no activity.
#12
> Try the latest dev, its fixed in there. I need to release 1.19 soon...
Please *do* release 6.x-1.19 ;)
Greetings, -asb
#13
this 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.
#14
#15
Automatically closed -- issue fixed for 2 weeks with no activity.
#16
Did you just forget or is there anything else we might be able to help you out with to get this fix released?
#17
At 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%...
#18
subscribe
#19
subscribe
#20
subscribe