GitLab

The link detection algorithm uses a depth-firsth traversal of links;
unfortunately, this can lead to connections being incorrectly omitted.
If a too-long pathway is encountered prior to a short one, the "seen"
check will omit it when it is encountered later.

While switching to breadth-first would resolve this more correctly,
simply tracking the depth that the link was found at is sufficient.

Also explain somewhat the rationale behind /^[a-z]/ rather that /_seq$/

For Classes, Groups and Users the Disabled column map entries was added with
fcec5ba already with the Status title.

as for Scrips

Also switch from h2 to h1 for parity with other Admin pages.

If you have many customfields this avoids scrolling to the bottom.
This also brings the customfields page in parity with users and groups.

This simplifies searching for queues and brings this in parity with the users
and groups filter.

If you have many queues this avoids scrolling to the bottom.
This also brings the queues page in parity with users and groups.

The input style (not only for type=text as showed the requestor but the
dropdowns too) is buggy on Firefox with weird round corners and general
look&feel.

Applying the "patch" fixes the issue and doesn't affect other browsers.
Additionally, remove the "-moz" and "-webkit" rules since the modern
browser releases don’t require them anymore, as they have all adopted
the oficial CSS3 syntax.

The fix in b6efaa8e removed caching and loaded a template
object, but the variable name $template used for the object
overwrote the initial $template variable which had the
template id/name. Rename to $template_obj.

  - There is no special handling for a "utc" context.

  - There is no default value for $context.

  - "UTC" may be still returned in cases where one of the server's and
    user's timezones is set.

This method is not a setter.

It causes warnings when an accessor is called on an unloaded Scrip

We pass NULL into the Date/IP parsing logic *before* we get to the check
which says "Oh, are you saying CF.{foo} IS NULL?  Then just left join to
OCFV and be done with it".  This causes warnings and errors in the logs
from trying to parse NULL as a Date or IP.  We did the right thing and
executed the LEFT JOIN anyway, but it caused a lot of noise.

 - Updated Lithuanian translation

 - "Content is an invalid IP address" has been renamed to
   "Content is not a valid IP address"

 - "Input can not be parsed as an IP address" has been dropped.

This reverts commit 40478732.

The CF object may not be readable without context.