Statistics page error

  • Nemopress

    (@nemopress)


    13 years ago

    Hello,
    I’ve encountered this error in the Statistics page:

    Warning: Illegal string offset 'name' in C:\xampp\htdocs\wordpress\wp-content\plugins\leaguemanager\admin\stats.php on line 73

    This should be the problematic line of code:
    <th scope="col"><?php echo $field['name'] ?></th>

    Also, the Javascript bit that comes after the line, this one:
    onclick="return Leaguemanager.addStat("stat_cambi", 4, 4);"
    doesn’t work, but the two things might be related.
    At the moment I’m using xampp for local development but I’m planning to deploy it on a shared hosting which I guess will have a different PHP version.

    Thanks in advance.

    http://wordpress.org/extend/plugins/leaguemanager/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author LaMonte Forthun

    (@lamontef)

    13 years ago

    I haven’t worked with the stats function much as is with LeagueManager because I could never get it to work quite right. To be honest, my thought was that it needed to be looked at for a long-term plan for making it usable for long-term stats and not just season-by-season.

    I’ll have a look at it to see if I can come up with any issues that can be quickly fixed, but I don’t think it makes any sense to spend a lot of time on it as is, I think it’s going to end up being re-written and it’s one of the top priorities that I have.

    With that said, let me ask two questions:
    1). Are you using the latest version of LeagueManager (3.8.8 or 3.8.8.1)?
    2). Do you have ProjectManager installed?

    Thread Starter Nemopress

    (@nemopress)

    13 years ago

    I’ve got the 3.8.8.1 one. I do have ProjectManager installed but I’m pretty sure that the I had the error even before.

    I’m fairly proficient with other languages but I haven’t touched PHP in a long time and wouldn’t want to mess things up. What I can gather from a superficial look is that it’s trying to slice or lookup $field which isn’t an array in that particular case and choking up on that.

    Plugin Author LaMonte Forthun

    (@lamontef)

    13 years ago

    I’ll have a look tonight, see if I can duplicate the problem and get back to you…

    Thread Starter Nemopress

    (@nemopress)

    13 years ago

    Thanks for the help.
    I don’t want to waste your time though and I think that I found where the problems lies.

    It might be a bug depending on how you look at it but it’s most likely a very niche case. Anyway, the problem was on how the constants are defined in the defineConstants() function and how xampp translates them, or more correctly Windows. More precisely, what happens is that this bit:
    pluginPath: "<?php echo LEAGUEMANAGER_PATH; ?>"

    translates to something like this:

    C:\xampp\htdocs\wordpress/wp-content/plugins/leaguemanager

    and the parser obviously chokes as the the backslashes aren’t escaped.
    I have modified the function to output the proper string and it seems to work just fine.
    It’s something of a platform problem really. 🙂

    Plugin Author LaMonte Forthun

    (@lamontef)

    13 years ago

    Nice work…

    When you mentioned XAMPP, I had a feeling there was going to be a setting of sorts that would come up.

    Plugin Author LaMonte Forthun

    (@lamontef)

    13 years ago

    I think we have a few others having the same problem, can you explain what you had to do to get the paths right?

    Thanks

    Thread Starter Nemopress

    (@nemopress)

    12 years, 12 months ago

    Sorry for the delay. What I did was what I explained above, altough I’m not entirely sure that those other users are having this exact problem.

    I checked what the error was from the browser console, saw that there was a parsing error on that line:

    C:\xampp\htdocs\wordpress/wp-content/plugins/leaguemanager

    And proceded simply to replace the echo that generates it, I mentioned the exact line before, with a:

    C:/xampp/htdocs/wordpress/wp-content/plugins/leaguemanager

    Since I don’t have a general exposure to the codebase I’m still not entirely sure why the software would expose such absolute paths to the page, even with an OS filesystem reference, but it was as simple as modifying backslashes to avoid the automatic string escapes.

    A long-term solution, which I guess should be preferrable, would be assuring that, when on Windows, the first part of the path gets properly escaped or that at least the slashes are replaced when necessary.

    I hope I made myself sufficiently clear or I can explain it again.

    Plugin Author LaMonte Forthun

    (@lamontef)

    12 years, 12 months ago

    Yes, very clear…

    I use XAMPP on my Mac, but will install it on my PC and do a few tests to see how to fix things.

    Thanks

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Statistics page error’ is closed to new replies.