has_profile flag vs. profile table lookup

One user at CPDN managed it to have a profile but on some pages the profile link isn't shown. His "has_profile" flag is 0/false but the entry in the table "profile" is definitely there.

Some of the PHP functions use a lookup on the profile table to decide wether to show the link or not - those work in his case.

Other PHP functions rely on has_profile, those do not work.

I think it would be a good idea to change process_create_results() and put the SQL

update user set has_profile=1 where id=$user->id

behind the "else" part so it isn't dependant on a previously existing profile but updated in any case.

I didn't find how the flag could be 0 while the profile is still there but this would be an acceptable workaround as long as the reason is unclear.


Here's the related thread at CPDN.

Good you did post in CPDN forums, CPDN DEVs and or MODs will need to take care of that problem.....
____________
Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

> Good you did post in CPDN forums, CPDN DEVs and or MODs will need to take care
> of that problem.....


In this specific case, only the CPDN guys can help, yes.

But it would be a basic solution that helps for all projects if the change I suggested for process_create_results() would be made. It would make the flag "has_profile" more reliable.
____________

Now it is more BOINC related ;-)

http://isaac.ssl.berkeley.edu/alpha/show_user.php?userid=4

The user page has a link "show profile" but the link target says "No user profile exists for that user ID."

So there needs to be a bugfix on BOINC level.
____________