issue with header.inc.php 7.1 beta2 ?!

when ever I try and change $site['url']   = "http://MYSITE.COM/";  to

"http://www.MYSITE.COM/";

it seems to stop a lot of things from working like; login, template design link and lang link, forum block (home page), polls block and other things etc!

I have no idea what the issue could be ..... can anyone help please ??

And i assume you have cleared the cache after? Manually?

Are you running a caching system like memcache which takes a hour to clear.

Is DNS for www properly resolving?

 yes I cleared manually ...

Im not sure how to tell if memecache is in place ?

"Is DNS for www properly resolving?"  umm i'm not sure ... is there an exact way of telling this ?

Does not matter if memcache is installed on your system or not. Check dolphins cache settings and see what cache type your using. The default is file.

As for dns resolving www. well, if you have shell access to your server run nslookup www.yourdomain.com

ok cache is set to file

when using shell I got this response back:-

Non-authoritative answer:
Name:   www.MYSITE.COM
Address: DOMAIN IP

Looks like you are plagued with another mystery. Everytime i have done that same change i have never had a problem.

about 14 hrs ago I changed the domains IP ...... I think it's resolved now ... OR could this cause the issue with changing domain to www. even though the answer I got reported the correct new IP ?? :-

Non-authoritative answer:
Name:   www.MYSITE.COM
Address: DOMAIN IP

thanks for your time with this again :)

Yes. That could be the cause. There are hundreds or root DNS servers throughout the world, and billions of small ones ISP's run. So it takes a while for any changes in DNS to get through the entire system.

Although your server may be seeing the correct IP address, it may not be on every lookup, and your own machine at home that your browsing the site with may not be seeing consistent IP addresses either.

It normally can take up to 72 hours for any DNS changes such as that to filter through all of the DNS servers throughout the world.

OK ... and this would cause the site to break / buttons etc not to work when changing domain to WWW. in header.inc.php ?

 I'm just trying to make sure this is why I been through a day of hell OR if there could be other reasons.

Not sure. In all cases i have seen in the past. Either the site works or it does not. I have never seen dns cause a half working, half broken site before.

But as a test, maybe you should turn off dolphins caching to at least try and rule that out.

 hummm ... well with all the caches totally off and the www. change in header.inc.php the site works without issue !

put caches back on and the site buttons not working again!!  grrr

And with the caching on you have problems?

If so, then my theory that dolphins caching system really sucks has been proven right yet again.

Try one cache at a time and thoroughly test before moving to the next to see if you can determine exactly which option is the problem.

The option that is the worst is JS compression. I never run with it on. But thats not exactly caching either.

 yes with caching on the issues return !

it don't make sense .... :(

 Damn deano!!    I turned off JS cache and put all others ON and the site works perfect !

so what are the consequences of having it off full time ??

None. As far as i can tell this is a server issue. The server may have some form of compression in place already and when turning on the dolphin compression it results in damaged cache files. However it is just a theory. I have never been able to find that exact cause, but i did see a post once somewhere here where someones host told them the same thing.

Just run with it off. I do.

 OK i have now enabled all caches (even JS files) >> turned off this option 'Enable compression for JS/CSS files(cache must be enabled):'

and the site is working awesome :) thanks for helping me narrow this down Deano !

Your welcome.

You would not believe the number of problems i have seen in this forum that are fixed when turning off the the JS caching option. That option should really be off by default in dolphin, or simply removed. It is too much trouble.

WTFFF .. ok my above method as detailed in above post seemed to work BUT actually stopped action buttons working like fave etc !!

I have now put all caches ON except for 'Enable cache for JS files'

I have also Enabled compression for JS/CSS files ....

NOW the site / buttons appear to be fully working :) ........ I hope !

 
Ok. The option for Enable compression requires the option for JS caching be on. So which is it exactly?

If you have JS Caching disabled, then you also should have JS compression disabled as well.

You can have JS caching on with JS compression disabled, but not the other way around. So if JS caching is off then JS compression should be off as well. Hence the wording next to that option that says (cache must be enabled) which meens you don't use that option if the cache is not enabled.

I  find it hard to believe that 2 sites on the same server with same settings can have so many different problems from each other ...

I have 7.1 beta1 version with all same set up on same server  (EVEN WITH JS CACHE ENABLED) working fantastic and it's not had half of the issues I experienced with the second site 7.1 beta2

The screen shot below shows the settings that is allowing my site / buttons to work without issue:-

Shut off the compression as well. The option specifically states cache must be enabled. So because the cache is off, compression must be off also.

But i would like you to reverse them and try just the compression off. If that does not work, then both should be off.

 When I reversed it the main site buttons like 'add video' or 'template design' worked HOWEVER actions buttons when viewing videos etc did not work at all (dead)!

with the settings in screen shot >> it all works great ...

I have cache for JS files OFF and CSS files enabled so thought I should still  keep 'Enable compression for JS/CSS files(cache must be enabled)'  on ??

Hmm.  Perhaps you might be right considering the compression is one option for both. Ok. As long as it continues to work ok.