Title: wordpress admin pages broken?
Last modified: August 21, 2016

---

# wordpress admin pages broken?

 *  [Burgejos000](https://wordpress.org/support/users/burgejos000/)
 * (@burgejos000)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/)
 * So recently I’ve been been messing around with the back end of wordpress. Yesterday,
   after updating a page, i was sent to a blank page. The url is domain.com/wp-admin/
   post.php I didnt think anything of it. But now, a co-worker of mine is unable
   to log into wordpress. She logs in on the admin page and ends up with a blank
   page. I’ve restored all of the wordpress files, but the same errors still occur.
   Any ideas of what to do?

Viewing 15 replies - 1 through 15 (of 19 total)

1 [2](https://wordpress.org/support/topic/wordpress-admin-pages-broken/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/wordpress-admin-pages-broken/page/2/?output_format=md)

 *  [WPyogi](https://wordpress.org/support/users/wpyogi/)
 * (@wpyogi)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739656)
 * What is the URL?
 *  Thread Starter [Burgejos000](https://wordpress.org/support/users/burgejos000/)
 * (@burgejos000)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739660)
 * [http://www.hisresources.org/wp-admin/post.php](http://www.hisresources.org/wp-admin/post.php)–
   where my problem is
    [http://www.hisresources.org/wp-admin/login.php](http://www.hisresources.org/wp-admin/login.php)–
   where my coworker’s problem is
 *  Thread Starter [Burgejos000](https://wordpress.org/support/users/burgejos000/)
 * (@burgejos000)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739663)
 * Sorry. the URL she was having problem with is [http://www.hisresources/wp-login.php](http://www.hisresources/wp-login.php)
 *  [WPyogi](https://wordpress.org/support/users/wpyogi/)
 * (@wpyogi)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739664)
 * Does this not work:
 * [http://www.hisresources.org/wp-login.php](http://www.hisresources.org/wp-login.php)
 *  [WPyogi](https://wordpress.org/support/users/wpyogi/)
 * (@wpyogi)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739668)
 * Cross-posted – see: [http://codex.wordpress.org/Resetting_Your_Password](http://codex.wordpress.org/Resetting_Your_Password)
 *  Thread Starter [Burgejos000](https://wordpress.org/support/users/burgejos000/)
 * (@burgejos000)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739671)
 * well. i just changed the password, i’m redirected to here: [http://www.hisresources.org/wp-admin/profile.php](http://www.hisresources.org/wp-admin/profile.php)
   and here’s another blank page
 *  Thread Starter [Burgejos000](https://wordpress.org/support/users/burgejos000/)
 * (@burgejos000)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739673)
 * resetting the password did not help with the login
 *  [RockSolid Design](https://wordpress.org/support/users/cfmwebdesign/)
 * (@cfmwebdesign)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739675)
 * Try enabling php error logging to see if there are any errors pointing to the
   problem file/location.
 * [http://codex.wordpress.org/Debugging_in_WordPress](http://codex.wordpress.org/Debugging_in_WordPress)
 *  Thread Starter [Burgejos000](https://wordpress.org/support/users/burgejos000/)
 * (@burgejos000)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739682)
 * Well, i enabled debugging mode (i didn’t know this existed. I will definitely
   be using this).
    I ended up getting the following error: Notice: is_page was 
   called incorrectly. Conditional query tags do not work before the query is run.
   Before then, they always return false. Please see Debugging in WordPress for 
   more information. (This message was added in version 3.1.) in /home7/leaddog1/
   public_html/hisresources/wp-includes/functions.php on line 2959
 * this is what is on lines 2951-2959. there was a message shaything that there 
   was an error before these lines. There was another error message 3 times before
   
   function _doing_it_wrong( $function, $message, $version ) {
 *  do_action( ‘doing_it_wrong_run’, $function, $message, $version );
 *  // Allow plugin to filter the output error trigger
    if ( WP_DEBUG && apply_filters(‘
   doing_it_wrong_trigger_error’, true ) ) { $version = is_null( $version ) ? ” :
   sprintf( __( ‘(This message was added in version %s.)’ ), $version ); $message.
   = ‘ ‘ . __( ‘Please see [Debugging in WordPress](http://codex.wordpress.org/Debugging_in_WordPress)
   for more information.’ ); trigger_error( sprintf( __( ‘%1$s was called **incorrectly**.%
   2$s %3$s’ ), $function, $message, $version ) );
 *  Thread Starter [Burgejos000](https://wordpress.org/support/users/burgejos000/)
 * (@burgejos000)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739689)
 * These are the errors that I am getting:
 *     ```
       /**
        * Marks a function as deprecated and informs when it has been used.
        *
        * There is a hook deprecated_function_run that will be called that can be used
        * to get the backtrace up to what file and function called the deprecated
        * function.
        *
        * The current behavior is to trigger a user error if WP_DEBUG is true.
        *
        * This function is to be used in every function that is deprecated.
        *
        * @package WordPress
        * @subpackage Debug
        * @since 2.5.0
        * @access private
        *
        * @uses do_action() Calls 'deprecated_function_run' and passes the function name, what to use instead,
        *   and the version the function was deprecated in.
        * @uses apply_filters() Calls 'deprecated_function_trigger_error' and expects boolean value of true to do
        *   trigger or false to not trigger error.
        *
        * @param string $function The function that was called
        * @param string $version The version of WordPress that deprecated the function
        * @param string $replacement Optional. The function that should have been called
        */
       function _deprecated_function( $function, $version, $replacement = null ) {
   
       	do_action( 'deprecated_function_run', $function, $replacement, $version );
   
       	// Allow plugin to filter the output error trigger
       	if ( WP_DEBUG && apply_filters( 'deprecated_function_trigger_error', true ) ) {
       		if ( ! is_null($replacement) )
       			trigger_error( sprintf( __('%1$s is <strong>deprecated</strong> since version %2$s! Use %3$s instead.'), $function, $version, $replacement ) );
       		else
       			trigger_error( sprintf( __('%1$s is <strong>deprecated</strong> since version %2$s with no alternative available.'), $function, $version ) );
       	}
       }
   
       /**
        * Marks a file as deprecated and informs when it has been used.
        *
        * There is a hook deprecated_file_included that will be called that can be used
        * to get the backtrace up to what file and function included the deprecated
        * file.
        *
        * The current behavior is to trigger a user error if WP_DEBUG is true.
        *
        * This function is to be used in every file that is deprecated.
        *
        * @package WordPress
        * @subpackage Debug
        * @since 2.5.0
        * @access private
        *
        * @uses do_action() Calls 'deprecated_file_included' and passes the file name, what to use instead,
        *   the version in which the file was deprecated, and any message regarding the change.
        * @uses apply_filters() Calls 'deprecated_file_trigger_error' and expects boolean value of true to do
        *   trigger or false to not trigger error.
        *
        * @param string $file The file that was included
        * @param string $version The version of WordPress that deprecated the file
        * @param string $replacement Optional. The file that should have been included based on ABSPATH
        * @param string $message Optional. A message regarding the change
        */
       function _deprecated_file( $file, $version, $replacement = null, $message = '' ) {
   
       	do_action( 'deprecated_file_included', $file, $replacement, $version, $message );
   
       	// Allow plugin to filter the output error trigger
       	if ( WP_DEBUG && apply_filters( 'deprecated_file_trigger_error', true ) ) {
       		$message = empty( $message ) ? '' : ' ' . $message;
       		if ( ! is_null( $replacement ) )
       			trigger_error( sprintf( __('%1$s is <strong>deprecated</strong> since version %2$s! Use %3$s instead.'), $file, $version, $replacement ) . $message );
       		else
       			trigger_error( sprintf( __('%1$s is <strong>deprecated</strong> since version %2$s with no alternative available.'), $file, $version ) . $message );
       	}
       }
       /**
        * Marks a function argument as deprecated and informs when it has been used.
        *
        * This function is to be used whenever a deprecated function argument is used.
        * Before this function is called, the argument must be checked for whether it was
        * used by comparing it to its default value or evaluating whether it is empty.
        * For example:
        * <code>
        * if ( !empty($deprecated) )
        * 	_deprecated_argument( __FUNCTION__, '3.0' );
        * </code>
        *
        * There is a hook deprecated_argument_run that will be called that can be used
        * to get the backtrace up to what file and function used the deprecated
        * argument.
        *
        * The current behavior is to trigger a user error if WP_DEBUG is true.
        *
        * @package WordPress
        * @subpackage Debug
        * @since 3.0.0
        * @access private
        *
        * @uses do_action() Calls 'deprecated_argument_run' and passes the function name, a message on the change,
        *   and the version in which the argument was deprecated.
        * @uses apply_filters() Calls 'deprecated_argument_trigger_error' and expects boolean value of true to do
        *   trigger or false to not trigger error.
        *
        * @param string $function The function that was called
        * @param string $version The version of WordPress that deprecated the argument used
        * @param string $message Optional. A message regarding the change.
        */
       function _deprecated_argument( $function, $version, $message = null ) {
   
       	do_action( 'deprecated_argument_run', $function, $message, $version );
   
       	// Allow plugin to filter the output error trigger
       	if ( WP_DEBUG && apply_filters( 'deprecated_argument_trigger_error', true ) ) {
       		if ( ! is_null( $message ) )
       			trigger_error( sprintf( __('%1$s was called with an argument that is <strong>deprecated</strong> since version %2$s! %3$s'), $function, $version, $message ) );
       		else
       			trigger_error( sprintf( __('%1$s was called with an argument that is <strong>deprecated</strong> since version %2$s with no alternative available.'), $function, $version ) );
       	}
       }
   
       /**
        * Marks something as being incorrectly called.
        *
        * There is a hook doing_it_wrong_run that will be called that can be used
        * to get the backtrace up to what file and function called the deprecated
        * function.
        *
        * The current behavior is to trigger a user error if WP_DEBUG is true.
        *
        * @package WordPress
        * @subpackage Debug
        * @since 3.1.0
        * @access private
        *
        * @uses do_action() Calls 'doing_it_wrong_run' and passes the function arguments.
        * @uses apply_filters() Calls 'doing_it_wrong_trigger_error' and expects boolean value of true to do
        *   trigger or false to not trigger error.
        *
        * @param string $function The function that was called.
        * @param string $message A message explaining what has been done incorrectly.
        * @param string $version The version of WordPress where the message was added.
        */
       function _doing_it_wrong( $function, $message, $version ) {
   
       	do_action( 'doing_it_wrong_run', $function, $message, $version );
   
       	// Allow plugin to filter the output error trigger
       	if ( WP_DEBUG && apply_filters( 'doing_it_wrong_trigger_error', true ) ) {
       		$version = is_null( $version ) ? '' : sprintf( __( '(This message was added in version %s.)' ), $version );
       		$message .= ' ' . __( 'Please see <a href="http://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information.' );
       		trigger_error( sprintf( __( '%1$s was called <strong>incorrectly</strong>. %2$s %3$s' ), $function, $message, $version ) );
       	}
       }
       ```
   
 *  [RockSolid Design](https://wordpress.org/support/users/cfmwebdesign/)
 * (@cfmwebdesign)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739704)
 * The debug feature helped me out on several times 🙂
 * The error youre getting is still not really helpful though …
 * Try disabling the custom theme youre using by renaming it via FTP. If I am correct
   WP will automaticly revert to the default theme. Do the same for the plugins 
   if that not helps.
 *  Thread Starter [Burgejos000](https://wordpress.org/support/users/burgejos000/)
 * (@burgejos000)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739710)
 * Where would i go via FTP to disable the custom theme manually? And for the plugins
   as well?
 *  Thread Starter [Burgejos000](https://wordpress.org/support/users/burgejos000/)
 * (@burgejos000)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739713)
 * The website displays normally, although it is very basic and in devlopement. 
   I would assume the problem is some where in wp-admin. Although none of those 
   files have been touched
 *  [RockSolid Design](https://wordpress.org/support/users/cfmwebdesign/)
 * (@cfmwebdesign)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739715)
 * Do you have access to the server where the website is hosted/uploaded? You should
   be able to do it through there if you don´t have FTP access.
 * Your site seems to be hosted by Bluehost, check if you have the login details
   for the admin panel.
 *  Thread Starter [Burgejos000](https://wordpress.org/support/users/burgejos000/)
 * (@burgejos000)
 * [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/#post-3739716)
 * I have the login info for blue host. Thats what i have been exploring through
   the last few days. Its set up through public_html rather than public_ftp, I still
   have control over everything in the site. Im not sure what file i would access
   to manually disable the themes and plugins. I am currently using the Graphene
   theme. It is the only theme uploaded to the site. That and a child theme of Graphene
   that i created.

Viewing 15 replies - 1 through 15 (of 19 total)

1 [2](https://wordpress.org/support/topic/wordpress-admin-pages-broken/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/wordpress-admin-pages-broken/page/2/?output_format=md)

The topic ‘wordpress admin pages broken?’ is closed to new replies.

## Tags

 * [admin](https://wordpress.org/support/topic-tag/admin/)
 * [Blank](https://wordpress.org/support/topic-tag/blank/)
 * [page](https://wordpress.org/support/topic-tag/page/)
 * [pages](https://wordpress.org/support/topic-tag/pages/)
 * [php](https://wordpress.org/support/topic-tag/php/)
 * [problem](https://wordpress.org/support/topic-tag/problem/)
 * [troubleshoot](https://wordpress.org/support/topic-tag/troubleshoot/)

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 19 replies
 * 3 participants
 * Last reply from: [RockSolid Design](https://wordpress.org/support/users/cfmwebdesign/)
 * Last activity: [13 years ago](https://wordpress.org/support/topic/wordpress-admin-pages-broken/page/2/#post-3739724)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics