DHIS 2.30 is displaying some icons and buttons with corrupted characters

I have installed DHIS2 2.30 on tomcat 9 with PostgreSQL. I have a problem with the display.

For example, when I go to ‘Maintenance’, the button for ‘Add’ and ‘List’ are not showing right. They are showing corrupted characters. The same thing is happening on that page with the ‘Metadata group editor’ icon at the top right.

When I go to the demo site, the display is correct. How can I fix this?

enter image description here

Maximum number of options when selected via next and previous buttons?

I’m designing a product that has customizable features. The user can customize a light color by pushing a forward (>) or back (<) button. This action will toggle through a set color palette that will loop back once they reach the end.

I’m setting it up so that holding either button (< or >) will jog more quickly through the color options, but assuming the user is unaware that holding the buttons will run through them quicker…

And regardless of how many colors a user can distinguish or even needs…

How many options (aka. button presses) is enough before the user gets frustrated by toggling through them all? Any experience or studies to support this?

It’s safe to assume that toggling through 3 colors would not be annoying. However, toggling through 1,000 colors could be. I’m wondering if there’s some “sweet spot” in between.


To clarify these are physical buttons on a physical product.

Where to put what type of save and cancel buttons on a mobile site?

We are making a responsive website. There is a form on the site and I am not sure what type of save and cancel buttons to use where. I have found several patterns as you can see in the picture with the following variables: – Position of buttons (top/bottom, horizontal/vertical) – Autosave/Save button – Type of top buttons (text/icons)

Action buttons input form mobile site

Which solution is best practice?

Users usually fill out the form top to bottom (in this case) which would support buttons at the bottom, but convention might rather speak for the top buttons. Or do the top buttons rather belong to (native) app navigation and not to mobile site navigation? The battle for screen estate would speak for horizontal button positioning (cancel next to save), but supporting left handed people would speak for the vertical positioning. Maybe the cancel button can be even left out and the cross at the top or back button would cover this function sufficiently?

Social Media Sharing Buttons concerning the Chinese Great Firewall

We are about to build a multi-regional website that targets users in China and other places. However, a concern was raised about the use of social media sharing buttons. Since China blocks common social media websites like Facebook and Twitter, we fear that showing buttons with their icons on them will cause China to block our site. However, we do want to allow users from other countries to share our website to these social media websites.

So the questions are:

  1. Will these social media buttons cause our site to be banned in China?
  2. If they are not banned, will they affect rankings in search engines?
  3. If the localised version (zh-hans) does not have these buttons, will it helps? However, the homepage in default language (which is not Chinese) will still have them.
  4. Will there be a difference to use sub-directories or sub-domains for different languages, since sub-domains are usually viewed as a different site?

Any suggestions are welcome.