Active
Project:
Panopoly
Version:
7.x-1.x-dev
Component:
Magic
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 Apr 2015 at 18:30 UTC
Updated:
13 Mar 2018 at 21:52 UTC
Jump to comment: Most recent
Comments
Comment #1
mazze commentedComment #2
dsnopekCan you try disabling the panopoly_magic module (which will disable previews entirely) and try saving the FPP and see if it's stored correctly?
If it is stored correctly when panopoly_magic is disabled, then that means this is a bug in panopoly_magic.
But if it's stored incorrectly even with panopoly_magic disabled, then it's an FPP issue and we'll need to fix it there first!
Thanks!
Comment #3
mazze commentedSure! I am in the middle of finishing some projects, but will try later this week.
Comment #4
mazze commentedHi David,
when I disable Panpoly Magic, storing the FPP does work, even with both field types (translatable, non-translatable) in the same FPP.
So it might be the Magic module. Let me know if I can help you with more testing!
Kind regards,
Matthias
Comment #5
dsnopekOk, thanks!
Comment #6
mazze commentedI thought I'd wait for the new FPP version in Panopoly to test again...;-)
But even after yesterday's update, its not possible to have FPP with multilingual fields. Neither does the preview work, nor are they stored correctly.
I use i18n module, entity translation, fpp bundles module, title field.
Comment #7
mazze commentedOK, found a way to make the preview work, although it's not the best user experience one might imagine;-)
- Create the FPP
- Save immediately
- Reopen
- Fill out the fiels
- Save
In this case, the preview works (although still some issues with title field sometimes). But maybe this helps – some language parameter is being delivered in edit mode, but not in create new mode...
Just tell me if i can help with more testing. And thank you so much for this incredible distro!
Comment #8
dsnopekIt's possible that this issue is fixed by #2398347: Panopoly Magic abuses FPP revisions, but it was merged a couple months before the most recent testing in #7, so maybe not. This definitely needs to be re-tested, though!