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.Here is what we are up to for Panopoly 1.12:
In progress
#2283531: Path alias isn't preserved if the user doesn't have "create url alias" permission
#2283223: Old content aliases should be preserved by default
#2128959: Replace default "update" module behavior with something that makes sense for distributions
#2160731: Panopoly Magic should respect a view's configured view mode
#2063541: Remove Open Sans?
#2209441: Update respondjs to version 1.3
Long standing (and important!) issues that we really, REALLY want to tackle
#2202885: Install fails on BOA/Drush/Aegir - No migration found with machine name PanopolyDemoNode
#2190579: [META] We have no best practices for updating to new Panopoly releases
#2293947: Make "Landing Page" into node + Panelizer (rather than a Page Manager page)
#2183937: Error on install of Panopoly-based install profile: "Column 'module' cannot be null" when profile starts with "e"
Nice to have
#2255095: Add "Crop" tool to Spotlight widget
#2231631: Tests randomly fail with "MySQL server has gone away" (take 4)
#2229297: Update 'media_vimeo' to version 2.0
#1987386: Include Radix theme in Panopoly
#2166865: Removing non-required modules from .info / .make files
#2181079: Update to Navbar 1.8
#1965864: Support CKEditor in Panopoly
#2115519: Undefined index: css in theme_panels_ajax_tab_ajax() (line 219 of panels_ajax_tab/panels_ajax_tab.module
Comments
Comment #1
dsnopekThe 1.9 release turned out to be security update! Switching this to 1.10.
Comment #2
dsnopekPanopoly 1.10 became a security release for https://www.drupal.org/SA-CORE-2014-004
Comment #3
rboedeker CreditAttribution: rboedeker commentedIt would be great to get these two fixes into the distribution:
Comment #4
caschbre CreditAttribution: caschbre commented@rboedeker.... can you create a separate panopoly issue for each of those? And for bonus points a patch. :-)
Comment #5
dsnopekPanopoly 1.11 also become a security release - updating the hitlist to 1.12!
Comment #6
sonicthoughts CreditAttribution: sonicthoughts commentedPlease consider moving #1965864: Support CKEditor in Panopoly to In Progress.
Several reasons:
Comment #7
dsnopekRe-arranged some issues:
Anyway, I think we could release 1.12 when the issues in the first section are fixed, but ideally after issues in the first 2 sections are finished (or, of course, when a security release forces our hand).
Comment #8
dsnopekAlright! All the "in progress" issues are complete - now it's the "long standing and important" issues left.
Comment #9
liza CreditAttribution: liza commentedOHAI PEEPS!
long time no geek :)
just a quick question: do i have to open an issue/request for this or can i keep it here: would it be possible to add to the notes of releases whether they contain Drupal security updates? that would be super helpful.
i'll take a closer look at issue & see where i can help --or if you guys have anything in mind, let me know.
thanks!
Comment #10
dsnopekHi @liza!
We always put a note at the top of the release notes saying whether the release contains a security release or not (see the notes for 1.12 for example). Also, we include it in the title of the announcement on groups.drupal.org/panopoly. For example, here's the announcement from yesterday:
https://groups.drupal.org/node/446403
If there is anything we can do to make it clearer when a security fix is included, please let us know! (Although, that probably makes more sense on another issue, as I'm about to close this one since 1.12 was released).
Thanks!
Comment #11
dsnopekClosing, since we released Panopoly 1.12 yesterday: https://www.drupal.org/node/2357281