Wedge

Public area => Bug reports => The Pub => Archived fixes => Topic started by: live627 on April 30th, 2012, 07:27 AM

Title: New indicator isn't showing in wireless mode
Post by: live627 on April 30th, 2012, 07:27 AM
New indicator isn't showing in wireless mode in the display template.
Title: Re: New indicator isn't showing in wireless mode
Post by: Nao on April 30th, 2012, 08:13 AM
As desired actually :)
Although I can perfectly be convinced that it's important enough to be retained!
Title: Re: New indicator isn't showing in wireless mode
Post by: Arantor on April 30th, 2012, 02:40 PM
I'd argue it should be there as it is quite important information.
Title: Re: New indicator isn't showing in wireless mode
Post by: Pentaxian on April 30th, 2012, 09:57 PM
On my iPad all the messages look like in this quote of the last message here. They include this notice.

Sorry if this is the wrong place to report it but is the simplest way to do it.

Today at 02:40 PM
Notice: Undefined index: actions_button in /Themes/default/Display.template.php on line 407
 
 Arantor
Wedgeward
I'd argue it should be there as it is quite important information.
Title: Re: New indicator isn't showing in wireless mode
Post by: Arantor on April 30th, 2012, 10:01 PM
I edited the post to remove full paths; while it's not likely to be a major deal, we do prefer it strongly if people only paste the relevant parts of paths.

It is very likely that Nao is currently work on it hence the errors.
Title: Re: New indicator isn't showing in wireless mode
Post by: Nao on May 1st, 2012, 08:25 AM
I was completely cut off from the Net at 5PM, while doing some heavy refactoring on the display template and some scripts. I phoned my ISP at 6PM, they said they were working on it...  Then at 7PM again, they said someone was dispatched to the DSLAM and would fix some broken hardware. At 1AM it was still down and I went to bed.
Only got it back up this morning -- which allowed me to finally upload my updated language files, eh...

I was still able to work on Wedge, but had to cope with swfobject not being definable as a local file so I got plenty of timeouts on that one each time I was looking at an Aeva-powered page...