aboutsummaryrefslogtreecommitdiffstats
path: root/view
diff options
context:
space:
mode:
authorredmatrix <redmatrix@redmatrix.me>2015-10-29 01:23:56 -0700
committerredmatrix <redmatrix@redmatrix.me>2015-10-29 01:23:56 -0700
commit96402a235482af73c9c958ad9b1cf629d0bfb8cb (patch)
treeceb22fd24e8abeb8026d84eeb1a94b7c4c4188ed /view
parent4fec7aa991e0afe63a47722a7186e6fd2058d20a (diff)
downloadvolse-hubzilla-96402a235482af73c9c958ad9b1cf629d0bfb8cb.tar.gz
volse-hubzilla-96402a235482af73c9c958ad9b1cf629d0bfb8cb.tar.bz2
volse-hubzilla-96402a235482af73c9c958ad9b1cf629d0bfb8cb.zip
This may take a few iterations to discover the best way to present the information, but we need a way for members to know what alternate locations are available for a channel during times of server issues - and as recently discovered if there aren't any hublocs at all; without digging around the database and probing channels and other messy stuff.
Diffstat (limited to 'view')
-rwxr-xr-xview/tpl/abook_edit.tpl7
1 files changed, 6 insertions, 1 deletions
diff --git a/view/tpl/abook_edit.tpl b/view/tpl/abook_edit.tpl
index 0a7cf2d4d..1ed3baafa 100755
--- a/view/tpl/abook_edit.tpl
+++ b/view/tpl/abook_edit.tpl
@@ -33,8 +33,13 @@
{{/foreach}}
<div class="section-content-info-wrapper">
<div>
- {{$addr_text}} <strong>'{{$addr}}'</strong>
+ {{$addr_text}} <strong>'{{$addr}}'</strong>
</div>
+ {{if $locstr}}
+ <div>
+ {{$loc_text}} {{$locstr}}
+ </div>
+ {{/if}}
{{if $last_update}}
<div>
{{$lastupdtext}} {{$last_update}}