-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After updating from flux 5.0.0 to 5.2.1, the plugin show's only "No fields found in form" #37
Comments
Hi @vaxul - sorry for the delay in responding. Is the same problem relevant if you upgrade directly to Flux 5.3.0? I'm guessing you could be affected by a recurring 4.x branch issue with field names not being passed to a hook the way they should - and this should be finally solved in 5.3.0 (but if that fails then please do try the Git master; I'm not exactly sure if the fix in question is part of 5.3.0, it was written right around the release of 5.3.0. Cheers, |
Hi Claus, I try an update to 5.3.0. Here is it the same: "No fields found in form" within the "Plug-In"-tab. In the frontend is all fine. If I do a fresh install from git-master, I get the same error in the backend and a new error in frontend: I have tried to truncate the database tables 'cf_extbase_object', 'cf_extbase_object_tags', 'cf_extbase_reflection', 'cf_extbase_reflection_tags' and I have deleted the "temp_CACHED_xxx.php" files. Greets Vaxul |
Hi Vaxul, Sorry for the delay, missed the notification email. The class Tx_Flux_Service_FlexForm has been removed, merged into Tx_Flux_Service_FluxService - so depending on your situation you should do one of three things:
Hope that explains everything and helps you solve the problem! Cheers, |
Hi Vaxul, All errors regarding this class (including those caused by FED) have been fixed in the latest git masters - if a thorough clearing of cache and temporary files doesn't help, feel free to reopen this issue :) Cheers, |
Is their a breaking change in the plugin configuration or the flux-template? Clearing cache do nothing.
I think, I had an similar problem in the past with updating flux.
The text was updated successfully, but these errors were encountered: