Php – Magento 1.3.2.2: Fatal error: Call to a member function getUsername() on a non-object

adminfatal errormagentoPHP

In Magento 1.3.2.2 we get a fatal error:

Fatal error: Call to a member function getUsername() on a non-object in 
.../app/design/adminhtml/default/default/template/page/header.phtml on line 31

During an order confirmation, Magento should make a transition to the success page. But we are getting that error instead.

An Admin header is shown with this error. If I refresh, I get to the success page where I should have been taken if everything was ok.

Best Answer

This error happens because header.phtml on line 31 has entry:

$this->getUser()->getUsername();

But getUser() method didn't return valid object. This method pretty simple and looks like this:

return Mage::getSingleton('admin/session')->getUser();

So, you should debug only one place: app/code/core/Mage/Admin/Model/Session.php Only one method setUser() object to session

public function login($username, $password, $request = null) {
    ...
    $this->setUser($user);

If user object loads and valid it is mean that you have problem with session it self:

check how cookies sets
cookies path and created time

It is not easy find the problem remotely without debugging. So I wish you success.

Related Solutions

Php – How to catch a PHP fatal (`E_ERROR`) error

Log fatal errors using the register_shutdown_function, which requires PHP 5.2+:

register_shutdown_function( "fatal_handler" );

function fatal_handler() {
    $errfile = "unknown file";
    $errstr  = "shutdown";
    $errno   = E_CORE_ERROR;
    $errline = 0;

    $error = error_get_last();

    if($error !== NULL) {
        $errno   = $error["type"];
        $errfile = $error["file"];
        $errline = $error["line"];
        $errstr  = $error["message"];

        error_mail(format_error( $errno, $errstr, $errfile, $errline));
    }
}

You will have to define the error_mail and format_error functions. For example:

function format_error( $errno, $errstr, $errfile, $errline ) {
    $trace = print_r( debug_backtrace( false ), true );

    $content = "
    <table>
        <thead><th>Item</th><th>Description</th></thead>
        <tbody>
            <tr>
                <th>Error</th>
                <td><pre>$errstr</pre></td>
            </tr>
            <tr>
                <th>Errno</th>
                <td><pre>$errno</pre></td>
            </tr>
            <tr>
                <th>File</th>
                <td>$errfile</td>
            </tr>
            <tr>
                <th>Line</th>
                <td>$errline</td>
            </tr>
            <tr>
                <th>Trace</th>
                <td><pre>$trace</pre></td>
            </tr>
        </tbody>
    </table>";
    return $content;
}

Use Swift Mailer to write the error_mail function.

Php – Reference – What does this error mean in PHP

Warning: Cannot modify header information - headers already sent

Happens when your script tries to send an HTTP header to the client but there already was output before, which resulted in headers to be already sent to the client.

This is an E_WARNING and it will not stop the script.

A typical example would be a template file like this:

<html>
    <?php session_start(); ?>
    <head><title>My Page</title>
</html>
...

The session_start() function will try to send headers with the session cookie to the client. But PHP already sent headers when it wrote the <html> element to the output stream. You'd have to move the session_start() to the top.

You can solve this by going through the lines before the code triggering the Warning and check where it outputs. Move any header sending code before that code.

An often overlooked output is new lines after PHP's closing ?>. It is considered a standard practice to omit ?> when it is the last thing in the file. Likewise, another common cause for this warning is when the opening <?php has an empty space, line, or invisible character before it, causing the web server to send the headers and the whitespace/newline thus when PHP starts parsing won't be able to submit any header.

If your file has more than one <?php ... ?> code block in it, you should not have any spaces in between them. (Note: You might have multiple blocks if you had code that was automatically constructed)

Also make sure you don't have any Byte Order Marks in your code, for example when the encoding of the script is UTF-8 with BOM.

Best Answer

Related Solutions

Php – How to catch a PHP fatal (`E_ERROR`) error

Php – Reference – What does this error mean in PHP

Warning: Cannot modify header information - headers already sent

Related Topic