WordPress.org

Support

Support » Alpha/Beta » WP 3 Alpha/Beta

WP 3 Alpha/Beta

  • How can semi skilled users get development releases?
    I’ve googled numerous patches for multi blogs on non MU, but don’t want that struggle.

Viewing 15 replies - 1 through 15 (of 32 total)
  • I am not sure I completely understand your question, but if you are just looking to keep up with the development builds, you can download a nightly build of WP 3.0 from the link on this page:

    http://wordpress.org/download/nightly/ “download the latest nightly build”

    Or you may want to use subversion access.

    Thanks, but that only goes to 2.9. Still want 3 beta.

    You can use the WordPress Beta Tester plugin to convert a 2.9.2 install to 3.0-alpha and get the latest nightly builds via automatic update:

    http://wordpress.org/extend/plugins/wordpress-beta-tester/

    Choose “bleeding edge nightlies” in the plugin’s settings to get you the latest and greatest.

    Thanks. Got that plugin but upgrade only went to
    http://wordpress.org/nightly-builds/wordpress-2.9-latest.zip
    How do I make it get the alpha? (I have made a new domain for this.)

    Oh, I have yet to try the “bleeding edge”.
    That got me
    http://wordpress.org/nightly-builds/wordpress-latest.zip.
    and “You are using WordPress 3.0-alpha.”
    Thanks

    OOOoookaaayy. As I mistakenly posted in
    http://wordpress.org/support/topic/365622?replies=4#post-1437806
    “I managed to get WordPress 3.0-alpha. So where are directions for setting up multi-blogs, from root, sub folder, or whatever?”
    Search and browsing did not find answer.
    It seems to me that a sticky page on installing pre release versions of WP3 would be handy — until the docs are formally updated.

    Thanks, but that only goes to 2.9. Still want 3 beta.

    I’m not sure if I follow you… did you get 3.0 Alpha or no?

    I’m using 3.0 Alpha right now on a test server. This link I referred you to: “download the latest nightly build” is where I got it. That seems to put a nice fresh copy of 3.0 alpha on your desktop. Download it and navigate to /wp-includes/version.php;

    /**
     * The WordPress version string
     *
     * @global string $wp_version
     */
    $wp_version = '3.0-alpha';
    
    /**

    – or read the readme.html. I’ve been running it on a test server for a while now.

    It also looks like the subversion access url I pointed you to might also be 3.0 Alpha as well.

    “To check out the latest WP codebase, try this checkout command:
    svn co http://core.svn.wordpress.org/trunk/

    This will “check out” all of the files you’ll need. To update your working copy later, go into the directory and run this command:
    svn update

    That will update all your file to the latest. If you’ve made a change you want to submit back to the core this will show you what files you’ve changed:

    svn status

    And this will output a line-by-line description of all the changes in a format that makes it easy for us to incorporate:”

    ….again, you can open readme.html or version.php to confirm.

    As for your other question… “So where are directions for setting up multi-blogs, from root, sub folder, or whatever”

    It is an Alpha release remember. You can follow release developments here: http://wpdevel.wordpress.com/ and there is a pretty good article on the multi-blog feature here: WordPress 3.0 Multisite Settings

    If you do discover that I am not using the latest and greatest alpha version that I think I am, could you please post a link to your download for 3.0? I had thought that I was keeping up with the current alpha build, but if not… I sure would like to.

    Thanks a million!!!

    I just tested this plugin on WP 3.0. http://wordpress.org/extend/plugins/wordpress-beta-tester/

    It does as advertised. If left in “Point release nightlies” mode it will update you to the latest 2.9 release. If you choose “Bleeding Edge” option, it will download from the URL I gave you above. 3.0 Alpha. The plugin solution should work just fine if you don’t use subversion.

    Ok so far. ver 3 alpha installed with choice of subdomains. Made cat.mydomain.com and dog.mydomain.com 3/16/0, still not found on internet a day later. Was I supposed to also create subdomains thru cpanel? If so, with what paths? My task is better served with subdomains than subfolders option.

    Any idea if the 2.9 themes will work on 3.0 Final Release? I would like to make my own theme but if it won’t work on the next version I’m not going to bother…

    Andrea Rennick

    @andrea_r

    Customer Care at Copyblogger Media and Studiopress

    @mugger

    Was I supposed to also create subdomains thru cpanel?

    They work on wildcard subdomains, you have to set those up on the server and in your DNS records.

    I’m betting the readme hasn’t been updated. Virtual subdomains are instant. no waiting. Tho now that I think of it, there should have been a message on the network setup page.

    Any idea if the 2.9 themes will work on 3.0 Final Release?

    No reason why they shouldn’t. I’m running 3.0 while testing all kinds of themes.

    They work on wildcard subdomains, you have to set those up on the server and in your DNS records.

    Just had to make a subdomain named asterisk. So, if I still need to make the subdomains in Cpanel, what do I point them to? Default?

    Ok, I used CP to make the ‘new’ subdomains. Now I just see the bare index’s, no tie to WP 3 alpha.

    I modified a prior WP install on another domain with beta plugin, up’d to 3alpha, enabled tools>Network, but don’t see SuperAdmin.

    Will anyone get me started before full release “in May”???

    My WP3 setup #1 is in root, for subdomains — which I had to enable in cpanel for browser to find. Still no connection from WP3, just minimal index in browser.
    My WP3 setup #2 is in a sub folder, still have not seen SuperAdmin DASHBOARD, so unable to test add-on blogs as subfolders.

    DASHBOARD said that one can not change choice of subdomain versus folders, which is unfortunate.

    By the way, both domains do show new 2010 theme, so parts are working.

    Andrea Rennick

    @andrea_r

    Customer Care at Copyblogger Media and Studiopress

    No no no,.. the asterisk *is* the wildcard. That is all that is need as long as your webhost also has wildcard subdomains enabled on your accout in Apache.

    Do not manually create the subdomains in cpanel. Those will be used by the sub-blogs in MU if you pick the subdomain option when you set it up. If you are choosing subFOLDER blogs, then you do not need to worry about wildcard subDOMAINS at all.

    you will not see the Super Admin menu until you set up the Network. you won’t see that menu item at all until you edit wp-config.php to include this line:

    define('WP_ALLOW_MULTISITE', true);

    1. I HAVE set up NETWORK in both. See SuperAdmin only in one.

    2. Hostgator told me that making a subdomain with asterisk as name is how to enable wildcards. Other companies have harder methods, or do not allow (such as BlueHost, I read somewhere).
    [I can ask them to verify.]

    3. Before I made the subdomains thru cpanel, about 36 hours had passed since I created them in 3 alpha and they NEVER appeared in my browser. So wp3 is at fault.

    4. Dashboard said the syntax is now
    define( ‘MULTISITE’, true );
    I added your older version and got “Problem loading page. The page isn’t redirecting properly.”
    http://as93.com/a93w/wp-login.php?redirect_to=http://as93.com/a93w/wp-admin/
    “Firefox has detected that the server is redirecting the request for this address in a way that will never complete.”

    Backleveled wp-config.php and http://as93.com/a93w/wp-admin/ no longer works.

    So, what I think you told me is negative advice.
    But, thanks for attempting to help me.

Viewing 15 replies - 1 through 15 (of 32 total)
  • The topic ‘WP 3 Alpha/Beta’ is closed to new replies.
Skip to toolbar