emanontest

that seems to be in line with what I was thinking it should be. So they shouldn’t both be set to the same thing.

ugh, either the nameserver settings haven’t updated yet (after switching them to dreamhost), or this still isn’t working..

that seems counter-intuitive to me. Your SITE is located at the domain URL, “home” by comparison to me sounds more like “admin homepage”.

So should I have one pointed to the domain and one pointed to the actual server directory? which should point where?

I’m currently testing on https://www.curiousitycrossroads.com

godaddy is set to forward to wordpress servers, and the site/url settings (are now once again) pointed to that domain.

over on weebly, this is basically all it takes. I tell godaddy that weebly has my site. I tell weebly what domain to send people to, and presto, website shows up as it should.

Here, this isn’t the case, and when I have both the site and home url set to my domain, I can’t figure out how to log into my backend anymore. domain.com/wp-login.php gives a 404.

I am on dreamhost. I tried pointing to dreamhost first thing this morning and just ended up getting a “page not found” error when the change took effect.

what I don’t get is why there is both a site url and a home url, if they are both supposed to be set to the same thing anyway? I would think the home url would be the actual server directory path and the site url would be the public domain. that would make sense.

I’ve been told over on wordpress.com forums that I have to pay for the domain mapping to do this, that’s apparently ‘the only way’. At this point it seems like it will stop this headache so I’m about ready to do it.

Sorry, you confused me, when you said standalone I thought you meant the yoursite.wordpress.com blog version, I am on a self-installed/hosted site, so I do belong here.

sorry, I keep getting confused that there are 2 different sites (why?), I thought I was on .com

I checked my settings as they suggest, I don’t have the “filter suspicious query strings” option checked, so that must not be the issue.

I just double checked and I have indeed re-activated jetpack and social sharing options in my settings, yet before the sharing icons were visible and now they are (still) not, so something is still off..

I guess I could always just install a different plugin for adding sharing icons to posts, but I don’t want to add any plugins for stuff that’s a core feature already.

I have not used PHPMyAdmin yet, i’ve only had to make a few small changes to php files and have done them in CuteHTML and then uploaded to the server.

I have not tried that other link you supplied, I’ll have to look into that… but what I fear is that the security plugin (Better WP Security in this case) altered files and so disabling it won’t un-alter them, so may not help. I also made the mistake with BWPS of disabling JetPack/Social Sharing which I have yet to figure out how to properly re-enable.

What I was thinking was since I was working on the site privately before officially launching (ie simply pointing the domain to wordpress instead of the placeholder page), and since the admin page is set as an extension of the domain now rather than as an extension of the server, if I point the domain at wordpress, then the /wp-admin page would become accessible again (essentially like turning the tumbler in a lock to create a valid pathway for the key)? Or is that not correct? I updated the nameservers in godaddy an hour ago but it’s still not pointing to wordpress (yet).

EDIT – As seems to have been the case a few times now – updating server files/settings in WP takes a good 15-20 mins to “take effect”, as I just managed to (by accident) stumble onto a valid login page and am now in the back end (and can see the WP site URL greyed out as what I changed it to from manually editing the wp-config file. Ok, this is a good start. Now I just have to figure out how to point the domain here properly!

I manually edited wp-config locally in a text editor and re-uploaded it to the server, overwriting the existing file, so even thought .htaccess says disallow any edits, I believe I can get past that.

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

# END WordPress

# Prevents directory listing
Options -Indexes

# protect wpconfig.php
<files wp-config.php>
order allow,deny
deny from all
</files>

OK, not sure how to delete my post, it turns out the code change did work, just not immediately (why making a PHP change would take upwards of 15 mins to show on a page refresh I don’t know). So this is resolved.