I don’t care how dumb this sounds, b/c I know for some of you rocket ninja full stack gulping grunting vagrants, it’s gonna seem obvious…
The domain is https://pressily.com (so you’re with me, right? whew!)
I simply added a folder —> /l <— and stuck Mautic on https://pressily.com/l/ (notice the forward slash / and the lowercase letter --> L <— /l ?)
I’m guessing, wondering, hoping this’ll run right along side my WordPress installation.
Was that the wrong place to put Mautic?
Does it need to be in a sub.domain?
Thanks for the feedback folks!
(…this is what happens when a marketing & ecommerce idiot gets ahold of a new toy) HA!
I don’t care how dumb this sounds, b/c I know for some of you rocket ninja full stack gulping grunting vagrants, it’s gonna seem obvious…
The domain is https://pressily.com (so you’re with me, right? whew!)
I simply added a folder —> /l <— and stuck Mautic on https://pressily.com/l/ (notice the forward slash / and the lowercase letter --> L <— /l ?)
I’m guessing, wondering, hoping this’ll run right along side my WordPress installation.
Was that the wrong place to put Mautic?
Does it need to be in a sub.domain?
Thanks for the feedback folks!
(…this is what happens when a marketing & ecommerce idiot gets ahold of a new toy) HA!
Hi Brad,
I just remember having read, that a sub domain installation was recommended. And especially a sub directory was not. At least there were problems with sub directory installations, that people fixed by changing to root. However - I have the same installation - WordPress is in the root folder. Generally its not a bad idea to make use of sub domains.
As if that’s not fun enough, I’ve also got the site running through Cloudflare which is integrated on the server level through the hosting company.
ugh…
[h]Problem, question, concern, that I have with putting @Mautic on a sub.domain:[/h]
Site example = https://pressily.com (not much there, but image if Team TreeHouse & Lynda focused specifically on WordPress) and the Mautic instance is running at https://l.pressily.com (if you can’t see it too clearly, there’s a lower case ‘L’ as the sub.domain)
I need to set up various analytics to track both https://l.pressily.com and https://pressily.com right? which stinks!
Reason & Scenario: Imagine a landing page at https://l.pressily.com/awesome-landing-page Now, surely I’m going to want to track if that page converted or not, right? I don’t just have to track it in Mautic, I have to track it over on Twitter, Facebook, & Google Analytics as well. If the landing page did not convert or the lading page was not effective enough, I need to know that to determine which analytical data I need to setup next. Either a retargeting pixel, or another alternative, and how long to wait to activate the followup.
on and on I could go, but…
On one hand, I’m reading folks talking about NOT using a sub.domain, then on the other hand, I’ve got critical reason that I would need to NOT have it running via a sub.domain & simply have it mapped to a folder like https://pressily.com/l (notice I put the ‘L’ on the end)
Does anyone have any more solid, definitive, feedback on a correct setup? Thanks!
If you are running .htaccess with file & folder directives you will have issues running in a directory. For example I have .htaccess directives stripping .php and adding a closing brace / which propogates through the folder structure of a site.
If you have a good hosting company you can usually get shell access into your hosting account 1 level up from the public_html folder and here is where i usually create a new folder for sub domains and run custom versions of Wordpress based on composer.json from roots.io or Mautic in your case. ie mautic.mydomain.com & www.mydomain.com.
In answer to your analytics questions if you are using Google Tag manager you can set up cross domain tracking to merge 2 or more domains allowing you to track separate, top-level domains as a single entity. For a sub-domain it should not matter as both would be tracked anyways.
Right so @eurogroup first, thanks for the reply. Now, are you using Mautic 2.x versions or an earlier version?
I’ve got total access to the server all the way, so adding anything necessary is definitely an option.
While the suggestion for cross domain tracking is definitely an option I might have to do, the other concern that goes hand-in-hand with that is the advertising. Is it possible to setup (not really a word) “cross-domain” ad pixels? Well, sure! 
But, if the release of Mautic 2.x and beyond is ~indeed~ completely safe & functional & working in a same domain scenario, it’d be a HUGE benefit to get that confirmation before going through all the motions, taking up time, setting up landing pages, integrating tracking pixels, …and more.
Mautic 2.x+ Safe for same domain installation? I’m still wondering…