heardpress

James Huff, correct, I’d hard coded them into the files during local development, but now when trying to update them, even manually, as mentioned above they result in 500 internal server errors (even though the page urls match the ones under pages in dashboard).

I already migrated to an online host. I think better-search-replace isn’t what i need as it couldn’t find any localhost based urls in the database. It seems to me I need to manually change all page urls under ‘pages’, seems I can’t get rid of http://127.0.0.1/wordpress, and change it to http://www.mysite.com there either, and that’s after having changed site url in the wp_options table.
Just googled again and got pointed to velvet blue which couldn’t find one iota in the database, yet all links on the site point to local harddrive, strange.

Thanks, looks good, but seems it blanket replaces everything, as opposed to targets only link urls? Suppose supplying a url path should target mainly link hrefs and such, but am not sure, made a backup in case, but would prefer not messing unnecessary things up.

I think I give up for now, it seems I’m not able to replace anything of the sort, but thanks a lot for taking your time.

In the process of replacing mysite.com/wordpress/ with mysite.com/ we scanned 11 tables with a total of 750 rows, 0 cells were changed. 0 db updates were performed.

Btw, I’ve checked the .htaccess and tried changing among other things like

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /wordpress/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]
</IfModule>

# END WordPress

to

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

but that gives 404 and other errors. Wondered if there’s something to add to .htaccess to fix it, but that seems to go deep into geek territory and shouldn’t be required to set up the world’s supposedly most popular blog/web software.

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.

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.

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?