1 tilqicom Feb 16, 2012 00:58
3 tilqicom Feb 16, 2012 01:29
sam2kb wrote:
1. It shouldn't, I will check it.
2. The code is okMaybe we should add a shedload of classes to the <body> tag according to language, browser/system, post type, category etc. Just like WP does it.
It would allow users to add precise CSS styles
Well as long as the detection is precise (:..
i guess it would do more good than the slight hurt it might do.Adding classes to body is a very good idea if you ask me.
4 tilqicom Feb 16, 2012 01:34
Well, oddly enough, it doesnt always do that. For one blog its correct but for the other its not, despite the fact that they both use the same skin.
[url=http://postimage.org/]http://s14.postimage.org/o5vptseep/sse_Untitled_8.jpg[/url]
5 sam2kb Feb 16, 2012 02:03
'chrome' option was added not so long ago. Is the version with 'msie' outdated?
6 tilqicom Feb 16, 2012 02:08
sam2kb wrote:
'chrome' option was added not so long ago. Is the version with 'msie' outdated?
version of what ? they are basically exactly same, same skin, same install of b2
7 sam2kb Feb 16, 2012 15:07
I thought you are talking about different b2evo instances. I'll check it
8 tilqicom Feb 18, 2012 04:16
Ok, so i have just upgraded to 4.2.0 beta (from cvs) and it seems the detection got only worse.
I used to have no problems in firefox, but now, 1 of my blogs out of 10 is recognized as msIE.
Should we consider this as a bug ?
9 sam2kb Feb 18, 2012 06:33
I wrote you somewhere already that CVS is extremely outdated. We dropped it in favor of private SVN, the code will be released to the public after b2evo 5 is out.
I hope you have a backup. Wait a couple more days for official 4.1.3 very stable! release.
10 tilqicom Feb 18, 2012 10:52
sam2kb wrote:
I wrote you somewhere already that CVS is extremely outdated. We dropped it in favor of private SVN, the code will be released to the public after b2evo 5 is out.
I hope you have a backup. Wait a couple more days for official 4.1.3 very stable! release.
Pfft.I have already updated |: Should i roll back to 4.0.5 from yesterday's backup ? is it that bad ?
How come 4.2.0 beta is "outdated" compared to an upcoming 4.1.3 ?
11 tilqicom Feb 18, 2012 13:20
Anyway, here is an update, i have rolled back to 4.0.5 and upgraded to 4.1.3 version you have sent me the other day via pm.
There has been some minor problems here and there but it all seems ok for now.
12 sam2kb Feb 18, 2012 16:27
How come 4.2.0 beta is "outdated" compared to an upcoming 4.1.3 ?
v4.2.0 was transformed into v5 long time ago. CVS is dead, nobody updates it.
Should we address those minor problems in the next 4.1 version?
13 sam2kb Feb 25, 2012 15:30
How does Hit:detect_useragent() work in 4.1.3, is there still a problem with chrome?
14 tilqicom Feb 25, 2012 16:20
sam2kb wrote:
How does Hit:detect_useragent() work in 4.1.3, is there still a problem with chrome?
Nope, everything seems ok in chrome with 4.1.3
15 sam2kb Feb 26, 2012 09:37
Ok cool :)
1. It shouldn't, I will check it.
2. The code is ok
Maybe we should add a shedload of classes to the <body> tag according to language, browser/system, post type, category etc. Just like WP does it.
It would allow users to add precise CSS styles