Parse Error after upgrade to 2.0.3

  • I get the same error everytime:
    Parse error: parse error, unexpected T_STRING, expecting ‘]’ in /home/user/public_html/wp/wp-admin/admin-functions.php on line 1826

    If I replace the wp-admin file with 2.0.2 I don’t get this error- but can’t edit links- “sorry you don’t have permission”

    This is on a clean install from Fantastico 2.0, then upgrading to 2.0.3
    Several times- same thing.

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

  • Don’t replace wp-admin file, that’ll just hose you since the permissions model changes from 2.0.2 to 2.0.3. Have you tried the 2.0.3 Tuneup plugin? https://txfx.net/code/wordpress/wordpress-203-tuneup/

    It says it’s trying to find a missing closing bracket “]” on line 1826 of the admin-functions.php file. Have you modded the code at all? That’s part of the wp_import_handle_upload function. My code on that line looks like this:

    $file = wp_handle_upload($_FILES['import'], $overrides);

    Try pulling a fresh copy of that specific file out of the ZIP file and uploading it over the current one.

    The tuneup is very important, but it’s a plugin. You can’t activate it until after you have WordPress running initially.

    Thread Starter nextwave

    (@nextwave)

    I hadn’t modded any code-
    my line 1826 didn’t look like that.
    I’m running 2.0.2 now- and everything is working.
    I’m going to try upgrading a different WP install – and see if it works.

    I don’t think I can use the 2,0,3 tuneup- since I can’t ever get to 2.0.3 – correct?

    Right. As pvtguy so eloquently put it, it does you no good until you can actually run 2.0.3. Sorry for suggesting it — I misread your original post.

    Thread Starter nextwave

    (@nextwave)

    I use Transmit on a Mac to upload-
    it seems that if you are in “auto” mode- instead of Binary- you generate this problem.
    Took a while to figure this out.
    No other WordPress update has seemed to care- but 2.0.3 seems to.
    Thanks.

    Nextwave: I don’t see how that would affect it, but I don’t have a Mac, so I don’t know. If you’ve got it working, then you might want to mark this “resolved.”

    HandySolo: I didn’t mean for that to come across like that. I was just typing an answer in a hurry. Sorry. : /

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Parse Error after upgrade to 2.0.3’ is closed to new replies.