Support » Everything else WordPress » What will happen when 1.3 is released?

  • After reading some one elses concerns on their blog, it got me thinking. What is going to happen to my heavily modified site (css, index.php) and all of my beautiful plugins when WP 1.3 is released?
    Are my (not mine but the ones I have installed) plugins and hacks going to work? Am I going to be looking at a lot of time to change over?
    Just trying to prepare myself mentally if it is going to be a long fight.

Viewing 10 replies - 1 through 10 (of 10 total)
  • I’ll admit I have been wondering a little myself. Not a problem for me… but like you said, I like to be prepared. 🙂
    One thing I cannot stress enough is to keep a detailed log of every modification you make. Makes things a lot easier for me at least. I keep a listing that includes the type of modification, the file it is in, where the file is located, what line(s) is/are modified and what the modified code is and what the original code is.
    Maybe I am just anal but it is very helpful to me. 🙂

    Mark (podz)


    Support Maven

    The CSS will remain unchanged so long as you do not upload the default one that comes in the package anyway. and overwrite what you have.
    I believe index.php has changed slightly, but putting in all your changes should not be a hassle.
    Plugin authors have had plenty of notice about any internal changes in the way WP handles data and variables, so hopefully all is good there.
    I certainly don’t see it as being any more of an issue than for the multitude of times I have upgraded.
    The best advice, as always, for anyone about to upgrade, is to backup your files. Backup the database. Backup your existing installation. If you haven’t installed Laughing Lizard’s OneClickBackup yet, do it now.
    If you do have a heavily modified site, then yes, it will take longer, but then that’s the price to pay – after all, the devs cannot know who has done what and engineer the product to work around it.
    How do I upgrade ?

    If you don’t want any new plugins and don’t need trackback, why go to the trouble of upgrading at all?

    Because we maybe interested in some other new feature…. or would rather have the latest, optimized code. Then there’s those of us who will wait for the dust to settle before upgrading… WP got all the way to Mingus before I finaly plunged into 1.2….but it’ll depend on what 1.3 holds in store for me.

    What will happen? The sky will fall, of course. (happily running 1.3-alpha-2 with plugins galore)

    Beel, I’m interested to see that plugins are working for you in 1.3-alpha-2.
    I get this note when I go to wp-admin/plugins.php : –
    Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/ on line 36.
    Any ideas what that means. Here’s the code, starting at line 35:
    $check_plugins = get_settings('active_plugins');
    foreach ($check_plugins as $check_plugin) {
    if (!file_exists(ABSPATH . 'wp-content/plugins/' . $check_plugin)) {
    $current = get_settings('active_plugins');
    update_option('active_plugins', $current);

    Moderator Ryan Boren


    WordPress Dev

    And make sure you run upgrade.php whenever you pick up a new nightly or update from CVS.

    Yea, the CVS Repository is finally back up!

    Weird. I activated a plug-in and the problem *seems* to have vanished!
    [Btw, this was a fresh install so there was no need to upgrade.]
    So, from your past experiences of this problem, is this common? Should I expect future problems or do you think it’s sorted?

    Oops – we’ve gone crazy again! I de-activated the plug-in and went to activate another and got all kinds of craziness.
    Not sure what nightly it is as someone else installed it on their server for me. I’ll see if I can get hold of them.
    There’s stuff kicking off all over the place now. E.g.
    Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/ on line 87
    Warning: Wrong datatype for second argument in call to in_array in /home/httpd/vhosts/ on line 115
    And when I now try to activate a plug-in I get:
    Warning: Invalid argument supplied for foreach() in /home/httpd/vhosts/ on line 87
    Fatal error: [] operator not supported for strings in /home/httpd/vhosts/ on line 11
    And nothing else.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘What will happen when 1.3 is released?’ is closed to new replies.