We use AdvAgg for managing our CSS delivery and this seems to cause problems to WYSIWYG, namely in calls to the special URL /wyiwyg_theme/[theme name].

The page returns OK or Failed depending on whether or not the theme name is valid, but given the way AdvAgg creates its aggregated files, the code trips up because $elements['#groups'][$child]['group'] is not set. There is no group element in $child.

I guess adding an isset() would prevent the warning, but does the fact of using AdvAgg break what this page is supposed to do in any case? I've not had any end-users report broken functionality or funky page layout anywhere.

Regards,

- Paul

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

paulbeaney created an issue. See original summary.

paulbeaney’s picture

Issue summary: View changes
idefix6’s picture

Thanks for the patch, I applied and tested it.
Warnings are gone now.

joshuautley’s picture

RBTC - worked for us as well. Thank you.

  • TwoD committed c1a42e1 on 7.x-2.x authored by paulbeaney
    - #2858355 by paulbeaney, idefix6, joshuautley: Fixed undefined index:...
TwoD’s picture

Status: Active » Fixed

Thanks for reporting, fixing, testing and verifying this!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.