• dss

    (@dss)


    Installing WP 2.0 RC1 was exactly the same process as installing WP beta 2. There are no new incidents with the installation, nor with any theme or plugin (that I can see from an initial demonstration.)

    However, there are a number of issues:
    1. The import admin page has a database issue, can not connect because the headers have already been sent. Further, the width of this page looks like a centered 40% width, and something’s definitely wrong.

    2. The upload option from the options menu has now been removed. Rather than having both methods as I had hoped, we now only have the dreary iPhoto style upload organization in the admin/write section. That’s a pretty heavy bummer.

    3. There is a css issue in concert with page reloading. This effects several things which I can see immediately. The first is the highlight of activated or deactivated plugins. The page needs to be reloaded manually after the automatic reload executes in order to see the results reliably. This is also true for the Theme Switcher, and any other CSS related element associated with an automatic page reload.

    Cool things:

    a.) The css has been modified a little further in the admin section. All the links in the dashboard line up nicely, and the font is a little different. Looking better.

    b.) Themes now offer preview images. This will make selecting a theme a visual experience, and not a text based memory game. Nice touch!

    c.) The backup database plugin is lovely, and works very well.

    Overview:

    I still want an option to upload files and images apart from the post.php, and would also appreciate either the ability to browse other folders with the current system, or preferences to set for this system so that I don’t have to have them foldered by month and year in the wp-content folder.
    also, I’d still like the old logo to come back, this new one is not warming on me in the least.
    I am excited for the Tiger Admin theme plugin to be updated for version 2.0, I miss its simplicity and beauty deeply.

Viewing 11 replies - 16 through 26 (of 26 total)
  • moshu

    (@moshu)

    pcdinh,
    This isn’t an upgrade – yet. I hope you didn’t run it on a live blog. This version is still for testing…

    pcdinh

    (@pcdinh)

    Is there anyway to turn back. Because I tried to upgrade my current blog.

    There is no way back to 1.5.2 unless you have a full database backup.

    bob58

    (@bob58)

    as upgrade does changes to the database design, that won’t work … if you have a backup: restore it to your db and reinstall the old version.

    If you don’t have a backup, there is only the way forward … do you have any plugins installed ? If so, delete them (after backing up the files). Maybe it’s “just” an incompatible plugin, causing the problem.

    Deactivate plugins.

    Change themes.

    Delete the new files and reupload – do NOT overwrite.

    Tell us what else you have tried / are trying

    twasnow

    (@twasnow)

    When I tried to install 2 RC1 everything went fine until I tried to login, what happens there is due to some weird thing with my web host it has the wrong paths ie click logon and it sends the request to https://www.ourtake.net/www.ourtake.net/v2/wp-login.php…
    instead of
    https://www.ourtake.net/v2/wp-login.php

    I had this problem in 1.5 but all I had to do was change the databse siteurl option, but this version seems to be ignoring it.

    any suggestions, I can’t even figure out where it is geting the address form, or I would just manually change it.

    I should also mention that paths to the themes are incorrect as well as there is NO formatting on the main page or on the login page

    thanks

    Nick Momrik

    (@mtdewvirus)

    pcdinh
    Look for the following line…
    //define(‘DISABLE_CACHE’, true); in wp-settings.php and remove the two slashes so that it’s no longer a comment.

    I had this issue on one my sites because the DB version is reporting as nothing/blank for some reason. I’m guessing it’s in the cache somewhere, but haven’t had the time to dig yet.

    like a charm pcdinh, like a charm. now I just finished copying over all of the posts and all of then users to the new database. And you know what, I didn’t realize until AFTER that there was an upgrade utility GRRRRR

    so for everyone else out there that doesn’t look for such things if you are upgrading, go to wp-admin/UPGRADE.PHP if I am wrong about this, because I am not going to check it. someone please correct me.

    So in regard to my post above I have a couple of questions.

    Firstly, can I create a second instance of wordpress off of ONE database? That is, can I have Strayhorn running in one folder and create a separate folder for 2.0 (say, ‘wp’ and ‘wordpress’) and have them both run off the same database for testing purposes, or do they need a dedicated instance of the php database for each?

    Also,
    I’m running phpMyAdmin 2.5.0 and MySQL 4.0.13 – are these too old? Do i need to upgrade one, the other, or both (I’m aware there are newer versions of each available, but I’m usure exactly how old these are). Also, how do I go about upgrading them if need be? Sorry for my n00b-ness, but I really don’t know how all this stuff works very well and I’m currently getting an error if I try to upgrade WordPress to 2.0 (see my post above).

    Thanks. Any advice and information is greatly appreciated.

    > Firstly, can I create a second instance of wordpress off of ONE database?

    Technically yes. You just choose a different table prefix for each instance.

    > and have them both run off the same database for testing purposes,

    No. The schema of 1.5.2 is different from 2.0. The will not run of the same set of tables.

    > or do they need a dedicated instance of the php database
    MySQL Database actually.

    > Ask your webhosting provider if you are on shared hosting platform.

    thanks for the help, angsuman….

    Anyone know about the MySQL and phpMyAdmin versions I’m running… is that the source of my “glob()” error?

Viewing 11 replies - 16 through 26 (of 26 total)
  • The topic ‘WP 2.0 RC1 Upgrade Feedback’ is closed to new replies.