{"id":356727,"date":"2026-09-09T16:50:13","date_gmt":"2026-09-09T16:50:13","guid":{"rendered":"https:\/\/br.wordpress.org\/plugins\/knewin-dino-publicador-de-noticias-corporativas\/"},"modified":"2026-09-09T16:34:59","modified_gmt":"2026-09-09T16:34:59","slug":"knewin-dino-publicador-de-noticias-corporativas","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/knewin-dino-publicador-de-noticias-corporativas\/","author":23334475,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"4.0.0","stable_tag":"trunk","tested":"7.1.2","requires":"4.6","requires_php":"7.2","requires_plugins":null,"header_name":"Knewin DINO Publicador de Not\u00edcias Corporativas","header_author":"DINO","header_description":"Plugin Knewin DINO para publicacao de noticias corporativas no WordPress.","assets_banners_color":"","last_updated":"2026-09-09 16:34:59","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":0,"downloads":92,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":[],"upgrade_notice":{"4.0.0":"<p>After updating files in an existing installation, deactivate and activate the plugin again to run schema migrations.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":[],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"<code>Dino &gt; Cadastro<\/code> screen with credentials, URLs, category, and frontend configuration.","2":"<code>Dino &gt; Instrucoes<\/code> screen with operational flow and endpoints."}},"plugin_section":[],"plugin_tags":[23709,38851,1248,7143,23853],"plugin_category":[],"plugin_contributors":[279982],"plugin_business_model":[],"class_list":["post-356727","plugin","type-plugin","status-publish","hentry","plugin_tags-dino","plugin_tags-jwt","plugin_tags-news","plugin_tags-publishing","plugin_tags-rest-api","plugin_contributors-dinoknewin","plugin_committers-dinoknewin"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/knewin-dino-publicador-de-noticias-corporativas.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"<!--section=description-->\n<p>Knewin DINO Publicador de Not\u00edcias Corporativas publishes corporate news sent by the DINO platform directly to WordPress.<\/p>\n\n<p>The plugin creates, updates, and deletes native WordPress posts by <code>releaseId<\/code>, downloads featured images, preserves image metadata, stores operational logs, and keeps compatibility with the legacy plugin namespace.<\/p>\n\n<p>This plugin integrates WordPress with the DINO platform. To use the integration, a site administrator configures local integration credentials in <code>Dino &gt; Cadastro<\/code> and provides the REST URLs shown in WordPress to the DINO platform.<\/p>\n\n<p>DINO Terms of Service: https:\/\/dino.com.br\/termos-de-uso\/<\/p>\n\n<p>DINO Privacy Policy: https:\/\/dino.com.br\/politicas-de-privacidade\/<\/p>\n\n<p>REST namespaces:<\/p>\n\n<ul>\n<li><code>\/wp-json\/dino-divulgador-de-noticias\/v4<\/code><\/li>\n<li><code>\/wp-json\/dino-divulgador-de-noticias\/v1<\/code><\/li>\n<\/ul>\n\n<p>Endpoints:<\/p>\n\n<ul>\n<li><code>POST \/auth<\/code><\/li>\n<li><code>POST \/publish<\/code><\/li>\n<li><code>POST \/delete-news<\/code><\/li>\n<li><code>POST \/logs<\/code><\/li>\n<li><code>POST \/version<\/code><\/li>\n<\/ul>\n\n<p>Use <code>v4<\/code> for new integrations. The <code>v1<\/code> namespace remains available for legacy clients.<\/p>\n\n<h3>External Services<\/h3>\n\n<p>This plugin integrates a WordPress site with the DINO platform.<\/p>\n\n<p>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.<\/p>\n\n<p>When the publication payload contains <code>imageUrl<\/code>, 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.<\/p>\n\n<p>Service used: DINO platform, operated by Knewin DINO.<\/p>\n\n<p>Terms of Service: https:\/\/dino.com.br\/termos-de-uso\/<\/p>\n\n<p>Privacy Policy: https:\/\/dino.com.br\/politicas-de-privacidade\/<\/p>\n\n<h3>Privacy<\/h3>\n\n<p>The plugin stores integration credentials, operational logs, received news data, image metadata, the configured category, and technical data required to correlate <code>releaseId<\/code> values with WordPress posts in the local WordPress database.<\/p>\n\n<p>The integration password is stored as a hash using <code>password_hash<\/code> for authentication and is also kept in the legacy <code>password<\/code> column so administrators can copy the integration data used in the partner system.<\/p>\n\n<p>The integration password is masked by default on the <code>Dino &gt; Cadastro &gt; Dados integracao<\/code> 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.<\/p>\n\n<p>The plugin registers REST endpoints to receive content from the DINO platform. Protected endpoints require a Bearer JWT token generated by the <code>\/auth<\/code> endpoint.<\/p>\n\n<p>The plugin does not add tracking, advertisements, pixels, or external scripts to the site's frontend.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install the plugin from the WordPress.org plugin directory or upload the ZIP file in <code>Plugins &gt; Add New &gt; Upload Plugin<\/code>.<\/li>\n<li>Activate the plugin.<\/li>\n<li>Go to <code>Dino &gt; Cadastro<\/code>.<\/li>\n<li>Register the integration name, email\/login, and integration password.<\/li>\n<li>Copy the DINO URLs shown on the screen.<\/li>\n<li>Configure the DINO category used for future publications.<\/li>\n<li>Test <code>POST \/auth<\/code> to obtain the <code>access_token<\/code>.<\/li>\n<\/ol>\n\n<p>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.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"how%20do%20i%20authenticate%3F\"><h3>How do I authenticate?<\/h3><\/dt>\n<dd><p>Send <code>POST \/auth<\/code> with JSON containing <code>login<\/code> and <code>password<\/code>. The expected response is:<\/p>\n\n<pre><code>{\"access_token\":\"jwt\"}\n<\/code><\/pre><\/dd>\n<dt id=\"how%20do%20i%20use%20protected%20endpoints%3F\"><h3>How do I use protected endpoints?<\/h3><\/dt>\n<dd><p>Send the following header:<\/p>\n\n<pre><code>Authorization: Bearer {access_token}\n<\/code><\/pre><\/dd>\n<dt id=\"does%20the%20plugin%20duplicate%20news%20posts%3F\"><h3>Does the plugin duplicate news posts?<\/h3><\/dt>\n<dd><p>No. The plugin correlates posts by <code>releaseId<\/code>. If the same <code>releaseId<\/code> is sent again, the existing post is updated.<\/p><\/dd>\n<dt id=\"which%20category%20is%20used%3F\"><h3>Which category is used?<\/h3><\/dt>\n<dd><p>The category is configured in <code>Dino &gt; Cadastro &gt; Publicacao<\/code>. The payload does not need to send a WordPress category.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20display%20image%20credits%20on%20the%20frontend%3F\"><h3>Does the plugin display image credits on the frontend?<\/h3><\/dt>\n<dd><p>Description and credit display is disabled by default when the option does not exist yet. The administrator can enable it in <code>Dino &gt; Cadastro &gt; Publicacao<\/code>; existing saved settings are preserved.<\/p><\/dd>\n<dt id=\"can%20the%20image%20alternative%20text%20be%20displayed%20visually%3F\"><h3>Can the image alternative text be displayed visually?<\/h3><\/dt>\n<dd><p>Yes. <code>imageAlt<\/code> 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 <code>Dino &gt; Cadastro &gt; Publicacao<\/code>.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20include%20showcases%20or%20shortcodes%3F\"><h3>Does the plugin include showcases or shortcodes?<\/h3><\/dt>\n<dd><p>No. This version publishes native WordPress posts. Public display is handled by the active WordPress theme.<\/p><\/dd>\n<dt id=\"do%20legacy%20clients%20continue%20to%20work%3F\"><h3>Do legacy clients continue to work?<\/h3><\/dt>\n<dd><p>Yes. The <code>\/wp-json\/dino-divulgador-de-noticias\/v1<\/code> namespace remains registered for compatibility.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>4.0.0<\/h4>\n\n<ul>\n<li>New modular PSR-4 architecture.<\/li>\n<li>Main namespace <code>v4<\/code>.<\/li>\n<li>JWT authentication without a hardcoded secret.<\/li>\n<li>News creation, update, and deletion by <code>releaseId<\/code>.<\/li>\n<li>Persistence in DINO legacy tables.<\/li>\n<li>Configurable DINO category.<\/li>\n<li>Technical DINO author.<\/li>\n<li>Image metadata support for description, caption, and credits.<\/li>\n<li>Optional visual display of image alternative text on the frontend.<\/li>\n<li>Administrative instructions screen.<\/li>\n<\/ul>","raw_excerpt":"Publish corporate news from the DINO platform to WordPress through REST API integration with JWT authentication and legacy endpoint compatibility.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/356727","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=356727"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/dinoknewin"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=356727"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=356727"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=356727"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=356727"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=356727"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=356727"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}