Just name it "fields" not "userfields" for custom objects (references #242)

This commit is contained in:
Bernd Bestel 2019-09-18 16:25:38 +02:00
parent 096fb7a116
commit 2522b3748c
No known key found for this signature in database
GPG Key ID: 71BD34C0D4891300
3 changed files with 5 additions and 2 deletions

View File

@ -1450,3 +1450,6 @@ msgstr ""
msgid "For example"
msgstr ""
msgid "Configure fields"
msgstr ""

View File

@ -44,7 +44,7 @@
<i class="fas fa-trash"></i>
</a>
<a class="btn btn-secondary btn-sm" href="{{ $U('/userfields?entity=userentity-') }}{{ $userentity->name }}">
<i class="fas fa-th-list"></i> {{ $__t('Configure userfields') }}
<i class="fas fa-th-list"></i> {{ $__t('Configure fields') }}
</a>
</td>
<td>

View File

@ -13,7 +13,7 @@
<i class="fas fa-plus"></i>&nbsp;{{ $__t('Add') }}
</a>
<a class="btn btn-outline-secondary" href="{{ $U('/userfields?entity=' . 'userentity-' . $userentity->name) }}">
<i class="fas fa-sliders-h"></i>&nbsp;{{ $__t('Configure userfields') }}
<i class="fas fa-sliders-h"></i>&nbsp;{{ $__t('Configure fields') }}
</a>
</h1>
<h5 class="text-muted">{{ $userentity->description }}</h5>