-
Notifications
You must be signed in to change notification settings - Fork 20
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
not compatible with userforms 5.3.2 #40
Comments
+1 I have also have encountered this issue, but this time with Userforms 5.4.0 and I can confirm that the error above is caused by this module as removing it (with |
Had the same issue too. |
Was this issue ever fixed? I noticed that there is a commit labeled: Work around CMS crash on user-defined forms, does that commit have any effect on this issue? |
@mooror Since this issue is still open, i guess it isn't fixed yet |
This was fixed as of version 1.0.6. |
@oddnoc i'm still experiencing this issue |
@guyvanbael Can you provide details of your environment or a minimal example where this issue arises? |
@oddnoc using latest silverstripe (4.10), userforms 5.11.1. (and theres elemental-userforms as well 3.1.0). If i remove the silverstripe-seo module, the page is accessible again. Thanx for looking into it! |
I'm unable to reproduce this issue. Can you provide your composer.json? |
Here's the composer.json. Mind that i've swapped out the module for the toastnz's opengraph module because this site is already live. |
using it in conjunction with userforms 5.3.2 (on ss4.3.3)
This is what's in the error log.
Uncaught Exception BadMethodCallException: "Object->__call(): the method 'Fields' does not exist on 'SilverStripe\CMS\Model\SiteTree'" at /Users/xxx/Documents/webroot/xxxx/vendor/silverstripe/framework/src/Core/CustomMethods.php line 54 {"exception":"[object] (BadMethodCallException(code: 0): Object->__call(): the method 'Fields' does not exist on 'SilverStripe\CMS\Model\SiteTree' at /Users/xxx/Documents/webroot/xxx/vendor/silverstripe/framework/src/Core/CustomMethods.php:54)"} []
The text was updated successfully, but these errors were encountered: