WordPress.org

Support

Support » How-To and Troubleshooting » [Resolved] Many bugs in wordpress (79 exactly!)2.6.2!!

[Resolved] Many bugs in wordpress (79 exactly!)2.6.2!!

  • Dear all,
    Actually i tested netbeans with wordpress sources and php debugger but
    in result
    79 bugs exactly exist on wordpress package;
    I don’t know how to send theit to wordpress Staff

Viewing 15 replies - 1 through 15 (of 17 total)
  • hello
    sorry to tell this for my first post, but its necessary for my opinion.

    im building modules and components for joomla and drupal.
    i would like to port some of them to wordpress.
    i remember having a good appreciation about wordpress with v2 and 2.5
    i have installed the 2.6.2 version on my local server and i get some errors that stopped my enthousiasm.
    i hope that this is only a temporary problem and the next version will be more stable.

    1/ headers already sent with the login page
    2/ im unable to use firebug because i always have javascript errors with ajax on the admin panel.

    my config :
    server :
    Apache/2.2.4 (Ubuntu) DAV/2 SVN/1.4.4 PHP/5.2.3-1ubuntu6.4 mod_ssl/2.2.4 OpenSSL/0.9.8e

    client :
    Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.9.0.3) Gecko/2008092510 Ubuntu/8.04 (hardy) Firefox/3.0.3

    note : im not asking for help about my problems because this is out of subject, but, i just would like to say that i m confirming a lot of bugs.

    re :

    headers already sent with the login page

    thats caused by not editing the wp-config.php file properly. Its a user introduced error, not something thats wrong with WP.

    re:

    im unable to use firebug because i always have javascript errors with ajax on the admin panel.

    youre wildly blessed. I used firebig, and the web dev toolbar without issue both inside and outside of wp-admin all of the time, without issue.

    Ive EVEN used IE’s equivalent to FF’s web dev toolbar inside wp-admin and had no trouble.

    so, like #1, thats your issue, not wordpress’

    Bugs can be reproduced.

    im not asking for help in this thread, because its not the place, but i just would like to answer about this.

    Its a user introduced error, not something thats wrong with WP

    i never had to edit the w-config.php file with 2.5 version.
    i have never edited this file.
    the blog should work with the default install system without any modification to the config file.

    @baudry – please see Reporting_Bugs.

    Moderator Samuel Wood (Otto)

    @otto42

    WordPress.org Tech Dude

    i have never edited this file.

    Then you never actually installed WordPress. Creating this file is basically mandatory to set up WordPress.

    i never had to edit the w-config.php file with 2.5 version.
    i have never edited this file.
    the blog should work with the default install system without any modification to the config file.

    …scratching my head over that statement.

    How would WordPress know what your database information is and where to find it for the installation? I don’t think you can install WordPress without editing wp-config, can you?

    define(‘DB_NAME’, ‘putyourdbnamehere’); // The name of the database
    define(‘DB_USER’, ‘usernamehere’); // Your MySQL username
    define(‘DB_PASSWORD’, ‘yourpasswordhere’); // …and password

    this file is automatically created by the installer

    i have never edited this file.

    you have to edit that file for wordpress to make the database connections, so thats simply not true.

    the blog should work with the default install system without any modification to the config file.

    you probably ought to open the file I am referring to, and take notice of its function.

    :

    You didnt paste the name of the file in the message, you didnt even paste the entire error message — so seemingly you dont want help.

    Here’s what it comes down to with those sorts of errors, and anyone with a decent knowledge of PHP should already know this. You cant send output to the browser before the headers are sent.

    WordPress doesnt do that ANYWHERE. ‘headers already sent ..” errors are not a result of buggy code inside WP.

    this file is automatically created by the installer

    its still edited. a file not in its default state has been edited.

    please reread my precedent post :

    i hope that this is only a temporary problem and the next version will be more stable.

    note : im not asking for help about my problems because this is out of subject

    this file is automatically created by the installer

    so, i regreat a lot to say that there are bugs, im very sorry to tell you this.
    this should be a problem with me for sure.
    if a modo would like to delete my posts and the ones that answered here, this could be very fine.
    only 2 posts should stay here ; the first one from Baudry and the answer from MichaelH

    Moderator Samuel Wood (Otto)

    @otto42

    WordPress.org Tech Dude

    I just tested the installer, and it definitely does not create extra blank lines at the bottom of the generated config file. And a default 2.6.2 install (using the online config generation method) gave me no errors on the wp-login.php.

    So somewhere, you had to have edited something.

    so, i regreat a lot to say that there are bugs

    bugs can be reproduced. nuff said.

    i have cleared everything and reinstalled and i dont have this bug anymore.
    maybe it was from a plugin that i installed then uninstalled.

    i dont have this bug anymore

    then it wasnt a bug, so why persist in calling it one.

    @ssm2017

    im building modules and components for joomla and drupal.
    i would like to port some of them to wordpress.

    Welcome to WordPress! Looking forward to see your plugins!

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘[Resolved] Many bugs in wordpress (79 exactly!)2.6.2!!’ is closed to new replies.