Seems to throw up a fatal error:

Fatal error: Call to a member function getCurrentTheme() on a non-object in /home/.../public_html/.../zp-core/zp-extensions/colorbox.php on line 20

when I activate colorbox plugin seems to be ok.

Am I missing something?

zenpage theme, latest release

Can you be a bit more specific? What exactly is the circumstance where this error occurs?

Sorry, here are the circumstances:

Colorbox plugin NOT enabled;
Register plugin enabled;
logged out;
click the "Register for this site" link;

1.4.0.1, Zenpage theme

Hmm. I cannot reproduce this. Nor does it really make any sense.

If the colorbox plugin is not enabled, then it should not be loaded, so could not throw any errors.

If you can reproduce the failure, please look in your database "options" table and find the option for zp_plugin_colorbox. (Do this when the failure is happening.) Report back the value you find.

Yeah - I know it doesn't make any sense, weird. I can reproduce it, and the value in the database is 0. I will try to investigate further. I cannot figure out why colorbox.php would be called, unless it was being forced by another plugin, but I cannot find it anywhere in register_user.php.

Is there any place where colorbox is force loaded, say in the admin files or something? I noticed the register_user.php loads some admin files.

Also, why would this error even be happening, the error in colorbox.php is:

`

$_zp_gallery->getCurrentTheme()

`

why would this be throwing a fatal error?

colorbox is force loaded in admin-globals.php, but then the OFFSET_PATH define should be non-zero, so that code should not be invoked. But I guess if somewhere the admin-globals are bein loaded without that define set it could be the problem.

On the otherhand, your description indicates that this is happening on the front-end. In that case, the $_zp_gallery variable should also be defined.

This could be avoided by changing that bit of code to first create its own copy af a gallery object, then using that copy. But still would like to know how this is happening, specially since I did not reproduce it.

[edit]
Got it: The development branch has a fix for this that seems not to have got to the support branch. I will get that released and it will be in the nightly build tonight. The above description unfortunatly did not apply to the trunc branch.

Thank you sbillard. Your edits in the nightly has solved my issue.