• Should you upload the entire wordpress folder, or just the wp_admin, wp-content, wp_includes and all the files inside it? Does it matter?

    Reason for asking is I was having problems accessing the login screen on godaddy because the local wordpress that i uploaded to it included the wordpress folder itself, whereas I only uploaded the aforementioned folders as per wpbeginner’s advice. Godaddy support then added the entire wordpress folder and I started seeing things, but not sure still since it seems to load the local machine directories the links still point to, so not sure about that, since I hadn’t changed the link urls yet.

    Also how do you change the wp-login.php url path? So that I can get to it without the /wordpress folder (provided it’s not needed), so that I can get to it via domain.com/wp-login.php? Couldn’t find any reference to it in wp-login.php.

Viewing 15 replies - 1 through 15 (of 18 total)
  • Thread Starter heardpress

    (@heardpress)

    shoulda tried stackoverflow?

    Using the folder depends on if you want to have /wordpress/ in your sites URL or not. If you just want the top-level domain, then you would upload all of the files inside the /wordpress/ directory into your servers public root folder.

    Thread Starter heardpress

    (@heardpress)

    Yea, that’s what i figured. But if I skip the wordpress folder, how do I change the redirect for wp-login.php so that it doesn’t point to .com/wordpress.wp-login.php, and instead to .com/wp-login.php? I found no reference to wp-login.php’s path inside wp-login.php, so assume it must be in another file, but there are so many.

    There’s no redirection that goes on standard. If you install WordPress in a folder, you use that folders name as well:

    www.mysite.com/sub-folder/wp-login.php

    If it’s installed in the root folder for the site it’s just

    www.mysite.com/wp-login.php

    Thread Starter heardpress

    (@heardpress)

    Yea, but when I did that i kept getting a 500 server error, and with the help of support we figured it was a mis redirect, i.e loging-php redirected to mysite.com/wordpress/wp-login.php, but at that point I had only uploaded the wordpress folder’s content, then as soon as support added the whole wordpress folder the redirect worked. But I don’t want it to read mysite.com/wordpress, hence wonder how to tell wordpress to not redirect to the /wordpress directory even when it doesn’t exist.

    Thread Starter heardpress

    (@heardpress)

    See as soon as I remove the wordpress folder, and only leave in place its content inside root, my site breaks, no styles applied, because wordpress acts like there’s still a /wordpress directory. I’m assuming it’s based on how it’s set up on my local machine where i uploaded it from, but isn’t there a way to change wordpress path, since it seems it can’t detect the change on its own?

    Ahh… That sounds more like you have moved the files, but you haven’t updated the URL’s in the database. That’s a common issue (and somethng that the architecture of WordPress doesn’t handle anywhere near as well as it should).

    WordPress holds all links and URL’s in the database as full URL’s, so everything will point to http://www.mysite.com/wordpress as an example, so when you move the site into a root folder, the system will still look for the /wordpress folder as that’s what’s stored in the database.

    There’s some plugins that can work with this for you, but I’ve had the most luck with this tool (use the V. 2 one). That will update everything in the database, and should get your site back on track.

    Thread Starter heardpress

    (@heardpress)

    Great, thanks for keeping it up. Happen to know what database table the urls are in? I know of for example wp_options for changing home page and site url, but not as for the ones you’re talking of have no idea.

    wp_options is the main one with the two main settings.

    BUT, WordPress stores URL’s as full URL’s for posts, and in ooptions and meta as serialised arrays, and these can’t be updated with a simple database query as you’ll break the array serialisation. That’s why you should run a tool like the one that I’ve linked above as it will change everything everywhere that it needs to be changed and do it the right way.

    Thread Starter heardpress

    (@heardpress)

    Ok, i downloaded it. I assume I should replace mysite.com/wordpress with mysite.com, correct, and check ‘all tables’, as we don’t know the ones containing the urls, just in case you know.

    Yes that’s correct.

    And just another note as well… Once you do this you will need to have all of the files in the root folder, not the /wordpress/ folder. And re-generate your permalinks by setting them to ‘Default’ and saving, and then back to your current settings and saving again. You need to do this to make sure that the .htaccess file is correct (it won’t work if you copy it directly from a sub-folder).

    Thread Starter heardpress

    (@heardpress)

    Thanks, will keep that in mind.

    Thread Starter heardpress

    (@heardpress)

    Oh, pity. After running interconnectit worpdress still redirects to site.com/wordpress/wp-login.php, even though I replaced site.com/wordpress with just site.com. The tool doesn’t tell you if there was a success either does it?

    Not sure yet what the button options are for either, like dry run, live run, I just ran ‘update details’, but again, it doesn’t seem updated so far.

    The buttons are for what it does. ‘Dry Run’ goes through the process but doesn’t update anything so you can see what the results are. ‘Live Run’ does this live and makes the changes. Both tell you how many changes were done. The ‘Update Details’ button only stores the values that you’ve put in for later on. You need to actually hit the ‘Live run’ button for it to change anything for real.

    Thread Starter heardpress

    (@heardpress)

    Swell. But, I just ran live run and seems to get no more than 1 cell changed, and it’s post related, nothing about login-php. Even tried replacing site.com/wordpress/wp-login.php with site.com/wp-login.php, but nil. So where’s wordpress/wp-login.php stored?

    Again I get a 500 error because wordpress redirects to wordpress/wp-login.php after login in from site.com/wp-login.php, but there’s no /wordpress directory on the server.

Viewing 15 replies - 1 through 15 (of 18 total)

The topic ‘Uploading wordpress, which folders to include?’ is closed to new replies.