Viewing 15 replies - 16 through 30 (of 31 total)
  • There are also (old) reports that WP Super Cache can cause that problem.

    EDIT: Also see this thread.

    edit it by pasting the code wrodpress gave me

    What code? WordPress doesn’t give you any wp-config.php code during the install process or after.

    Thread Starter lilou1502

    (@lilou1502)

    i dont have that line though… should i add it ?
    all i have is :

    ….
    require_once(ABSPATH . ‘wp-settings.php’);
    ?>

    What file are you talking about? Are you working from a copy of wp-config-sample.php?

    Thread Starter lilou1502

    (@lilou1502)

    i believe i pasted the code it gave me after entering password, login… etc on that page : http://anyonecancook.99k.org/blog/wp-admin/install.php

    Thread Starter lilou1502

    (@lilou1502)

    instead of creating a blank php file and pasting the code, i used the wp-config-sample, deleted the code and pasted the one i got from wordpress

    Thread Starter lilou1502

    (@lilou1502)

    Here is what i did (from wordpress the missing manual) :

    Running the Install Script
    This is the final set of steps. Think of it as activating the WordPress site you just created.
    1. To start the installation, type the web address where you installed WordPress into your browser, and then add /wp-admin/install.php to the end.
    2. Click “Create a Configuration File.”
    and then got some code

    So you’ve not completed the installation yet?

    Thread Starter lilou1502

    (@lilou1502)

    yes i did because if i go to the install.php it says it is already installed but when i try to log in it doesnt work

    So what details are you adding to your new wp-config.php file? Please just give a general answer. Do not post the actual details here.

    Thread Starter lilou1502

    (@lilou1502)

    sorry but i’m not sure what you’re asking exactly…
    DB_COLLATE is empty but i guess it’s normal
    otherwise i have name, user, password, host, charset
    then a series of DEFINE and the end they tell not to chage in the comments… im sorry it’s probably not what you’re asking though. could you please reformulate the question ?

    The ONLY things you should be adding to the file are the database name, user, password & host.

    Thread Starter lilou1502

    (@lilou1502)

    what about that then:
    should it be like this :

    define(‘AUTH_KEY’, ‘put your unique phrase here’);
    define(‘SECURE_AUTH_KEY’, ‘put your unique phrase here’);
    define(‘LOGGED_IN_KEY’, ‘put your unique phrase here’);
    define(‘NONCE_KEY’, ‘put your unique phrase here’);
    define(‘AUTH_SALT’, ‘put your unique phrase here’);
    define(‘SECURE_AUTH_SALT’, ‘put your unique phrase here’);
    define(‘LOGGED_IN_SALT’, ‘put your unique phrase here’);
    define(‘NONCE_SALT’, ‘put your unique phrase here’);

    or like that

    define(‘AUTH_KEY’, ‘YbGv9c$vAd244jiY[G?W<WD5gDW]m),F:r0avil;%^*{wSK>T*@p]AOJg1n|`w~Y’);
    define(‘SECURE_AUTH_KEY’, ‘(:t/JOBIAx~C@mg+WJyN=NIO( n/_IR8_pg2qIq#!5.n<Hg:e3g0Ryc+I|(?^`’);
    define(‘LOGGED_IN_KEY’, ‘GjHix:/%K7I @2jCv>$V)?LNAzld2s@3qt5uJBr@d03Pu4a39r7&k4eh:F#W9a_N’);
    define(‘NONCE_KEY’, ‘q*GAu92.])s~+GnulSm8Y<JHx_nOi!/l9)Iq#SZ[vMbXTQb>i<%XJsmg5^M+D8Lq’);
    define(‘AUTH_SALT’, ‘d5IEDdHwedR_eRBGdS#3kEZs)P@-549.>#2?#XH83KC[%Z#i-_VNH_jq43(lK?6&’);
    define(‘SECURE_AUTH_SALT’, ‘,g9*=g#|J4rNi/EFOsKZwh4K..hMz,|44w+pcl@Mpi]vfxXMX Pw<X?QT$?]=XvQ’);
    define(‘LOGGED_IN_SALT’, ‘ oysDW5fI%F<Cl8a27PWk[Q{N&$ZD:hNm;^e:1SSp|wlys Ou*Ld|h8I_hv[=rc2’);
    define(‘NONCE_SALT’, ‘_h*U<]@{,]W3`tVDHMXx.G>+_7v4iSLn[2[@B$04xH_}&#U~.I:O:vRR@x&*UkG,’);

    that’s the only difference between the sample i edited and the one created by wordpress

    Thread Starter lilou1502

    (@lilou1502)

    thank you so much!!! with the one i edited myself, it works perfectly fine. its the frist code up there. i dont know why there’s so many other things on the other one created by wordpress

    I have the same problem but I can’t even login to the admin to edit the lines?? HELP

    Thanks!

    Warning: Cannot modify header information – headers already sent by (output started at /home/tomenz1/judgeolalewis.com/wp-content/plugins/wp-social-blocks/twitter_timeline.php:13) in /home/tomenz1/judgeolalewis.com/wp-login.php on line 384

    Warning: Cannot modify header information – headers already sent by (output started at /home/tomenz1/judgeolalewis.com/wp-content/plugins/wp-social-blocks/twitter_timeline.php:13) in /home/tomenz1/judgeolalewis.com/wp-login.php on line 396

    Warning: Cannot modify header information – headers already sent by (output started at /home/tomenz1/judgeolalewis.com/wp-content/plugins/wp-social-blocks/twitter_timeline.php:13) in /home/tomenz1/judgeolalewis.com/wp-includes/pluggable.php on line 678

    Warning: Cannot modify header information – headers already sent by (output started at /home/tomenz1/judgeolalewis.com/wp-content/plugins/wp-social-blocks/twitter_timeline.php:13) in /home/tomenz1/judgeolalewis.com/wp-includes/pluggable.php on line 679

    Warning: Cannot modify header information – headers already sent by (output started at /home/tomenz1/judgeolalewis.com/wp-content/plugins/wp-social-blocks/twitter_timeline.php:13) in /home/tomenz1/judgeolalewis.com/wp-includes/pluggable.php on line 680

    Warning: Cannot modify header information – headers already sent by (output started at /home/tomenz1/judgeolalewis.com/wp-content/plugins/wp-social-blocks/twitter_timeline.php:13) in /home/tomenz1/judgeolalewis.com/wp-includes/pluggable.php on line 875

Viewing 15 replies - 16 through 30 (of 31 total)
  • The topic ‘Cannot modify header information’ is closed to new replies.