Whereas we've already agreed to move to views support for project* in the near future, and,
Whereas webchick has been pulling her hair out for hours dealing with GHOP-related monkey tasks that could be solved quickly via views, and,
Whereas aclight and I already had a working copy of project_issue_views.inc ready to go from http://drupal.org/node/76725
Therefore be it resolved, that views 5.x-1.6 is now installed and enabled on drupal.org.
This issue is only for everyone's information, and so other site admins don't wonder where the hell http://drupal.org/admin/build/views came from. ;)
Cheers,
-Derek
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | views-5.x-1.6-memcache.patch_1.txt | 4.33 KB | dww |
| #1 | views-5.x-1.6-memcache.patch.txt | 4.44 KB | dww |
Comments
Comment #1
dwwCursed memcache patch on d.o. :( Sorry about that, killes. Here's a patch against views 5.x-1.6 that should solve the troubles. I'm going to try it on d.o right now, and check very closely for PHP errors. ;) Stay tuned.
Comment #2
dwwArgh, whoops. Upon closer inspection, the hacked version of core on d.o is expecting the serialized field in the {cache_views} table, and handling the serialize/unserialize stuff, but *not* the changed order of arguments as in D6. Let's try this again...
Comment #3
dwwYay, finally, that seems to have done it. views is enabled now without php errors.
http://drupal.org/issues/tags/GHOP
seems to be working nicely for authenticated users, still no memcached or views errors in the watchdog.
i'm going to call this done, but please reopen if there are other problems...
Comment #4
dwwp.s. I'm leaving views UI disabled until we need to construct other views. Only full site admins have permissions to administer views, anyway, so it's no big deal to enable the UI module if you need it. Seems like we should avoid the cost of the UI module during normal operation of d.o...
Comment #5
(not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.