BoldMinded

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 Fatal Error

Status Resolved
Add-on / Version Publisher 1.2
Severity Critical
EE Version 2.5.2

Mike C

Feb 27, 2014

Hi Brian -

We’re seeing this error come up for a staging version of a couple sites on MSM using a build you sent the other week:

Fatal error: Cannot call overloaded function for non-object in /chroot/home/cadexdev/system252/expressionengine/third_party/publisher/ext.publisher.php on line 111

We’re not seeing this on the production version which is still using Publisher 1.1.3.

Thoughts?

Thanks,
Mike

#1

BoldMinded (Brian)

I see this as line 111 in 1.1.3. Can you confirm its the same in your build?

ee()->load->add_package_path($publisher_path);

#2

BoldMinded (Brian)

Have you compared the PHP versions? The php.ini for memory allotment etc? If it happens on one environment and not another the first thing is to find out what the difference in the environments is.

#3

Mike C

Yes, same line in our 1.2 build. Current php memory limit is 256mb. Same php version… 5.4.14.

These environments should be pretty much identical… both deployed to the same host (Nexcess) within days of each other.

#4

BoldMinded (Brian)

I’ve never seen an error like that. Especially given that its a core EE method I’m calling. Did you var_dump the $publisher_path value to see if it was correct?

#5

Mike C

The path is correct. Also, this doesn’t happen all the time - occasionally the site loads ok.

#6

Mike C

Anything further regarding this issue Brian? Were waiting on this before potentially moving anything to production.

#7

BoldMinded (Brian)

I haven’t looked into this because I’ve never seen this happen in any of my environments or heard similar reports from people. It sounds like an environment issue to be honest.

#8

Mike C

Hmmm… ok. It just seems odd that we had no issue with 1.1.3 and now we have these issues with 1.2. I guess we’ll try upgrading to 1.2.2 and see if that helps.

#9

BoldMinded (Brian)

I hear what you’re saying, but the line of code it is throwing the error on is a pretty common core method to call in an EE add-on.

Is it always line 111? Which is this? ee()->load->add_package_path($publisher_path);

Have you searched the third_party folder to see what other add-ons are also calling this method?

#10

Mike C

Yep, it’s always that line… 111: ee()->load->add_package_path($publisher_path);

We have not… I’m guessing some others do but, well, it just seems too far past a coincidence for a site that’s been running fine in this respect for many, many months to now throw this error at us after the only change was literally upgrading to 1.2.

#11

Mike C

Just some further info on this… I’m not a dev and I haven’t had my dev look at this yet but we ran this by the hosting company (nexcess) who looked at the problem and they said the issue was that the load function in Pub was being called twice and the second time it didn’t have access to the add_package_path method (it wasn’t inheriting something).

#12

BoldMinded (Brian)

Mike, would you be able to zip up your site (and database) and send it to me for testing? I want to see if I can replicate this locally.

#13

BoldMinded (Brian)

Have you updated any other add-ons since this started happening? If you provided FTP access I could take a look at the dev site directly and do some debugging.

#14

Mike C

Nothing else updated - just Pub 1.2. These sites are a duplicate of what is currently in production - except for the updated Publisher 1.2.

I’ll update the ticket shortly with FTP and CP credentials - and you’re welcome to look through things. As said, the problem is not consistently happening which makes it tougher to troubleshoot. It was happening yesterday and as said, we walked through the site with Nexcess and they seemed to think there was nothing server related going on which rings true to me given the production sites are in a similar environment with them and have not been having any issues with Pub 1.1.3 (other than a non-related bug we had found which 1.2 fixes).

#15

BoldMinded (Brian)

Mike, you’re still running EE 2.5.2, which I dropped support for when 2.6 came out. You’ll need to upgrade before I can look into this further. In fact, upgrading might fix it since I can’t replicate it in a 2.7 or 2.8 environment.

#16

BoldMinded (Brian)

I’m going to close this. If you upgrade to 2.7 or 2.8 and this is still an issue just open a new ticket.

Login to reply