Description

Knewin DINO Publicador de Notícias Corporativas publishes corporate news sent by the DINO platform directly to WordPress.

The plugin creates, updates, and deletes native WordPress posts by releaseId, downloads featured images, preserves image metadata, stores operational logs, and keeps compatibility with the legacy plugin namespace.

This plugin integrates WordPress with the DINO platform. To use the integration, a site administrator configures local integration credentials in Dino > Cadastro and provides the REST URLs shown in WordPress to the DINO platform.

DINO Terms of Service: https://dino.com.br/termos-de-uso/

DINO Privacy Policy: https://dino.com.br/politicas-de-privacidade/

REST namespaces:

/wp-json/dino-divulgador-de-noticias/v4
/wp-json/dino-divulgador-de-noticias/v1

Endpoints:

POST /auth
POST /publish
POST /delete-news
POST /logs
POST /version

Use v4 for new integrations. The v1 namespace remains available for legacy clients.

External Services

This plugin integrates a WordPress site with the DINO platform.

The plugin does not automatically send WordPress data to external servers during activation. After the administrator configures the integration, the DINO platform may call the site’s REST endpoints to authenticate, publish, update, delete, or query integration records.

When the publication payload contains imageUrl, the plugin downloads the image from that remote URL using native WordPress media APIs and stores it in the site’s media library. The image URL is provided by the DINO platform in the publication payload.

Service used: DINO platform, operated by Knewin DINO.

Privacy

The plugin stores integration credentials, operational logs, received news data, image metadata, the configured category, and technical data required to correlate releaseId values with WordPress posts in the local WordPress database.

The integration password is stored as a hash using password_hash for authentication and is also kept in the legacy password column so administrators can copy the integration data used in the partner system.

The integration password is masked by default on the Dino > Cadastro > Dados integracao screen and can be revealed with the visibility button by users with administrator permissions. Treat this value as sensitive and restrict access to the WordPress admin area.

The plugin registers REST endpoints to receive content from the DINO platform. Protected endpoints require a Bearer JWT token generated by the /auth endpoint.

The plugin does not add tracking, advertisements, pixels, or external scripts to the site’s frontend.

Installation

Install the plugin from the WordPress.org plugin directory or upload the ZIP file in Plugins > Add New > Upload Plugin.
Activate the plugin.
Go to Dino > Cadastro.
Register the integration name, email/login, and integration password.
Copy the DINO URLs shown on the screen.
Configure the DINO category used for future publications.
Test POST /auth to obtain the access_token.

On activation, the plugin creates or updates its internal tables. If plugin files are replaced while the plugin is already active, deactivate and activate it again to run schema migrations.

FAQ

How do I authenticate?

Send POST /auth with JSON containing login and password. The expected response is:

{"access_token":"jwt"}

How do I use protected endpoints?

Send the following header:

Authorization: Bearer {access_token}

Does the plugin duplicate news posts?

No. The plugin correlates posts by releaseId. If the same releaseId is sent again, the existing post is updated.

Which category is used?

The category is configured in Dino > Cadastro > Publicacao. The payload does not need to send a WordPress category.

Does the plugin display image credits on the frontend?

Description and credit display is disabled by default when the option does not exist yet. The administrator can enable it in Dino > Cadastro > Publicacao; existing saved settings are preserved.

Can the image alternative text be displayed visually?

Yes. imageAlt is always saved to the native WordPress media accessibility field when an image is attached. If the administrator wants that text to appear below the featured image, it can be enabled in Dino > Cadastro > Publicacao.

Does the plugin include showcases or shortcodes?

No. This version publishes native WordPress posts. Public display is handled by the active WordPress theme.

Do legacy clients continue to work?

Yes. The /wp-json/dino-divulgador-de-noticias/v1 namespace remains registered for compatibility.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Knewin DINO Publicador de Notícias Corporativas” is open source software. The following people have contributed to this plugin.

dinoknewin

Translate “Knewin DINO Publicador de Notícias Corporativas” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

4.0.0

New modular PSR-4 architecture.
Main namespace v4.
JWT authentication without a hardcoded secret.
News creation, update, and deletion by releaseId.
Persistence in DINO legacy tables.
Configurable DINO category.
Technical DINO author.
Image metadata support for description, caption, and credits.
Optional visual display of image alternative text on the frontend.
Administrative instructions screen.

Description

External Services

Privacy

Installation

FAQ

How do I authenticate?

How do I use protected endpoints?

Does the plugin duplicate news posts?

Which category is used?

Does the plugin display image credits on the frontend?

Can the image alternative text be displayed visually?

Does the plugin include showcases or shortcodes?

Do legacy clients continue to work?

Reviews

Contributors & Developers

Interested in development?

Changelog

4.0.0

Meta

Ratings

Contributors

Support