npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

volto-multilingual-widget

v3.2.1

Published

A widget for Volto to insert values for any language enabled

Downloads

952

Readme

volto-multilingual-widget

A widget for Volto to insert values for any language enabled

To be used with mrs-developer, see Volto docs for further usage informations.

Usage

If you're using Volto < 12, then use v1.0.1

If you're using Volto < 16, then use v2.2.4

This is meant to be used on JSON or text fields, because it will send to the registry a string with a JSON inside.

In your Volto project, in src/config.js you can bind this widget for an id, example:

import { MultilingualWidget } from 'volto-multilingual-widget'

...

export const widgets = {
  ...defaultWidgets,
  id: {
    ...defaultWidgets.id,
    cookie_consent_configuration: MultilingualWidget(),
  },
}

Custom widget

If you see, you're not using the component directly, but you call as a function. The default widget used for the form is a rich text editor, which saves strings with html. As a parameter, you can pass a custom widget for language specific values, like:

import { MultilingualWidget } from 'volto-multilingual-widget'
import { ArrayWidget } from '@plone/volto/components';

...

const CustomWidget = ({ id, value, placeholder, onChange }) => (
  <input type="number" id={id} placeholder={placeholder} value={value} onChange={onChange} />
)
const defaultValue = []; // could be any, defaults to ''

export const widgets = {
  ...defaultWidgets,
  id: {
    ...defaultWidgets.id,
    news_type: MultilingualWidget(ArrayWidget, defaultValue),
    cookie_consent_configuration: MultilingualWidget(CustomWidget),
  },
}

If needed, you can pass a second argument for the default value for the custom widget.

Multilingual widget is agnostic about value types and handles the multilingual aspect more than data specific ones. So you could handle boolean or numeric values, which will be saved in a JSON as described below.

The only contrain about custom widget is based on the props, which are:

id (string) ID attribute of the widget element, bound to the label for accessibility reasons.

value (any) Language specific value.

placeholder (string) Placeholder text of the input

onChange (function) This is the method that will apply updates to the final JSON. Its firm is:

langValue => void

and you should pass directly the language specific value, so the type of the parameter should be the same as value one.

Results

What will be sent to Plone is in this format, with a key for any enabled language in your Plone site:

{
  "it": "<p>Il tuo testo in italiano</p>",
  "en": "<p>Your text in English</p>",
  "eo": "<p>Via esperanta teksto</p>"
}