Toolset 1.6.19 – OpenStreetMap Integration Is Here!

   Kathy Banach

Announcements

April 2, 2025
19

Toolset 1.6.19 is here, bringing long-awaited support for OpenStreetMap, behind-the-scenes improvements to the Maps block, and a range of compatibility updates and bug fixes across Toolset plugins.

Build with OpenStreetMap and Enjoy a Faster Map Block

One of the most requested features is now available in Toolset Maps 2.2.0: full integration with OpenStreetMap. You can create fully interactive maps without relying on API keys or paid subscriptions.

Selecting OpenStreetMap in Toolset Settings
OpenStreetMap added with Toolset Map block

But that’s not all. Behind the scenes, we’ve moved the Map block entirely to JavaScript, cutting down on backend calls and eliminating the lag you may have felt when making updates. Now, the interface is faster, and you’ll see previews instantly as you build. 

If you’re working with Azure Maps, you’ll notice that we fixed some glitches, too. Marker dialogs now stay inside the map view, and markers load at exactly the right moment, so everything looks and works just as it should.

Improved Multilingual Workflows with WPML

If you’re using WPML, you’ll notice smoother integration all around.

You no longer need to jump between different screens. The Translation Management Dashboard is now your central hub for sending all Toolset-related content for translation—including custom post types and their labels, taxonomy labels, relationships, and field groups.

Just go to WPML → Translation Management, find the section with what you want to translate (like labels or field groups), select the items, and send them for translation. 

That’s it—quick and straightforward.

Toolset 1.6.19 also adds full support for WPML’s revamped Advanced Translation Editor, which now mirrors the structure of the WordPress editor. This makes it easier to translate complex, structured content with familiar labels and layout.

Expanded Label Support for Custom Post Types and Taxonomies

Toolset Types 3.6.0  gives you even more ways to fine-tune how your custom content appears in the WordPress admin.

When you register custom post types or taxonomies, you can now customize a broader set of labels—covering everything WordPress supports up to version 5.8. This includes newer labels like the message shown after publishing an item. 

For example, you can change “Add Book” to something more relevant, like “Submit a Bestseller”.

Customized label for adding a new item

With this new support in Toolset, messages feel more tailored and intuitive for the type of content you’re managing.

General Improvements and Fixes

Alongside the major updates, Toolset 1.6.19 includes a range of smaller fixes and enhancements to improve your day-to-day work.

In Toolset Views and Blocks, Button blocks show their icons properly, and Image blocks linking to Lightbox work properly inside AJAX-paginated Views.

You’ll also benefit from improved compatibility with PHP 8.2 and 8.3, so you’re ready for the latest server environments.

For other fixes and plugin-specific changes, check out the full changelogs:

Toolset Maps 2.2.0

See the changelog

Toolset Types 3.6.0

See the changelog

Toolset Views 3.6.19

See the changelog

Toolset Blocks 1.6.19

See the changelog

Toolset Forms 2.6.23

See the changelog

Toolset Layouts 2.6.17

See the changelog

Ready to Update to Toolset 1.6.19?

As always, we’re rolling out plugin updates gradually—but you already know the drill. If you want to try the new features right away:

  1.  Go to Plugins → Add New Plugin and click the Commercial tab
  2. Click to Check for updates
  3. The latest Toolset plugins will appear on the list and you can update your site to them

It can take up to 24 hours for the updates to reach all sites. If you don’t see them on your site, try a bit later.

In the meantime, we’d love to hear from you:

Feel free to share your thoughts in the comments!

 

