devot:eeDevoted to ExpressionEngine

I just updated to EE 2.7.1 and get the following errors when trying to access the Modules section of the CP:

A PHP Error was encountered
Severity: Notice
Message: Use of undefined constant BASE - assumed ‘BASE’
Filename: taxonomy/base.taxonomy.php
Line Number: 174

A PHP Error was encountered
Severity: Notice
Message: Undefined property: Addons_modules::$cp
Filename: taxonomy/base.taxonomy.php
Line Number: 180

Fatal error: Call to a member function add_to_head() on a non-object in /expressionengine/third_party/taxonomy/base.taxonomy.php on line 180

I’m using Taxonomy 3.0.7

That’s really, really odd.

BASE is an ExpressionEngine constant, it’s used throughout the EE core and I’m scratching my head a bit wondering why it’d be giving you that error on the modules page.

What PHP version are you on?
What other Modules and Extensions are you running?
Have you modified that file?

The first mention of that constant is supposed to be line 172, not 174 which you have in your error output.

Also, can you confirm when you upgraded to 2.71 you ran the update wizard etc and everything else is running ok?

Looks to me like something is up with your upgrade.

Hi Ian,

PHP version 5.4.10
Sorry, the reason the line number is slightly off is because I was tinkering with it ;)
But it’s definitely line number 172 then 178 where add_to_head is called.

Quite a few other modules installed, but I only just updated EE and a few other modules, so I’ll see if anything else is causing this and get back to you..

Okay, the issue was somehow caused by the Publisher module.
Sorry about that, the errors pointed straight at Taxonomy so that’s where I started looking for answers.

Oh, and thanks for the quick support, much appreciated.

No worries, glad you got it sorted!

We just came across this issue. Maxwell, what was it about Publisher that was causing this? WHAT DID YOU SEE? (http://xkcd.com/979/)

FWIW, I haven’t seen any bug reports like this in ages for Publisher.

This is an EE 2.7.0 site, and Publisher isn’t even installed. I was wondering what it was about Publisher that we could possibly identify in another add-on.

I’m pretty sure this error only occurred for me when I tried to install Publisher and only when Taxonomy was already installed beforehand.

To get around it it I disabled Taxonomy, installed Publisher then re-enabled Taxonomy.

Thanks for rounding back and sharing! In our case, there was a mod security rule on the server that we were tripping up, and Taxonomy happened to be the scapegoat/red herring.