• hi
    my problem started after i updated my wordpress site.
    log in page was not showing…(blank page)
    after some research ive been told to delete blank lines on the functions.php file
    i did that and now the page comes up just fine
    but it messed up my website with a warning on the header and when i try to log in it does not let me and gives me more warnings.

    warning on header:

    Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-content/plugins/wp-e-commerce/wpsc-core/wpsc-constants.php on line 17

    warnings on log in page:

    Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-content/plugins/wp-e-commerce/wpsc-core/wpsc-constants.php on line 17

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-login.php on line 349

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-login.php on line 361

    warnings after trying to log in:

    Warning: session_start() [function.session-start]: Cannot send session cache limiter – headers already sent (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-content/plugins/wp-e-commerce/wpsc-core/wpsc-constants.php on line 17

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-login.php on line 349

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-login.php on line 361

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-includes/pluggable.php on line 669

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-includes/pluggable.php on line 670

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-includes/pluggable.php on line 671

    Warning: Cannot modify header information – headers already sent by (output started at /home/content/93/8282693/html/repairs/wp-includes/functions.php:1) in /home/content/93/8282693/html/repairs/wp-includes/pluggable.php on line 866

    can anyone help me please?
    website https://www.tikanti.com

Viewing 3 replies - 1 through 3 (of 3 total)
  • Your server needs its PHP SESSIONS configuring by your host – it seems the directory where sessions are stored may have incorrect permissions set.

    Thread Starter danieldude

    (@danieldude)

    hmm…. i replaced the function.php file with a new on from a different install and im back to a blank login page with no errors…

    and do you know what premissions i need to give to what directory?
    where are sessions stored?
    I’m kinda of a newbie

    function.php has nothing to do with permissions.

    It could be your /tmp direcotry and you can chmod (rwxr-xr-x) that will set the permissions to 755. But it also looks like you may have some plugin issues.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘getting warnings and cant access back-end’ is closed to new replies.