SitePoint Sponsor

User Tag List

Results 1 to 8 of 8
  1. #1
    SitePoint Member
    Join Date
    Aug 2010
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    problem upgrading to wordpress 3.01

    Hi, I just upgraded from wordpress 3 to 3.01 and now I get this;

    Fatal error: Cannot redeclare trackback_rdf() (previously declared in /home/collage/public_html/culturaldissection.co.cc/wp-includes/comment-template.php:747) in /home/collage/public_html/culturaldissection.co.cc/wp-includes/deprecated.php on line 2515

  2. #2
    Programming Team silver trophybronze trophy
    Mittineague's Avatar
    Join Date
    Jul 2005
    Location
    West Springfield, Massachusetts
    Posts
    17,014
    Mentioned
    187 Post(s)
    Tagged
    2 Thread(s)
    Hi bananagrenade, welcome to the forums,

    That function is defined only in the deprecated.php file in WordPress 3.0 and only in the comment-template.php file in WordPress 3.0.1

    Sounds like you maybe did an overwrite? The "auto-upgrade" feature?

    Anyway if you make sure all the files are 3.0.1 and there are none "left over" from earlier versions you should be OK

  3. #3
    SitePoint Member
    Join Date
    Aug 2010
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question

    Hi, how did you solve it? I have the same problem now, my message is:
    Fatal error: Cannot redeclare trackback_rdf() (previously declared in /homez.361/kryptoma/www/wp-includes/comment-template.php:747) in /homez.361/kryptoma/www/wp-includes/deprecated.php on line 2515

    What I have to do via ftp? Thanks!

  4. #4
    Programming Team silver trophybronze trophy
    Mittineague's Avatar
    Join Date
    Jul 2005
    Location
    West Springfield, Massachusetts
    Posts
    17,014
    Mentioned
    187 Post(s)
    Tagged
    2 Thread(s)
    AFAIK the only way for this to happen is because the wp-includes/deprecated.php is the one that was in WordPress 3.0

    If you replace that with the wp-includes/deprecated.php file from version 3.0.1 that error should be resolved.

    However, I would be concerned that there are other files "left over" and other errors/bugs might crop up.

    To repeat my question to bananagrenade,
    Sounds like you maybe did an overwrite? The "auto-upgrade" feature?

  5. #5
    SitePoint Member
    Join Date
    Aug 2010
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by Mittineague View Post
    AFAIK the only way for this to happen is because the wp-includes/deprecated.php is the one that was in WordPress 3.0

    If you replace that with the wp-includes/deprecated.php file from version 3.0.1 that error should be resolved.

    However, I would be concerned that there are other files "left over" and other errors/bugs might crop up.

    To repeat my question to bananagrenade,
    ---Quote---
    Sounds like you maybe did an overwrite? The "auto-upgrade" feature?
    ---End Quote---
    Yes, auto-upgrade...

  6. #6
    Programming Team silver trophybronze trophy
    Mittineague's Avatar
    Join Date
    Jul 2005
    Location
    West Springfield, Massachusetts
    Posts
    17,014
    Mentioned
    187 Post(s)
    Tagged
    2 Thread(s)
    I wonder if it's a bug in that feature. I tried it once when it first came out, but I have a few hacked Core files that I need to upload manually anyway so I just download - unzip - edit - delete old - upload new.

    I don't think there's an easy way to determine if the auto upgrade feature has left other files. You could use your FTP client to look at file dates, but that would be time consuming and I imagine many files are repackaged unchanged from earlier versions and would be OK.

    I've already upgraded to 3.0.1 but next version release I'll try the auto, download the files to localhost, then uninstall - install manually, download the files again and compare.

    Until then I guess you have 2 choices. Replace only the wp-includes/deprecated.php file and hope for the best. Or install everything manually.

    Seems to me if the auto feature was buggy the issue would have come up sooner, but who knows.

  7. #7
    SitePoint Member
    Join Date
    Aug 2010
    Posts
    3
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    [QUOTE=Mittineague;4677815]
    Until then I guess you have 2 choices. Replace only the wp-includes/deprecated.php file and hope for the best. Or install everything manually.

    QUOTE]

    Thanks!!! It works!!! (the first option, replace only the deprecated) I have now the 3.0 version, and I think it will stay for a long time...

  8. #8
    SitePoint Member
    Join Date
    Sep 2010
    Posts
    1
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Hey all. This happened to me after auto upgrading.

    The good news is that replacing the deprecated.php file with the 3.01 version worked.

    For those looking, here's the code:
    http://phpxref.com/xref/wordpress/wp...php.source.txt

    Just copy that into a text editor, save as deprecated.php in the /public_html/wp-includes folder and your wordpress site will return.


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •