It's correct that it complains, but if you check the LDR, it will now
have a default value and you can directly hit save again.
On 03.09.2018 10:04, Narcis Garcia wrote:
I've tested default framework in "Catalyst IT Ltd" demo, and it has same
behaviour: Without clicking in 000/LEADER field, it
What if the user types something there by mistake?
El 03/09/18 a les 15:09, Tomas Cohen Arazi ha escrit:
> Narcis, what you describe is the expected behaviour: you need to click
> on the field to get it filled. Not a bug, but the expected behaviour.
>
> El lun., 3 sept. 2018 a las 5:05, Narcis G
Narcis, what you describe is the expected behaviour: you need to click on
the field to get it filled. Not a bug, but the expected behaviour.
El lun., 3 sept. 2018 a las 5:05, Narcis Garcia ()
escribió:
> I've tested default framework in "Catalyst IT Ltd" demo, and it has same
> behaviour: Without
I've tested default framework in "Catalyst IT Ltd" demo, and it has same
behaviour: Without clicking in 000/LEADER field, it's not filled and
[Save] action complains about required value.
El 03/09/18 a les 08:00, Katrin Fischer ha escrit:
> Hi Narcis,
>
> if configured correctly Koha will not l
Hi Narcis,
if configured correctly Koha will not let you save the record without
filling in a default value. If it only does fill the LDR if you click in
the field, something is still not quite right in your configuration.
I suggest you try the behavior in one of the available demo databases
- No plugin icon; as far as I know the form icons.
- 000 is mandatory and 000@ is mandatory too; but it has effect only
when Visibility:Editor=Enabled
- When Visibility:Editor=Enabled it only populates a value on click.
When this is done, international characters have full expected behavior
(right
Hi Narcis,
000 should, if properly configured, auto-fill with a good value when
clicking into the input field or when trying to save the record for the
first time.
- Is there a plugin icon next to the 000 field?
- Is it mandatory?
- Does it populate when you click it?
If the LDR is there, ne
From: koha-ow...@lists.katipo.co.nz
"Your message to Koha awaits moderator approval"
"Message body is too big: 61980 bytes with a limit of 40 KB"
I'm still waiting for somebody releases that my previous post to the
list. I had to format it in HTML to present some SQL table properties.
Thank you
Hi Narics,
try the following:
In your MARC framework, make the LDR 000 @ visible in the editor again.
Open the record, make sure the field is filled, save it. The plugin
linked to the LDR should take care of setting some sensible default
value just by clicking into the field. Try to view the
Hi
> Didn't see the "El halcon Maltš" example?
Do you mean the following that you have sent only to Katrin Fischer?
SELECT * FROM koha_biblio.biblio WHERE biblionumber = 2;
+--+---+--+---+--+---++-+-
Didn't see the "El halcon Maltš" example?
As "Koha web interface" I meant both OPAC and staff area.
El 24/08/18 a les 18:24, Michael Kuhn ha escrit:
> Hi Narcis
>
> You wrote:
>
>> When cataloguing books with non-english characters, I see well saved
>> strings at database (from OS console), bu
Hi Narcis
You wrote:
> When cataloguing books with non-english characters, I see well saved
> strings at database (from OS console), but Koha web interface is not
> showing those unicode characters as expected.
What exactly is shown? Can you give some examples?
What do you exactly mean with "K
Recorded "El Halcon Maltés" is presented as "El halcon Maltš"
Bad viewed with tested browsers:
M. Firefox: UTF-8 (no luck switching to central european ISO / Windows)
Gnu Icecat: UTF-8 (no luck switching to central european ISO / Windows)
Midori: Unicode (no luck switching to UTF-8 / ISO-8859-1)
E
Hi Narcis
You wrote:
> When cataloguing books with non-english characters, I see well saved
> strings at database (from OS console), but Koha web interface is not
> showing those unicode characters as expected.
>
> MariaDB works with character set utf8mb4
> Apache works with charset UTF-8
> All
cher ha escrit:
>
> Hi,
>
> how did you catalog them? Did you use a standard or a modified
> framework? Z39.50/SRU? Can you show us the MARC of your record?
>
> Hope this helps,
>
> Katrin
>
> *Gesendet:* Donnerstag,
When cataloguing books with non-english characters, I see well saved
strings at database (from OS console), but Koha web interface is not
showing those unicode characters as expected.
MariaDB works with character set utf8mb4
Apache works with charset UTF-8
All Koha database tables have collarion u
16 matches
Mail list logo