lumenbeing

Hi Andrea. Found this post through a google search and its close enough to my issue I hope y’all don’t mind me tacking on.
I’m moving a example.com to a multisite configuration using subdomains and domain mapping.
I’m currently tracking example.com with google analytics. Under the new system I have created:
sub1.domain.com -> (to be) mapping to example.com
sub2.domain.com -> mapping to example2.com
sub3.domain.com -> mapping to example3.com

Right now sub1.domain.com is a duplicate (with some design changes) of example.com
Before I map it and change the DNS at the registrar level so example.com points to the multisite (on a different sever) I want to get sorted out what is the best google analytics strategy here.
Ultimately I would like to track all three domains within the same GA account. I mean I guess I do? The sites are set up to look like they all belong together with tabs at the top. Really example2.com and example3.com were formerly part of example.com, we decided to break it up for SEO purposes since we are targeting 3 keyword groups.
So if a visitor enters one subsite, then makes her way to another, I still want to know what the original referrer was. I don’t want to see sub sites showing up as traffic sources for the other sites. Especially for conversion tracking purposes.
Is there a way for me to do this and still be able to look at site traffic individually too. Maybe a separate profile and filter for each?

Okay that didn’t work either…

Okay so making the change you suggested did not solve the issue. But I think we’re on the right track now. Obviously I’m way out of my depth with apache config, but I found this interesting note on https://httpd.apache.org/docs/2.2/mod/core.html#options

Normally, if multiple Options could apply to a directory, then the most specific one is used and others are ignored; the options are not merged. (See how sections are merged.) However if all the options on the Options directive are preceded by a + or – symbol, the options are merged. Any options preceded by a + are added to the options currently in force, and any options preceded by a – are removed from the options currently in force.

Maybe I need plus symbols?

Yep that part is working fine. Just wondering about the way options are set here. Based on your wild guess.

Ipstenu, thanks for taking an interest in my issue. It is really holding up development for this site. Going to try your suggestion now. Oh and thanks for showing me how to correctly form the pastebin link.
BTW there is also a a httpd-vhost.conf file where the wildcard lives. It is linked to at the end of htpd.conf
Maybe check it over and see if you spot any problems there.

# Use name-based virtual hosting.
#
NameVirtualHost *:80
<Directory />
    Options FollowSymLinks
    AllowOverride All
    Order deny,allow
    Deny from all
</Directory>
#
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for all requests that do not
# match a ServerName or ServerAlias in any <VirtualHost> block.
#
<VirtualHost *:80>
    ServerAdmin [email protected]
    DocumentRoot "/opt/bitnami/apache2/htdocs"
    ServerName echotreemedia.com
    ServerAlias *.echotreemedia.com

#    ErrorLog "logs/dummy-host.example.com-error_log"
#    CustomLog "logs/dummy-host.example.com-access_log" common
</VirtualHost>

I think there is a clue here ??

Yep. I’ve got a bunch of these:
[Thu Jan 27 12:30:00 2011] [error] [client 123.125.71.107] File does not exist: /opt/bitnami/apache2/htdocs/interactive-post
[Thu Jan 27 12:30:03 2011] [error] [client 123.125.71.111] File does not exist: /opt/bitnami/apache2/htdocs/test-post
[Thu Jan 27 12:30:08 2011] [error] [client 123.125.71.115] File does not exist: /opt/bitnami/apache2/htdocs/feed
[Thu Jan 27 12:30:12 2011] [error] [client 123.125.71.107] File does not exist: /opt/bitnami/apache2/htdocs/welcome
[Thu Jan 27 12:30:16 2011] [error] [client 123.125.71.103] File does not exist: /opt/bitnami/apache2/htdocs/about-2

er…

<script src="https://pastebin.com/embed_js.php?i=Bs35eVjN"></script>

Didn’t know about the forum rules for pasting in loads of code. Here is the httpd.conf:
Embedded Code For Paste ID: Bs35eVjN

Thanks for the response. Yes. Sub-domains are working. Its just the permalinks that are causing me trouble.

I have a different problem. My domain is configured for sub-domains but I can’t get permalinks to work. I fear it is a combination of bad settings in htaccess , httpd.conf , and httpd-vhosts.conf
Andrea to the rescue?

Okay I have resolved myself to the fact that WordPress is just going to change my domain back to the public URL every time I restart the instance. I can live with it.
But I can’t live without permalinks. I need Buddypress to work.
So the latest thing I’ve tried is changing my wordpress.conf file.
to this:
‘<Directory “/opt/bitnami/apache2/htdocs”>
Options Indexes MultiViews +FollowSymLinks
AllowOverride All
Order allow,deny
Allow from all
</Directory>’

And now the site gives me 403! PLEASE HELP!

So far setting up multi-site on AWS / ec2 has been one thing after another.I can’t get permalinks and subdomain multi mode to work at the same time.

Now this is weird. After changing the database, everything worked fine, but I’m not having trouble with permalink. They just don’t work. I get 404 everytime. So I figure that must be something to do with the httpd.cnf or httpd-vhost.conf but here’s the weird part. Everytime I make a tweak to these files I have to restart Apache to see the effects, but every time I restart Apache, those datebase tables go back to https://ec2-50-16-250-250.compute-1.amazonaws.com for site and URL fields. Then I get locked out again and have to change them again through phpMyAdmin.
Now I’d really like to solve my permalink problem, but before I can do that I need to know what is overwriting my database when I restart my EC2 instance. There does not even seem to be a Site URL or WordPress directory field in my admin settings anymore after enabling multi-site.

Awesome. You were right Andrea. I had to change the site and home tables. Took some doing but I finally figured out how to get phpmyadmin to work. Turns out there was a phpmyadmin.conf file and I had to add ‘Allow from all’ in there.