# Release Notes: 2.6

## Improvements

- Added documentation for PRO integration with MultilingualPress ([#2699](https://github.com/GatoGraphQL/GatoGraphQL/pull/2699))
- Added documentation for new PRO field `_strRegexFindMatches` ([#2708](https://github.com/GatoGraphQL/GatoGraphQL/pull/2708))
- Added GraphQL variables `$translateFromLanguage`, `$includeLanguagesToTranslate` and `$excludeLanguagesToTranslate` to persisted queries ([#2694](https://github.com/GatoGraphQL/GatoGraphQL/pull/2694) / [#2700](https://github.com/GatoGraphQL/GatoGraphQL/pull/2700)):
  - [PRO] Translate posts for Polylang (Gutenberg)
- Added scalar types to the GraphQL schema:
  - `IntValueJSONObject` ([#2703](https://github.com/GatoGraphQL/GatoGraphQL/pull/2703))
  - `IDValueJSONObject` ([#2704](https://github.com/GatoGraphQL/GatoGraphQL/pull/2704))
- Added predefined persisted queries:
  - [PRO] Translate posts for MultilingualPress (Gutenberg) ([#2706](https://github.com/GatoGraphQL/GatoGraphQL/pull/2706))
  - [PRO] Translate posts for MultilingualPress (Classic editor) ([#2706](https://github.com/GatoGraphQL/GatoGraphQL/pull/2706))
  - [PRO] Translate Poedit file content ([#2709](https://github.com/GatoGraphQL/GatoGraphQL/pull/2709))
- Added Gato GraphQL intro video to documentation (Classic editor) ([#2707](https://github.com/GatoGraphQL/GatoGraphQL/pull/2707))

### Added `siteURL` field ([#2697](https://github.com/GatoGraphQL/GatoGraphQL/pull/2697))

Added the following field to the GraphQL schema, via the "Site" module:

- `Root.siteURL`

For instance, executing the following query:

```graphql
{
  siteURL
}
```

...will produce:

```json
{
  "data": {
    "siteURL": "https://mysite.com"
  }
}
```

### Added fields to fetch multisite data ([#2698](https://github.com/GatoGraphQL/GatoGraphQL/pull/2698))

The GraphQL schema now supports fetching data from a WordPress multisite network, provided via the new "Multisite" module.

This module adds the following fields to the GraphQL schema:

- `Root.networkSites`
- `Root.networkSiteCount`

Field `networkSites` returns an array with all the sites in the network, each of the new `NetworkSite` type, which contains the following fields:

- `id`
- `name`
- `url`
- `locale`
- `language`

These fields are only enabled when multisite is enabled (i.e. when method `is_multisite()` returns `true`).

For instance, executing the following query:

```graphql
{
  networkSiteCount
  networkSites {
    id
    name
    url
    locale
    language
  }
}
```

might return:

```json
{
  "data": {
    "networkSiteCount": 3,
    "networkSites": [
      {
        "id": 1,
        "name": "Site in English",
        "url": "https://mymultisite.com",
        "locale": "en_US",
        "language": "en"
      },
      {
        "id": 2,
        "name": "Site in Spanish",
        "url": "https://es.mymultisite.com",
        "locale": "es_AR",
        "language": "es"
      },
      {
        "id": 3,
        "name": "Site in French",
        "url": "https://fr.mymultisite.com",
        "locale": "fr_FR",
        "language": "fr"
      }
    ]
  }
}
```

## Fixed

- Identifying extension in `createMediaItem` when filename has more then one dot

## [PRO] Improvements

- [PRO] Added input `valueWhenNonExistingKeyOrPath` to field `_objectProperty`
- Added automation rules:
  - MultilingualPress: When publishing a post, translate it to all languages (Gutenberg)
  - MultilingualPress: When publishing a post, translate it to all languages (Classic editor)

### Added integration with MultilingualPress

Gato GraphQL PRO now has an integration with the [MultilingualPress](https://multilingualpress.org/) plugin.

The GraphQL schema is provided the fields to retrieve multilingual data.

#### Types `Post`, `Page`, `PostTag` and `PostCategory`

Query the language for the entity, and the IDs for the translations for that entity.

These types implement interface `MultilingualPressTranslatable`.

| Field | Description |
| --- | --- |
| `multilingualpressTranslationConnections` | Translation connections for the entity for all sites in the network, or `null` if no connection was assigned. |

Field `multilingualpressTranslationConnections` provides results of type `MultilingualPressTranslationConnection`, from which we can query the site ID and entity ID for the connection. It accepts input `includeSelf`, to indicate if to include the queried entity's connection in the results (it's `false` by default), and inputs `includeSiteIDs` and `excludeSiteIDs`, to filter the included sites in the results.

For instance, you can now run this query:

```graphql
{
  posts {
    __typename
    multilingualpressTranslationConnections {
      ...MultilingualPressConnectionData
    }
    multilingualpressTranslationConnectionsWithSelf: multilingualpressTranslationConnections(filter: { includeSelf: true }) {
      ...MultilingualPressConnectionData
    }

    categories {
      __typename
      multilingualpressTranslationConnections {
        ...MultilingualPressConnectionData
      }
      multilingualpressTranslationConnectionsWithSelf: multilingualpressTranslationConnections(filter: { includeSelf: true }) {
        ...MultilingualPressConnectionData
      }
    }
    
    tags {
      __typename
      multilingualpressTranslationConnections {
        ...MultilingualPressConnectionData
      }
      multilingualpressTranslationConnectionsWithSelf: multilingualpressTranslationConnections(filter: { includeSelf: true }) {
        ...MultilingualPressConnectionData
      }
    }
  }

  pages {
    __typename
    multilingualpressTranslationConnections {
      ...MultilingualPressConnectionData
    }
    multilingualpressTranslationConnectionsWithSelf: multilingualpressTranslationConnections(filter: { includeSelf: true }) {
      ...MultilingualPressConnectionData
    }
  }
}

fragment MultilingualPressConnectionData {
  siteID
  entityID
}
```

#### Types `GenericCustomPost`, `GenericTag` and `GenericCategory`

These types implement interface `MultilingualPressMaybeTranslatable`.

`GenericCustomPost` is a type used to represent any custom post installed on the site, such as `Portfolio`, `Event`, `Product`, or other. Similarly, `GenericTag` and `GenericCategory` are used to represent their taxonomies.

Each of these CPTs and taxonomies can be defined to be translatable on the MultilingualPress settings. Field `multilingualpressTranslationConnections` will then have the same behavior as for `Post` and the others (described above), and also return `null` if the entity's CPT or taxonomy is not configured to be translated.

In addition, field `multilingualpressIsTranslatable` indicates if the CPT or taxonomy is configured to be translatable.

| Field | Description |
| --- | --- |
| `multilingualpressTranslationConnections` | Translation connections for the entity for all sites in the network, or `null` if no connection was assigned, or if the entity is not configured to be translated (via MultilingualPress Settings). |
| `multilingualpressIsTranslatable` | Indicate if the entity can be translated. |

For instance, you can now run this query:

```graphql
{
  customPosts(filter: { customPostTypes: ["some-cpt", "another-cpt"] }) {
    __typename
    ...on GenericCustomPost {
      multilingualpressIsTranslatable
      multilingualpressTranslationConnections {
        ...MultilingualPressConnectionData
      }
      multilingualpressTranslationConnectionsWithSelf: multilingualpressTranslationConnections(filter: { includeSelf: true }) {
        ...MultilingualPressConnectionData
      }
      
      categories(taxonomy: "some-category") {
        __typename
        ...on GenericCategory {
          multilingualpressIsTranslatable
          multilingualpressTranslationConnections {
            ...MultilingualPressConnectionData
          }
          multilingualpressTranslationConnectionsWithSelf: multilingualpressTranslationConnections(filter: { includeSelf: true }) {
            ...MultilingualPressConnectionData
          }
        }
      }
      
      tags(taxonomy: "some-tag") {
        __typename
        ...on GenericTag {
          multilingualpressIsTranslatable
          multilingualpressTranslationConnections {
            ...MultilingualPressConnectionData
          }
          multilingualpressTranslationConnectionsWithSelf: multilingualpressTranslationConnections(filter: { includeSelf: true }) {
            ...MultilingualPressConnectionData
          }
        }
      }
    }
  }
}

fragment MultilingualPressConnectionData {
  siteID
  entityID
}
```

### Added field `_strRegexFindMatches`

Field `_strRegexFindMatches` has been added to the **PHP Functions via Schema** module. This field executes a regular expression to extract all matches from a string.

For instance, running this query:

```graphql
{
  _strRegexFindMatches(regex: "/https?:\\/\\/([a-zA-Z0-9][a-zA-Z0-9-]{1,61}[a-zA-Z0-9]\\.[a-zA-Z]{2,})/", string: "In website https://gatographql.com there is more information")
}
```

...will produce:

```json
{
  "data": {
    "_strRegexFindMatches": [
      [
        "https:\/\/gatographql.com"
      ],
      [
        "gatographql.com"
      ]
    ]
  }
}
```