All add-ons currently require PHP 7.4 or greater.
On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.
Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: CMS—Exception caught: No such property
| Status | Resolved |
| Add-on / Version | Custom System Messages 3.0.1 |
| Severity | |
| EE Version | 3.2.1 |
Peter Stalker
Mar 20, 2016
Description:
This is a CMS installation on a site I have just updated from EE 2.7 to EE3. Without CMS installed, emails go through with the standard EE error messages. With CMS installed, the emails still go through but there is no CMS message, only an ‘Exception caught’ error. I have attached various relevant screenshots. I notice that the action codes are different from those on my other, new EE3 installation
Detailed steps to reproduce the issue:
1. Entering a valid or a non-valid message at http://www.jerichowharf.com/contact
BoldMinded (Brian)
This is a different error than what you got on Friday? The attached image does not show any exception error.
BoldMinded (Brian)
There is only 1 image attached to the ticket.
Please respond via the website and not in the notification emails. Thanks.
Peter Stalker
Comment has been marked private.
BoldMinded (Brian)
And you’re using the same build I sent on Friday that worked on the other site? Can you share the template code and a screenshot of the settings?
Peter Stalker
Comment has been marked private.
BoldMinded (Brian)
Did you try testing the form without the Captcha?
Peter Stalker
Comment has been marked private.
BoldMinded (Brian)
Go to that file and add this var_dump($data) die;, then submit the form to reproduce the error. Copy/paste the output here.
https://www.dropbox.com/s/g99hei0t6e4fk7t/Screenshot 2016-03-20 16.13.08.png?dl=0
Peter Stalker
Comment has been marked private.
Peter Stalker
Comment has been marked private.
BoldMinded (Brian)
You’re welcome. If you report it to Low, point him to this URL and send him that error message stack trace too. I can’t think of how CSM would be involved, but if it is I can work with Low to fix the conflict.