Comments 19 Responses

  1. The update to add OpenStreetMaps is absolutely great. The cost of the Google Maps API was getting out of hand and I was just thinking about removing a lot of the maps. But with this update, I will just be able to replace it with OpenStreetMaps!

    Reply

    • Thanks for the kind words, Tim. We’re so glad to hear this update came at the perfect time for you!

      Reply

  2. WOW!!!

    This is amazing news!!

    Just this morning, I was working on a custom OpenStreetMap integration!

    The best part is seeing Toolset alive and finally getting new features. The Toolset fans community has been struggling for a long time, thinking it was all over. Knowing that there is an intention to move forward and improve Toolset is truly fantastic news!

    Thank you!

    Reply

    • We really appreciate your feedback, Umberto. It’s good to know the update was helpful and even better that it landed when you needed it!

      Reply

  4. Ahhh, your update absolutely made my morning! 🌞✨

    I was just working on a custom OpenStreetMap integration — and then I read this fantastic news! It feels like Toolset is finally coming back to life after a long silence. Like a favorite band you thought had broken up for good, and suddenly — surprise comeback with a brand-new album! 🎉

    The Toolset community clearly held on for a long time, often with the sinking feeling that this brilliant application might be gone for good. And now? There’s movement again, new features, and a real sense of direction. It’s honestly such a relief — and above all, it brings real joy!

    Thanks also for the OpenStreetMap integration! 🎯 That timing couldn’t have been better — it almost feels like Toolset never took a break at all. 🚀

    Thank you so, so much for this positive turn. It’s truly amazing to see things moving forward — and in such a great way! 🙏

    ¡Pura vida, and keep it up!

    Reply

  5. What updates are you hoping to see next?
    Toolset dealing with Elementor PRO specifically displaying Template Layouts with dynamic content (frankly I’m still struggeling much which module to use – Blocks or Views or both?)

    Reply

    • Thanks for the feedback! We’ll pass this on to the team and see what we can do to make things clearer.

      Reply

    • Hi there,

      About five years ago, I went through a very similar struggle—tried almost every popular page builder out there, spent hundreds of dollars, and still felt like I was patching things together rather than building with clarity. That’s when I cautiously started exploring Gutenberg Blocks. It was still in its early stages and, honestly, quite frustrating at first—tight layouts, unintuitive interfaces, and a lot of trial and error.

      Back then, there was even a forum thread asking whether page builders would ever be replaced by Gutenberg. I confidently replied, “No way!”—thinking page builders were here to stay. Funny how things change! I’m now fully invested in Blocks, and I’ve never looked back.

      The key turning point for me was finding the right theme and block plugin combination. After extensive research, I settled on Blocksy for its lightweight, performance-first philosophy and unmatched design flexibility. To complement it, I found Stackable Blocks, and the integration between the two is simply seamless.

      So now, I run Blocksy + Stackable (Pro versions) as my go-to setup. I made the lifetime investment, and I can confidently say—it’s been the best decision in my WordPress journey. No bloat, no unnecessary layering, no plugin conflicts. Just native WordPress, running fast and clean.

      In terms of Elementor Pro, or any other page builder—honestly, I moved away from them. Elementor is powerful, no doubt, but adds a heavy footprint and complexity I no longer want to manage.

      That said, I still continue to use Toolset — just not for visual layout building with Elementor. Instead, I use Toolset where it truly shines: for advanced data relationships, custom post types, repeatable field groups, conditional logic, and dynamic content filtering. When the requirements go beyond what Blocks alone can handle — Toolset steps in perfectly. But for most layout and dynamic content needs, Blocks (especially when paired with a good block plugin like Stackable, Kadence Blocks, or GenerateBlocks) are more than sufficient.

      So to answer your question:

      For layout: I prefer Blocks (Blocksy + Stackable)

      For advanced dynamic and structured content: I still rely on Toolset Views and Blocks, depending on the use case

      And yes—Blocks are the future, simply because they are now part of WordPress Core and are evolving with every major update.

      Just my two cents, but I hope this gives you some perspective and saves you the same struggle I went through.

      Cheers!
      Alok Sharma

      Reply

  6. Oh my!

    What an amazing thing to hear!
    Keep up the good work guys!

    I hope we can get some work done on the bugs that piled over the months and are plaguing the support of current Toolset blocks with current WordPress versions.

    Keep it up, we’re still here and paying those subscription dollars!

    Reply

    • Hi Jim! You can simply switch to OpenStreetMap in Toolset > Settings. Your Toolset Map block will switch the rendering to use OSM tiles.

      Reply

  11. This is absolutely fantastic news!

    As someone who strictly follows a privacy-first philosophy, I’ve always wanted to move away from Google Maps and its data-heavy, privacy-intrusive model. The addition of OpenStreetMap support in Toolset Maps 2.2.0 is a huge step in the right direction, and I really appreciate the team listening to the community on this long-requested feature.

    No API keys, no subscriptions, no strings attached — just fast, open-source, and privacy-respecting maps. Exactly what many of us have been waiting for!

    Also, kudos for moving the Map block entirely to JavaScript. The performance improvements are noticeable, and the instant previews make the workflow feel so much smoother.

    Toolset just keeps getting better. Thank you for making it easier to build powerful, ethical, and modern WordPress sites.

    Reply

Leave a Reply  

Please leave here comments about this page only.
For technical support and feature suggestions, head to our forum. We are waiting there!

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>