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: Publisher is causing an PHP Error when using the Assets 2.0.3 tag pair.
Status | Resolved |
Add-on / Version | Publisher |
Severity | Critical |
EE Version | 24 |
Filip Vanderstappen
Jan 24, 2013I’m using Assets 2.0.3 on ExpressionEngine 2.5.5 (and Publisher 0.97.6 installed). With the following code in a template:
{exp:channel:entries channel="products" entry_id="15" dynamic="no"}
{entry_id}
{products_images}{url}{/products_images}
{/exp:channel:entries}
It’s always resulting in this error (Full stack trace: http://cl.ly/image/2N231A1U0o25):
Fatal error: Call to a member function row() on a non-object in /Users/Filip/Sites/FOSWEB/system/expressionengine/third_party/assets/ft.assets.php on line 1193
When disabling Publisher (with the switch in Publisher settings) the error is gone. When you take a look at the full stack trace you can see it’s passing Publisher.
Cheers,
Filip
BoldMinded (Brian)
Ugh, I’m not seeing that locally either… Will try to dig into it more tonight.
BoldMinded (Brian)
Thanks for the stack trace too.
Filip Vanderstappen
I had the same error when sending a Cartthrob notification mail. Strack trace is here:
Filip Vanderstappen
Here is some more follow up information. This only happens in “Development” mode and only when when ‘replace_url’ is called through the Publisher_lib ‘apply’ function.
BoldMinded (Brian)
I think I might have this fixed in the next build. The pre_process check I added before was in the wrong location. I was seeing the Assets error locally prior to the change, and its not happening for me anymore. In the Publisher_lib file change the beginning of the apply method to look like this:
BoldMinded (Brian)
Filip, did this fix work for you?
Filip Vanderstappen
Sorry, forgot to give feedback on this. It worked out fine. Just tested it again on an isolated environment and it did the trick. Didn’t experience any other issues with this fix.