The profile load function (profile_load_profile) was not found.

Please go back to your settings and make sure it is using the content_profile module (the "Module" tab); this message would indicate that you have chosen the core profile module.

Yes, if you don't have the core profile module enabled, I could see this happening before you select the content profile module and some fields. The fix for #340673: Fatal Installation Error should resolve this. It will be in the -dev version that rolls up at midnight GMT. I'm going to mark this as fixed by that; if it is not, please re-open it.

It won't roll a new version for another two hours or so yet (midnight GMT)

I realize this issue was mark as fixed and closed, but I am still having the profile load function was not found error show up. I am using Content Profile 6.x-1.x-dev.

Issue also exists with realname.module,v 1.4.4.26 2008/12/30 i.e. 6.x-1.1

In fact, after installing (then re-installing and clearing cache), the Module tab at admin/user/realname/module only shows Core Profile- there is not option to select RealName.

The error The profile load function (_load_profile) was not found. also displays on every page.

Drupal v 6.8

Rolling back to 6.x-1.1-rc3 actually fixes the issue- the error disappears! Stranger and stranger...

Hey Guys!

Did you already set this module up? After I added a field for realname and set it up into the module settings, the error message disappears.

Good Luck!

Greetings

CKIDOW

Aah yes this does work, silly omission... thank you CKIDOW!

Attached patch adds another check to make sure the $fields (and $module) variables have been set before displaying this error.

-  if (!isset($account->{key($fields)})) {
+  if (!isset($account->{key($fields)}) && !isset($fields)) {

Further testing showed that my patch broke things quite badly :)

I'll make another effort shortly.

EDITED TO ADD:
After trying a few different approaches, I'm not sure I have a good solution for this. I guess it's not a huge problem, but I'm sure there must be a better way to handle this.. Maybe moving the $module = variable_get(... to earlier in the function, and put it inside a module_exists to see which module are installed.

I uninstalled the module and saw what you've been reporting. It is fixed now.

The most recent stable version of this module, still has this bug.

"Fixed" means this is still in the -dev version. Check the project page for what fixes are in the -dev version. When I am satisfied that the -dev version has been tested adequately, I will publish it.

[edit: Never mind, found a fix by installing current dev release.]