You are not logged in.
Here is the TXP Tip covering this topic.
Let me know if you find any glaring errors within it.
Offline
Added a little comment what does symlink means – i think now it’s pretty clear to understand.
Providing help in hacking ATM! Come to courses and don’t forget to bring us notebook and hammer! What for notebook? What a kind of hacker you are without notebok?
Offline
Thanks Phil, Victor, everybody, I’ve caught the speed bug too! This looks like another great addition to the txp speed up tips! After getting it all working, I posted a comment on TXPTIPS, Phil, using Victor’s symbolic link method instead of DocumentRoot and also using rvm_css. Just one other thing not mentioned: I can no longer use <txp:site_url /> to point to folders on subdomains, so I use <txp:output form form="speedurl" /> now. Perhaps there’s a better way?
TXPQ Examples and discussion of Textpattern CMS quality.
Offline
I noticed in .htaccess there’s a line: #Options +FollowSymLinks. Does this need to be uncommented, what difference does it make? It is still commented in mine and everything is working.
There’s also this line: #Options -Indexes ?
TXPQ Examples and discussion of Textpattern CMS quality.
Offline
wet wrote:
maniqui wrote:
Regarding the cookieless subdomain trick, i think it’s only possible if you server static assets from a totally different domain name.
Depends.
If you set cookies using a cookie domain of
.example.com(note the leading dot), all subdomains ofexample.comwould share this cookie. OTOH, if you usedexample.com(no leading dot) as the cookie domain, it would only be used on this particular host.
I interpret Googles instructions for disabling cookies in sub domains somewhat differently to wet but I could be wrong and hence this post. I think that the instructions indicate that an entry of example.com (i.e. no leading dot) would have the browser automatically add it back in to make tracking (and cookie setting) available in top level sub domains like sub1.example.com and sub2.example.com. Physically including the dot i.e. .example.com also makes tracking (and cookie setting) available in lower level sub domains like sub1.sub1.example.com and sub2.sub1.example.com. To achieve non tracking of a sub domain (and no cookie setting) one needs to be specific and add a ‘none’ setting i.e _gaq.push(['_setDomainName', 'none']); . I admit that seems counter intuitive if one wants to retain Google tracking of the main domain example.com and so am a quivering mass of uncertainty.
Last edited by joebaich (2010-11-13 18:00:33)
Offline
@joebaich
I can confirm that _gaq.push(['_setDomainName', 'none']); works for avoiding the cookie to be set on all other domain’s host (aka subdomain).
Offline
Anyone know how to fix Piwik so it doesn’t set cookies on subdomains?
Offline