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: Errors installing Publisher Lite 2
Status | Resolved |
Add-on / Version | Publisher Lite 2.3.0 |
Severity | |
EE Version | 3.5.3 |
Luke Jennings
Mar 06, 2017Hi,
This is a similar issue to ticket #1403 but slightly different version info. When installing Publisher Lite 2 we receive the error “Fatal error: Class ‘BoldMinded\Publisher\Model\Gateway\CategoryGateway’ not found in /server_path/system/ee/EllisLab/ExpressionEngine/Service/Model/MetaDataReader.php on line 147”
Running on PHP v5.6.30
We’ve since tried this on a completely new install of EE v3.5.3 and still get the same error.
Thanks & regards,
Dave
BoldMinded (Brian)
Comment has been marked private.
Luke Jennings
Thanks Brian,
Tried the new build on the fresh EE install and got exactly the same error: “Fatal error: Class ‘BoldMinded\Publisher\Model\Gateway\CategoryGateway’ not found in /webroot/system/ee/EllisLab/ExpressionEngine/Service/Model/MetaDataReader.php on line 147”
BoldMinded (Brian)
Can you provide more info about your server? This issue seems new, but the code referenced here has not changed in months, and I’ve yet to experience it myself on 3 different servers.
BoldMinded (Brian)
Luke, are you still having issues with this? Have you tried it on a different server? Or tried it with a new/fresh EE install with no other add-ons?
BoldMinded (Brian)
Can you provide a list of all field types used in the entry you are getting the error on, and a list of all add-ons installed?
BoldMinded (Brian)
Luke, double check to make sure the Model/Gateway directory is title case. One of the other reports had the folder named Model/gateway, which was causing the problem. https://boldminded.com/support/ticket/1415
Luke Jennings
Apologies for the delay in coming back to you Brian, but it looks like this was the problem.
I’ve made this change and tried replicating the error on various environments and it all installs perfectly now, no errors or warnings, and the add-on seems to be functioning correctly.
Thanks for your help.