-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I’ve noticed that if I login on RT from a mobile (in this case,
android), it goes into mobile mode as expected, but only after logging in.
It would be nice to have a mobile login page, too.
Is this something missing or do I need to activate it separately?
Thanks,
Giuseppe
Giuseppe Sollazzo
Senior Systems Analyst
Computing Services
Information Services
St. George’s, University Of London
Cranmer Terrace
London SW17 0RE
Email: gsollazz@sgul.ac.uk
Direct Dial: +44 20 8725 5160
Fax: +44 20 8725 3583
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOuqizAAoJEAqigArPBfJXkvUH/Ap7SQKyBvkXVbfz5FrZ9/uM
E+DfvQ/fepnC4Zwrc73678EIfrHlqdD1c8Q/zgdERPfkU4YaGMAoIMxMv96Y91Sn
Jrl2RJFFWtdpP9PY0y9ziI/FgmdP8eNJ0EA6QkD+eV+povaZbxmAjv5vfDAx/RYi
2dKmJN+zsgci745IHdW6tSm9Tf/iG689ky3bqLFX8vXTj2ww64d5kGWr5JbZqJbn
C9wKJwgbD9fEaH2co4J1buCnhXBfxUU+hMdO7O+uL+VAtfKfbFHrEDMoq/7TzrER
9aCpn5bYgOnJuKnrppgH592t0lSQbkqb/Uot9CyzsfFKBCx3JM0ttMOifCFsvhg=
=2aDO
-----END PGP SIGNATURE-----
I’ve noticed that if I login on RT from a mobile (in this case,
android), it goes into mobile mode as expected, but only after logging in.
It would be nice to have a mobile login page, too.
Is this something missing or do I need to activate it separately?
There’s a bug in the 4.0 series that sends you to the normal login
page instead of a mobile page. In 4.0.2 and later we serve a lot less JS
on that page, so it should be better. It turned out to be a complex
issue, so there is no fix yet (ticket 16809).
-kevin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Kevin,
thanks for your reply.
Do you think that moving to 4.0.2 will sort it?
Thanks,
GiuseppeOn 09/11/11 16:47, Kevin Falcone wrote:
On Wed, Nov 09, 2011 at 04:22:11PM +0000, Giuseppe Sollazzo wrote:
I’ve noticed that if I login on RT from a mobile (in this case,
android), it goes into mobile mode as expected, but only after
logging in. It would be nice to have a mobile login page, too.
Is this something missing or do I need to activate it
separately?
There’s a bug in the 4.0 series that sends you to the normal login
page instead of a mobile page. In 4.0.2 and later we serve a lot
less JS on that page, so it should be better. It turned out to be a
complex issue, so there is no fix yet (ticket 16809).
-kevin
-------- RT Training Sessions
(http://bestpractical.com/services/training.html) * Barcelona,
Spain ? November 28 & 29, 2011
Giuseppe Sollazzo
Senior Systems Analyst
Computing Services
Information Services
St. George’s, University Of London
Cranmer Terrace
London SW17 0RE
Email: gsollazz@sgul.ac.uk
Direct Dial: +44 20 8725 5160
Fax: +44 20 8725 3583
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOurKiAAoJEAqigArPBfJXRaoIAI7LBZEfeBBn2a/pFzLgTw7i
50OA66jzkkjPdJnwtimKtLz4m+XCvhrXAwPvg/0tsYfXzPk9wR7Crykpl92tO9Ks
Snxk95PcDRf6RoDyk12280fx8Jr7kd4MUw5D/chboC+QGBHlO9kPYn1b83O6ScNa
Z6J+WsjWhxkje/TnpTu7EWqoh4BVFr5Kd5JvVN4PJsbFWlOM3p3UmFmeOs9c9/5t
tQr8Y6yiRR7vsg3W4hUUZ+1uh3zf5KLGTvyYYi7RMBEgraiiy2I59yztBhrH797x
Uk8Mv52iZZWhXlZGlNIKOUyvfL/DndtFBMjRPGOULHVWiKRSlbJ0WhFVkDPSVB8=
=o1bO
-----END PGP SIGNATURE-----
Hi Kevin,
thanks for your reply.
Do you think that moving to 4.0.2 will sort it?
I’m not sure what version you have, and I also don’t know what you
mean by sort it. You will not get a mobile login page in 4.0.2 or
4.0.3, you will get a lighter login page however.
You can view the bug in our bug tracker if you want to see what it
covers.
-kevin> On 09/11/11 16:47, Kevin Falcone wrote:
On Wed, Nov 09, 2011 at 04:22:11PM +0000, Giuseppe Sollazzo wrote:
I’ve noticed that if I login on RT from a mobile (in this case,
android), it goes into mobile mode as expected, but only after
logging in. It would be nice to have a mobile login page, too.
Is this something missing or do I need to activate it
separately?
There’s a bug in the 4.0 series that sends you to the normal login
page instead of a mobile page. In 4.0.2 and later we serve a lot
less JS on that page, so it should be better. It turned out to be a
complex issue, so there is no fix yet (ticket 16809).