nicholasmr / obblm

Automatically exported from code.google.com/p/obblm
26 stars 54 forks source link

"Coaches" info no longer displays at all when logged in #56

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Looking at a specific coach page when logged in shows no data -- page 
cuts off
2.
3.

What is the expected output? What do you see instead?

When I'm NOT logged in, I see all the normal data for a Coach page that 
was there in r29 and prior.  When I AM logged in and look at the same 
Coach page, I get the coach's name centered at the top, the grey headers 
of "Picture of *coach*" (which takes up 80% width) and "About" (20% width) 
below that, and then nothing; the page ends. Even for a coach who has a 
picture and some "About" text, that actual data does not show when logged 
in.

When logged in, I'd expect to see the coach's contact info, given the r32 
code update, and the rest of the expected data 
(photo, "About," "Teams," "Matches played")

What version of the product are you using?

038r34

Please provide any additional information below.

I'm assuming the problem is in the updated code in sections.php from r32; 
I skipped straight from r29 to r34, so I don't actually know if the r32 
version worked.  But I see that there were no differences in the 'Coaches' 
section of the sections.php code, so I'm assuming it wouldn't have been 
any different.

Original issue reported on code.google.com by lahat...@gmail.com on 26 Mar 2009 at 3:24

GoogleCodeExporter commented 9 years ago
I'm at r33 and I can see that "Contact information" column disappears when not 
logged
in and visible (with the data) when logged in. The rest of the team info is 
unchanged.

Original comment by blodae@gmail.com on 26 Mar 2009 at 4:02

GoogleCodeExporter commented 9 years ago
Works fine here.
I suspect that you have not run the newest SQL commands from the INSTALL file. 
This
usually leads to php errors, which stop the page loading suddenly - having the 
effect
you describe.

Please run the remaining SQL commands (running the same ones multiple times 
does no
harm) and make sure that all obblm program files are replace/updated.

Original comment by Nimda...@gmail.com on 26 Mar 2009 at 4:08

GoogleCodeExporter commented 9 years ago
Been there, done that. Several times even. You're not alone. ;-) A tip: if you 
run
the commands in a bunch and one fails - Rerun the statements after the failed
statement. Rinse and repeat until all are processed. (Failure usually means that
you've already run that statement.) Nicholas places newest SQL statement last 
as far
as I've seen.

/Daniel

Original comment by blodae@gmail.com on 26 Mar 2009 at 4:31

GoogleCodeExporter commented 9 years ago
Hmm, I know I was quite sure that I ran all the SQL commands when I went to r29;
Nicholas had pointed that out to me then to fix a different issue I'd had then, 
and I
also learned the "keep running the rest after one fails" trick then, too.  Oh 
well,
I'm sure I must have missed one somewhere, somehow, no matter how thorough I 
think I was.

I was on a deadline earlier and couldn't troubleshoot as much as I would have 
liked,
so I just rolled everything back to r29 for the time being and it appears to be
working normally again at that version.  I appreciate the suggestions and trust 
it
does work, so I'll try playing with the upgrade again later tonight.

Original comment by lahat...@gmail.com on 26 Mar 2009 at 11:15

GoogleCodeExporter commented 9 years ago
Please feel free to mail me a copy of your DB to nicholas.rathmann@gmail.com, 
and
I'll have a look at it. Note that there is no harm in doing so, passwords are of
course encrypted.

Original comment by Nimda...@gmail.com on 27 Mar 2009 at 10:23

GoogleCodeExporter commented 9 years ago
I see your league has taken the latest alpha into use. I'm assuming, from the 
thread
in your forum, that it works now.

Original comment by Nimda...@gmail.com on 5 Apr 2009 at 2:19