WordPress.org

Ready to get started?Download WordPress

Forums

Recuring "404 - File or directory not found" error (11 posts)

  1. kwgagel
    Member
    Posted 2 years ago #

    I've been getting this error since I installed fresh using version 3.0. I'm up to 3.3 now and still get it. I can replicate the issue when I add a new link using the Add link option under links. The thing is that it actually saves the link despite the error.

    Here is a cropped screen shot of the error:
    http://blogs.cnc.bc.ca/gagel/?attachment_id=38

    I'm using IIS 7.x on Windows 2008 R2 server.

    I've turned on debugging and logging and can't find anything to point me in the right direction despite errors being logged. Here is a sample of them:
    PHP Notice: WP_User->id was called with an argument that is deprecated since version 2.1! Use WP_User->ID instead. in D:\wordpress\wp-includes\functions.php on line 3542
    PHP Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in D:\wordpress\wp-includes\functions.php on line 3542
    PHP Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in D:\wordpress\wp-includes\functions.php on line 3542
    PHP Notice: add_contextual_help is deprecated since version 3.3! Use get_current_screen()->add_help_tab() instead. in D:\wordpress\wp-includes\functions.php on line 3458
    PHP Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in D:\wordpress\wp-includes\functions.php on line 3542
    PHP Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in D:\wordpress\wp-includes\functions.php on line 3542

  2. Knut Sparhell
    Member
    Posted 2 years ago #

    Hello

    I'm also running a lot of sites under IIS7.

    When I browse to wp-admin/links.php I get an empty page, but no error. From the PHP file header:

    This page is accessed by the link management pages and handles the forms and AJAX processes for link actions.

    1. Check that the file is there
    2. If it is, investigate why IIS refuses to serve it (blocked by insufficient user rights?)
  3. kwgagel
    Member
    Posted 2 years ago #

    I've had a look and the correct page is link.php not links.php. I checked against a fresh download for the correct files.

    Browsing to wp-admin/link.php just results in a blank page. But I'd expect that because no data has been exchanged with the server.

    Would you have any links to sites with info on correctly setting permissions up on IIS7?

  4. Knut Sparhell
    Member
    Posted 2 years ago #

    Yes, meant link.php

    From IIS7 admin, content view, locate the file, right click and check that this file has the same rights (read&execute) as the others in the folder.

    If you can get this file through the browser (blank page), then you have to look elsewhere.

    I will get back if I can find any clue.

  5. kwgagel
    Member
    Posted 2 years ago #

    Thanks, I just found something else out that might help us track this down.

    I logged in as the network administrator and tried it on the top level blog without any problem. Then using that same account I switched over to my blogs dashboard and tried adding another link.

    I got the same error. So it appears that this issue is for lower level blogs only - not the main top level blog...

  6. kwgagel
    Member
    Posted 2 years ago #

    I've managed to identify the source of the problem. Seems to be a logic error in the coding. Here's what's happening...

    The options.php file is issuing a redirect after saving settings. The redirect appears to be built using the absolute path of the settings page while appending the absolute path again to return the user to the settings page they were on. The resulting url looks like this:
    userblog/wp-admin/userblog/wp-admin/options-general.php?settings-updated=true
    Which leads to the 404 error. If I switch the code in line 164 of options.php to use $parent_file instead of the wp_get_referer() function it redirects the page properly.

  7. Knut Sparhell
    Member
    Posted 2 years ago #

    Are you ready to submit a formal bug report for this issue? If not, someone might help.

    Where does options.php and options-general.php come into this issue?

  8. kwgagel
    Member
    Posted 2 years ago #

    I'm doing that now.

    This error shows up when someone tries to save a new setting in their blog.

  9. kwgagel
    Member
    Posted 2 years ago #

  10. Knut Sparhell
    Member
    Posted 2 years ago #

    When this is on multisite and with BuddyPress, why didn't you say so in the first place?

    Your ticket is invalid. This is NOT a WordPress core issue.

    Next time you ask for support here, please give all relevant information. We help for free, using our spare time.

  11. kwgagel
    Member
    Posted 2 years ago #

    Ticket filed with buddypress and promptly closed as a wordpress core issue. See http://buddypress.trac.wordpress.org/ticket/3892 for more info.

Topic Closed

This topic has been closed to new replies.

About this Topic