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: PHP error notification on Channel Fields edit page
| Status | Resolved |
| Add-on / Version | Publisher 1.5.9 |
| Severity | Trivial |
| EE Version | 2.9.2 |
Diederik v Hoorebeke
Nov 25, 2014This is the error:
A PHP Error was encountered
Severity: Notice
Message: Undefined property: stdClass::$field_name
Filename: Publisher/Publisher_lib.php
Line Number: 184The error is field type independent.
I hope it’s nothing to serious… 😊
BoldMinded (Brian)
If you don’t have field type installed then disable all other addons until the error goes away. This is most likely an addon conflict.
Diederik v Hoorebeke
Ok, I’ll check.
LouWii D.
I have the same issue. It’s apparently coming from FieldPack field types.
Each field type from FieldPack will throw those two errors :
A PHP Error was encountered Severity: Warning Message: Attempt to modify property of non-object Filename: Publisher/Publisher_lib.php Line Number: 173 A PHP Error was encountered Severity: Notice Message: Trying to get property of non-object Filename: Publisher/Publisher_lib.php Line Number: 184
Is there any way to solve this ?
BoldMinded (Brian)
Do either of you have the Entry Type fieldtype installed? If so, grab the newest version from Github.
Lima Test
Hi
I get a similar error.
It seems that the Expresso Store fieldtype causes this error. I uninstalled Store and the warning/notice disappeared.
I’m not sure how to fix this and if it is even a critical issue? Any help would be appreciated.
PS: Store 2.4.1 & Publisher 1.5.9
BoldMinded (Brian)
Just out of curiosity though, do you have Entry Type installed?
Search the Store files for the following string “ee()->api_channel_fields” and if you get search results, post back the lines of code where its found. I don’t have a license for the newest version so I can’t look myself.
BoldMinded (Brian)
I have the FieldPack installed locally and can’t replicate this issue. Something else, most likely Entry Type, is creating a new instance of ee()->api_channel_fields object, which is kind of a big no no in a singleton designed app. Entry Type was updated a few weeks ago to fix this issue.
If you don’t have Entry Type installed, then disable all other add-ons until Publisher is the only one left, and if the error is still occurring then create a new ticket. Since I can’t replicate this I’m chalking this up to an add-on conflict and marking it resolved.