Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

The preview variations have been renamed to animated for clarity. We have not seen any project using it, but if that is the case, rename your “previewBig” variations to “animatedBig” for example.

New Portal features

New Back-Office features

Dataview i18n language filtering

In order to give our users more flexibility about what they are seeing in the dataview, it’s now possible to show/hide all the i18n field from the dataview. A new button “Translations” is now displayed when i18n fields are present in the dataview. This is totally independant from the security and it’s working on what is already displayed.

New analytics display mode in the datalist

In the datalist, there is a new entry called “Analytic Dashboards”, it enables you to see all the left filters as graphics and therefore see how they are distributed in the current object.

To add a new graphic, just add the tag popinlist_search_group or popinlist_search_tree on any property you want to inspect, it will then be displayed on the left and a graphic will appear.

New dashboards and features on Analytics V2

List of the new features :

  • You can now select both “from” and “to” in the period filter.

  • A dashboard about search in the back-office has been added.

  • A dashboard about filters in the back-office has been added.

  • New filters are available for some dashboards.

On top of that, performances has been improved so dashboards loading is now noticeably faster.

New copy / paste values for multi-update

Previsouly, it was only possible to copy metadata from a given dataview and paste them to a new asset.

This copy/paste operation is now available in a multi-update.

A new button “Paste Values” appears when there are copied data in the clipboard.

All the non-empty metadata from copied asset are pasted to the selected assets, it then works as a classical multi-udpate.

The operation is automatically set to “Change”.

External video tracking

To keep track on where this video has been externally published, a new objet “externalvideo” that is linked to the default asset will now be filled by the MediaCloud API when the video is published on a YouTube channel :

Reverse Image Search

The plugin PACKAGED_ReverseSearch offer a new tab in the dataview of an asset, to trigger a Image Reverse search, powered by Tineye and Google Image search.

To trigger a new search, hit “register asset”.

When the search is complete, the list of the matches will be displayed with a line for each domain match :

Clicking on a domain opens a detailed list of matches for this domain :

Structure changes

Added structures

Following structures were added to support asset reverse search feature.

  • reversesearch

  • reversesearchdomain

  • reversesearchmatch

  • reversesearchpage

Following structure were added to store external video IDs and status on Youtube.

  • externalvideo

Updated structures

massimportitem

  • itemisvalid (ADDED) Allows to store item validity against its target structure

    • child → activated

    • Not editable

    • default 1

Removed structures

Following structures were related to the Labs_Tineye plugin have been removed from the NAR:

  • tineyebacklink

  • tineyeresult

  • tineyesearch

  • wkftineyebacklink

  • wkftineyebacklinkaction

  • wkftineyeresult

  • wkftineyeresultaction

  • wkftineyesearch

  • wkftineyesearchaction

New operation of the API connection in session mode

The version 2021.4 introduces a new connection mode of the API in session mode. The surfer is no longer created at each invocation (this avoids the execution of surferservices at each invocation).

This mode is called sessionful.

This mode is activated by default, with the sessionful plugin parameter.

Cookies

The cookie used to maintain the session is JSESSIONID.

The x-wedia-api-token, x-wedia-api-token-so and x-wedia-api-token-tk cookies are maintained.

Session sharing between Backoffice and Portal

The session (the JSESSIONID cookie) is shared between Portal and Backoffice. This means that logging into one connects to the other. And disconnecting from one, disconnects from the other.
Note that when a user disconnects from Portal as a user, he is automatically reconnected to the "Portal" as an application.

Compatibility

There is no change to make in the way the services are called (signin, token refresh, signout). The cookieauth parameter is always used to switch to cookie mode (instead of bearer). However, the sessionauth parameter is no longer supported.

The session/JSESSIONID mode is enabled by default. The operation is imposed on all callers, but it is necessary for them to maintain the JSESSIONID cookie to operate in session mode (including if authenticated by bearer), otherwise there will always be a connection (with execution of the surferservices) at each invocation.

The old modes are still supported. API Authentication & Connection Modes

WXM_RESTAPI_SESSION

The WXM_RESTAPI_SESSION plugin has been put on some environments to force a session connection. It is no longer needed in sessionful mode. The connection being already in session, it will be without effect to invoke its service /api/rest/session/signin. However, it is better not to use this workaround anymore.

Portal development in localhost

The Portal development done on the localhost domain requires a special setup.

Local development with REST API sessionfull mode

Old cookies maintained by browsers

Normally, the server handles old cookies that may interfere with the new system. There may be special unmanaged cases that require cleaning up the cookies in the browser.

  • No labels