ProcessWire 3.0.65 core updates

ProcessWire 3.0.65

This week we have ProcessWire 3.0.65 on the dev branch. This version primarily focuses on bug fixes, covering issue reports from our issues repository on GitHub. While there weren't any major issues, we were able to cover quite a few items, so if you are following the dev branch it's worthwhile to grab this week's version.

ProcessWire 3.0.65 also upgrades the CKEditor version from 4.6.2 to 4.7.0. While it might look like there were several minor versions in between those two, there aren't. Version 4.7.0 is the version that follows 4.6.2. In my opinion, the most interesting additions in 4.7.0 were the addition of a Table Selection plugin that lets you “select and manipulate an arbitrary rectangular table fragment (a few cells, a row or a column)” and the new added support for pasting from Microsoft Excel. For a full list of changes, seek the CKEditor 4.7.0 release notes.

New multi-language URL field

A need that sometimes comes up on multi-language sites is to have a multi-language URL field. You might need to store URLs or link to URLs that are specific to the language the user is viewing your page in. Anywhere that multiple languages are involved, sooner or later you are going to need the ability to store different URLs for each language. We've not had this in the past, so your best bet was just to repurpose the existing multi-language text field. But now we've got a dedicated multi-language URL field available called FieldtypeURLLanguage, which provides a much better solution.

The multi-language URL fieldtype works essentially the same as the existing URL fieldtype. In fact, it extends the existing core URL fieldtype, so it shares all of the same features. But it also works the same as the existing multi-language text field, enabling you to use it (from the API side) exactly the same way that you use the FieldtypeTextLanguage field included with the core. Which is to say, it's very simple to use.

I decided not to add this as a core module since not everyone needs a multi-language URL field. Instead, I've released it as a module in our modules directory and on my GitHub account. Though if there's a strong need, we might always add it to the core later. I would also be interested in learning what other simple Fieldtypes you might find useful to have multi-language variations of.

I hope that you all have a great weekend and enjoy the ProcessWire Weekly. We'll see you back here next week, when we hope to make a little more progress on the page export/import features that we talked about last week.

Comments

  • soma

    soma

    • 2 years ago
    • 80
    Thanks for the new multilang url field. Much appreciated and always needed. What we also need is a multilanguage email field.
    • ryan

      ryan

      Actually I've already got it built, at the same time as the URL one. I hadn't released it because I couldn't think of a good enough use case for it. :) Glad to hear it would be worthwhile, I'll plan to release it next week.
  • Peter Verkooijen

    Peter Verkooijen

    • 2 years ago
    • 10
    OK, I guess it's on the regular download page...
  • juergen

    juergen

    • 2 years ago
    • 71
    What also comes to my mind is a multilanguage image field. Sometimes I need to upload 2 logos of a company because they have text in it. One logo for German and one logo for English. Same for banner or teaser images.
  • Lenz

    Lenz

    • 2 years ago
    • 40
    Thanks a lot for the multilanguage URL field. Very useful indeed. I would add to JUERGENs suggestion that in general multilanguage file fields (images, videos, pdfs etc) could come in handy. At least i have several use cases for it.
  • Mikel

    Mikel

    • 2 years ago
    • 20
    I second the need of a general multi language file field. Especially on product related sites, where you got pack shots in different languages, it has been a pain using a different file field for every language.
  • Peter Verkooijen

    Peter Verkooijen

    • 2 years ago
    • 00
    Where can I get these latest dev versions? I just downloaded and uploaded something from github.com/processwire/processwire, but it turns out to be the same 3.0.62 version I already had. Apologies for being noobish.
     

    NextProcessWire updates and new field types

    3

    This week we've got a new multi-language email field, a tutorial on how to use file/image files as multi-language fields, plus we introduce a new and unique ProFields module that's in the works. More 

    Twitter updates

    • We added WebP image support this year and many have been adopting it in existing projects. We look at a process used for migrating existing websites to WebP images— from preliminary considerations to implementation & testing, w/lots of tips & tricks too: More
      16 August 2019
    • Core version 3.0.137 on the dev branch adds the ability to hook multiple methods at once, in a single call. This post details how it works and provides a useful example of how you might put it to use in your development environment— More
      2 August 2019
    • ProcessWire 3.0.136 updates our CKEditor version and adds a new backtrace() method to the core Debug class— More
      26 July 2019

    Latest news

    • ProcessWire Weekly #276
      In the 276th issue of ProcessWire Weekly we're going to summarise the latest weekly update from Ryan, introduce a new third module called WireMail Mail Logger, and highlight a new site of the week. Read on!
      Weekly.pw / 24 August 2019
    • WebP images on an existing site
      In this post we’ll look at a process used for migrating an existing website to use WebP images. We’ll cover everything from preliminary considerations to implementation and testing, with lots of tips and tricks along the way.
      Blog / 16 August 2019
    • Subscribe to weekly ProcessWire news

    “We chose ProcessWire because of its excellent architecture, modular extensibility and the internal API. The CMS offers the necessary flexibility and performance for such a complex website like superbude.de. ProcessWire offers options that are only available for larger systems, such as Drupal, and allows a much slimmer development process.” —xport communication GmbH