The MU forums have moved to WordPress.org

Pages not found (15 posts)

  1. rogerwebb
    Member
    Posted 16 years ago #

    I got mu loaded up a day or so ago but it wouldn't permit new users to register from the log-in page. Everything else seemed to work OK

    So i reloaded but now when I've finshed the start up procedure: input my data base details i get a clean 'OK' and then the login and password e-mail

    Opening the link gives me an unformatted login page which I use though its not looking formatted as it should - as if the css is missing

    Still I persevere but after logging in i get a 'psge not found screen'

    can anyone tell me how to solve my problem

    Filezilla will not let me remove the empty directories from failed attempts -many

  2. drmiketemp
    Member
    Posted 16 years ago #

    A link would help so we can see what is occuring.

    Best bet would be to go through your host's hosting program and delete those empty directories. They're usually run as root so they'll get deleted.

  3. rogerwebb
    Member
    Posted 16 years ago #


  4. drmiketemp
    Member
    Posted 16 years ago #

    Um, you may want to delete that as we no longer have a moderator around here who can. Please do it asap as you only get 10 minutes to do so.

    I mean a link to your site. Just need to see the outputted html.

  5. rogerwebb
    Member
    Posted 16 years ago #

    blog login http://retiredbutactive.co.uk/wpmu/wp-login.php

    password 8a6f1d372b70

  6. drmiketemp
    Member
    Posted 16 years ago #

    Yup, you've got the URLs wrong. You've got the index.php in the URL which is incorrect. (Probably should do a trac ticket on that since this isn't the first time it's come up.)

    Easiest way to fix is to delete everythhing and start over. When you go through the setup options and enter the URL, just put in the URL (ie http://retiredbutactive.co.uk/wpmu/) and not the index.php bit.

    If you can't reinstall or *chuckle* probably don't want to, open up your database and go through the tables and remove any mention of 'index.php' from the URLs. You'll need to review the wp_blogs, wp_#_options, wp_blog_versions, and wp_site (that's the important one) tables.

    Hope thi shelps,
    -drmike

  7. rogerwebbretiredbutactiveco
    Member
    Posted 16 years ago #

    In the end I had to clean out the data bases - as you suggested, plus all the blog material on my site and re-load from scratch.

    It came up ok eventually tho it never gave me options about where to place index php.

    However, unzipping leaves you with the site in a folder, in a folder. i had stripped off one as unnecessary, but now I've loaded up including the outer and apparently unnecessary folder - perhaps it is necessary!

    Now I `have the blog up i'm back to the original problem that the login screen gives no oppoertunity for a new member to register - if you've time to help me with that I'd be very gratefull

    In any cas; thanks for what you've done already

    Roger

  8. drmiketemp
    Member
    Posted 16 years ago #

    Where should wp-signup.php and wp-login.php be on your site? Are those files actually there and readable by the webserver?

    The unzipping bit is actually normal for linus software. You unzip locally first and then upload the files within that unzipped directory via ftp to where you want them to go. And yes, it's backwards to me as well.

  9. rogerwebbretiredbutactiveco
    Member
    Posted 16 years ago #

    It's there large as life http://www.retiredbutactive.co.uk/wordpress-mu/wp-signup.php

    but if you try to access it it returns the famous 404 response

    Roger

  10. drmiketemp
    Member
    Posted 16 years ago #

    That link works fine for me. Sign up works as well.

    The issue is that you've installed the software into a subdirectory and are trying to do subdomains off of it. You can't do that as it doesn't work. You wind up with URLs like the following and get the 404's:

    http://drmike.retiredbutactive.co.uk/wordpress-mu/

    If you put the software into a subdirectory, you can only offer subdirectory blogs to your end users.

  11. rogerwebbretiredbutactiveco
    Member
    Posted 16 years ago #

    I do appreciate your efforts on my behalf, but have to admit to being a little lost.

    When you talk of putting wpmu into a sub-directory I have to ask a sub-directory of what? The whole site (retired but Active0 is in a sub-directory of my site root (/RbA3/) and the unzipped wpmu comes nested in /wordpress-mu-1.2.3

    I have then uploaded to park wp in /RbA3/wordpress-mu/ (I took the -1.2.3 off the title to simplify the links.

    Where should the software be?

    Roger

  12. ekusteve
    Member
    Posted 16 years ago #

    You have your mu site here:

    http://www.retiredbutactive.co.uk/wordpress-mu/

    The wordpress-mu part is the subdirectory. You removed the "-1.2.3" from the directory to simplify...and that is good. The way you have it is the "typical" way people would set-up a regular WordPress install, but the general advice for Mu is to move all files out of the wordpress-mu directory and place them in your root. Then you would end up with the following address for your install:

    http://www.retiredbutactive.co.uk/

    Your site is loading with the subdirectory install, but the problems you are having may be related to this. It looks like you are using your root for your "retired but active.com website", so I understand that it could get a little "messy" moving all the mu files into root, if you have a lot of other files/folders there in support of that site then you would need to do a little reorganizing to make this work in root and still have your other site.

    Steve

  13. rogerwebb
    Member
    Posted 16 years ago #

    Many thanks to those who have helped me. I've learned rather more than I ever wanted to know to get to a (fairly) satisfactory result.

    In going through this process I have identified issues that must be common to a lot more installations than mine where the blog facility is part of a wider ranging site.

    1. the installation needs to go into the very root of your site even though the main part of the site is in a directory already. In my case, I have a site for the over-50s called retiredbutactive.com which is held on the server in a directory called /RbA3/. I put wordpress into a subdirectory /RbA3/wordpress-mu/ and it lost several funtions in the process.
    2. If the site doesn't load up to your satisfaction the first time round it is probobly advisable to remove the data base files it creates on your server before trying again.</p>
    3. When you unzip after downloading it from the wordpress site it will create a directory structure on your home machine with /wordpress-mu.1.2.3/ at the top. This appears superfluous but must be left in place for the upload to your site or all sorts of rubbish ensues.
    4. When you put it into the root it will create a direcory all on its own called /wordpress-mu.1.2.3/. Personally I renamed this /wordpress-mu/ to make the links easier.

    5. If you want your site to be a multi-blog with visitors able to run their own blogs then you need to make a separate link to /wordpress-mu/signup.php

    I do hope this is helpful.

    Roger Webb

  14. drmiketemp
    Member
    Posted 16 years ago #

    1) I believe it states that in the readme.txt file included within the download.

    2) You also have to remove the wp-config.php file and empty the .htaccess file. (Some host server software won't allow you to actually delete the .htaccess file. Emptying it will work fine.)

    3) No, actually. You upload the files contained within that subdirectory. Says so in the readme.txt file and it pretty much standard with almost all open source software. (Sucks though. I hate how they do that.)

    4) Actually I plaster that link everywhere I can. Main blog's theme, the meta widget, the meta area on all themes, the support forum, etc.

  15. lunabyte
    Member
    Posted 16 years ago #

    In regards to the package being extracted into a directory, that's the way it should be when it's extracted.

    Have you ever extracted a large package that dumps all of its files to where you extracted it, and created a huge mess or overwritten something important?

    It's a standard cya/safeguard to have the package extract to its own directory, and then have the end user decide where they want it.

About this Topic

  • Started 16 years ago by rogerwebb
  • Latest reply from lunabyte