Bug #68517
closed
FlexForm does not change while switching to another Plugin
0%
Description
Hello,
when I change from Plugin1 to Plugin2 in my Content-Record the FlexForm was not changed. Further the message that "the form fields will change now" does not appear.
After changing the plugin I have to save first now.
Stefan
Updated by Daniel Goerz over 9 years ago
I cannot reproduce this. Does this error still exist?
Updated by Stefan Froemken over 9 years ago
I have this problem on current master from 27.07.2015 08:08.
Tested in FF and Chrome.
No JavaScript problems logged in console.log.
Updated by Frans Saris over 9 years ago
- Status changed from New to Needs Feedback
Updated by Stefan Froemken over 9 years ago
It worked since years. I just confirm it on TYPO3 6.2. I don't have a TYPO3 7.3 installation here.
Updated by Markus Klein over 9 years ago
- Status changed from Needs Feedback to New
Updated by Andreas Wolf over 9 years ago
- Status changed from New to Rejected
Works for me on current master. As others also reported that it works, I’ll close this.
@Stefan ping me on Slack if you can reproduce it again, then we can sort it out. :-)
Updated by Anja Leichsenring over 9 years ago
- Status changed from Rejected to New
this is reproducable.
How I do it: I have in current master installed ext:news and ext:cal. Then a plugin is created on any page, and the select field with the available plugins contains News and Calendar. Selecting any value does not reload the form, so the dedicated flexforms are not shown.
Updated by Anja Leichsenring over 9 years ago
- Status changed from New to Rejected
Obviously it is only me. We tried this now with four people. Sorry to say this, there must be some weird configuration issue, and maybe the moon phase plays a role as well. Lets wait for other reports to come it, that help shine a light on this. I will close the issue until then.
Updated by Markus Klein over 9 years ago
- Sprint Focus deleted (
Stabilization Sprint)
After hours of tracing we found out that a garbled TCA is the culprit.
Caused by the bootstrap_package. Pull request https://github.com/benjaminkott/bootstrap_package/pull/210
Updated by Markus Klein over 9 years ago
- Target version deleted (
7.4 (Backend))
Updated by Anja Leichsenring over 9 years ago
- Status changed from Rejected to Resolved
so no core error, only a missing $GLOBALS in third party extension. Thanks for this catch.
Updated by