Closed (fixed)
Project:
Panopoly
Version:
7.x-1.18
Component:
Magic
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
28 Feb 2015 at 21:49 UTC
Updated:
1 Apr 2015 at 21:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
candelas commentedI debugged more and the problem is that in Settings, Formatter options, when you select any formatter, and click Continue, any settings chosen in this second screen, in General Settings, are not saved and it keeps the default options.
Comment #2
candelas commentedMaybe this problem is related to Ctools new version. I found this issue #2152413: Ctools / Panels / Panelizer doesn't store field formatter settings of Textformatter Contrib that talks about a bug in Ctools #2152405: ctools_fields_get_field_formatter_settings_form() not fully compatible to field_ui that has being patched and is now in the release 7.x-1.6
Comment #3
candelas commentedI had applied patch in comment #4 in #2424017: Malformed (and useless) string context causes errors with new versions of CTools and I reverted and it had not change. I applied patch in comment #30 in #1259430: Convert entity_field to use #ajax for formatter options and I always got the options for image formatter when I changed from image to any other formatter. I was able to save a different image style, but that was not solving the problem, so I reverted it.
Any tips to solve this problem will be very welcome, thanks
Comment #4
candelas commentedComment #5
candelas commentedHello and sorry: its not caused by Panopoly, but by Panelizer :)
I've just installed Drupal 7.34, CTools 1.6, Panels 3.5 and Panelizer 3.1. Panelizer was giving me problems so I substituted with the one given by Open Atrium that has this patches
- http://drupal.org/files/issues/array-to-object-on-update-1623536-26.patch
- http://www.drupal.org/files/issues/panelizer-search_api-2416505-3.patch
- http://drupal.org/files/1982654-panelizer-dontaskmethatagain-2.patch
There I tested and for content types panelized the formatter settings for images are saved, but for the user no.
So I filled this #2444987: User images formatters settings not saved and change to feature request, so when a patch is created, I will ask to be included in Panopoly.
Again thanks, and have a good day :)
Until then, if another user has this problem, I used a display that is not panelized and only put the image where I can assign a formatter and its settings are saved. Then include as a panel pane in the content of the panelized full view.
Comment #6
candelas commentedHello
I tried Panelizer 7.x-3.2-beta1+17-dev with Drupal 7.34, CTools 1.6, Panels 3.5 and works.
So I tried with Panopoly 7.x-1.18, CTools 1.6, Panels 3.5 and Panelizer 7.x-3.2-beta1+17-dev and don't work.
Because of that I reclassify as a bug.
It looks like a new version 7.x-3.2 of Panelizer will come soon #2155813: Plan for Panelizer 7.x-3.2 release and a beta version is already there https://www.drupal.org/node/2418551
The menu has changed from Config to Structure, so links in Panelizer doesn't work, like
admin/config/content/panelizer/user/user.page_manager/content
should be
admin/structure/panelizer/user/user.page_manager/content
I hope this is useful to someone :)
Comment #7
aschmoe commentedJust did a little testing since I ran into the same issue, and found that virgin installs using latest panels + ctools have no issues with field formatter settings.
I then went down the list disabling likely culprits and found that panopoly_magic is the offending module.
Added the appropriate component label.
Comment #8
aschmoe commentedLooks like the issue stems from:
"Notice: Undefined index: ctools_field_list in ctools_entity_field_content_type_formatter_styles_submit() (line 234 of /modules/contrib/ctools/plugins/content_types/entity_context/entity_field.inc)."
So magic will need to update to deal with the new ctools submit structure.
Comment #9
dsnopekThis sounds like a regression, so I'm marking it as Critical.
Comment #10
dsnopekComment #11
drupa11y commentedJust tried it with this config:
Panopoly 7.x-1.18+11-dev // 7.x-1.x-dev 2015-Mar-07,
CTools 1.6,
Panels 3.5 and
Panelizer 7.x-3.1
Panopoly Magic 7.x-1.18+2-dev
Result: don´t works.
When I try to edit the settings / formatter styles on the profile page I get the following errors:
1. Changing the "Image style":
2. Clicking "Finish":
Therefore I could only "exit" via "Cancel".
Comment #12
drupa11y commentedFrom the "reports/dbllog" I got these ones:
Comment #13
drupa11y commentedDisabling Devel removes the Ajax message and "Finish" is possible, but it does still not work.
Comment #14
drupa11y commentedUpdated to Panopoly Magic 7.x-1.18+3-dev -> does not solve the problem
Updated to Panelizer 7.x-3.2-beta1+19-dev -> does not solve the problem
"admin/config/content/panelizer/user/user.page_manager/content" changed to
"admin/structure/panelizer/user/user.page_manager/content"
Log-Messages:
Comment #15
drupa11y commentedUpdated to Panels 7.x-3.5+0-dev & cTools 7.x-1.6+2-dev -> does not solve the problem
Logmessages as already mentioned above and
Comment #16
astringer commentedHi I'm getting what I believe is a similar error trying to format a number in a pane for a content type. The number is formatted in "manage displays" correctly. The number displays correctly (with a comma) in a non-panelized node view. But is incorrect in the panelized page (uses a space). It's like the setting doesn't get saved in Panelizer.
Log
When I try to edit the exact same (field format > comma) for a single node I get:
Any ideas for a work around? I'm fairly new to drupal and very new to panels. Thanks.
Comment #17
hanoiiThis is really affecting for a number of formatters, if not all of them. I have a registration field which is also failing to be saved. Disabling panopoly_magic seems to make it work for the time being, but really looking for a fix or better workaround. If there's any pointers I might try to take a look but probably not an easy one to fix for one that hasn't work on it.
Comment #18
dsnopekThanks, @candelas, for all the research you did! This looks like a regression caused by this change to CTools, which you found: #2152405: ctools_fields_get_field_formatter_settings_form() not fully compatible to field_ui
Thanks, @mori, for all the testing and the detailed information you added here! That definitely helped me in figuring out how to fix this.
Anyway, here is a patch to panopoly_magic that should fix this! I may just commit it since this is a critical bug. But normally I wouldn't allow a change to panopoly_magic without simultaneously adding Behat tests, so I'm going to see how quickly I can put some together.
Comment #19
hanoiiIt does work, however, I see [no preview] on every field, is that on purpose:
It's less critical though, but it was a nice feature.
Comment #20
dsnopekNo, that's not on purpose! It's definitely a bug. But I think we should make a new issue for that, so we don't delay this one getting committed. Can you create the new issue and post your screenshot in it? Thanks!
Comment #21
dsnopekHere's a patch to a Behat test for this functionality! It fails without the panopoly_magic patch, but passes with it. I'm going to run these both on Travis-CI quick, and if everything passes, I'll commit.
EDIT: Here's the Travis-CI build: https://travis-ci.org/panopoly/panopoly/builds/54893939
Comment #22
dsnopekHere's a new test patch! That one left the IPE open which broke subsequent tests. :-) I'll try on Travis-CI again once it's posted.
EDIT: Here's the Travis-CI build: https://travis-ci.org/panopoly/panopoly/builds/54904570
Comment #23
hanoiiNew bug created #2454947: Preview doesn't update when editing the value of a field via FAPE
Comment #24
dsnopek@hanoii: Thanks! :-)
Comment #25
dsnopekThere was a PHP >= 5.4 error in panopoly_magic and the Travis-CI tests run on PHP 5.4. This new patch should fix it!
EDIT: Here is the Travis-CI build: https://travis-ci.org/panopoly/panopoly/builds/54916105
Comment #27
dsnopekThe tests passed! Committed. :-) Thanks again, everyone, who worked on this issue!
Comment #28
candelas commentedThanks to you for all your generosity. I hope I finish with an installation with node.js and can test again to collaborate with Panopoly :)