The next big version of Ultimate Fields is in development and will probably get released in the fall. Version 3 (2 was 99% ready, but I decided to skip it) brings tons of changes even on top of 2, but this is a topic for another article.

One of those changes will be the removal of qTranslate support. I am aware that many users choose Ultimate Fields because of this feature, however at the time of writing this article qTranslate has been long gone and qTranslate X is not being maintained anymore.

When Ultimate Fields 1 was released, qTranslate was a very popular plugin and even I was using it for most of my projects. Since then I came to the conclusion that there are too many things, which are problematic about the one field-multiple values approach. That, combined with the fact that qTranslate X is not really being supported led me to this decision.

If you are using Ultimate Fields in combination with qTranslate X at the moment, please write a comment below this article to describe what types of multilingual fields you are using.

If enough people request it, I will probably try to implement some limited multilingual functionality (no conditional logic, no repeatable fields, no required fields) in order not to break any websites.

Through the past year I’ve been working on Ultimate Fields 2, the next version of Ultimate Fields, my plugin for custom fields throughout the WordPress backend. At this point there are many open tasks, but there is a lot that is already done, so I feel ready to share some if it with the world.

Let’s start the game!

After a triple-digit number of websites I worked on during the last few years, I finally get to have one on my own. At least one that is online and consists of something else, rather than a “Coming soon…” screen. Continue reading “Hello, World!”