Hi! Thanks for your plugin!

It would be significant enhancement to purge REST Cache (https://strapi-community.github.io/strapi-plugin-rest-cache/) on publish/unpublish

On a linux server, it seems like the plugin is publishing not relating on the date. Even if I put a date that is far in time to publish: When the cron action gets launched, the entry get published not considering the date.

I checked dates and they seem great:

When installing this plugin, I get the following dependency error:

~/dev/my-project$ npm install strapi-plugin-publisher
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react-router-dom
npm ERR!   peer react-router-dom@"^5.2.0" from @strapi/[email protected]
npm ERR!   node_modules/@strapi/design-system
npm ERR!     @strapi/design-system@"1.2.1" from @strapi/[email protected]
npm ERR!     node_modules/@strapi/admin
npm ERR!       @strapi/admin@"4.3.6" from @strapi/[email protected]
npm ERR!       node_modules/@strapi/strapi
npm ERR!         peer @strapi/strapi@"^4.3.4" from @strapi/[email protected]
npm ERR!         11 more (@strapi/plugin-graphql, @strapi/plugin-seo, ...)
npm ERR!     peer @strapi/design-system@"^1.2.0" from [email protected]
npm ERR!     node_modules/strapi-plugin-menus
npm ERR!       strapi-plugin-menus@"^1.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! strapi-plugin-publisher@"*" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react-router-dom
npm ERR!   peer react-router-dom@"^6.2.1" from [email protected]
npm ERR!   node_modules/strapi-plugin-publisher
npm ERR!     strapi-plugin-publisher@"*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

Stapi version 4.3.6. Is this my setup or is it a problem with the plugin?

I have install and enabled the plugin, but unfortunately, the section Publisher not apear at the content-type informations.

Any help?

config/server.ts:

export default ({ env }) => ({
  //...
  cron: {
    enabled: true,
  },
});

config/plugins.ts:

export default ({ env }) => ({
    //...
    publisher: {
      enabled: true,
    },,
});

Plugin version: "strapi-plugin-publisher": "^1.1.3" Strapi version: "@strapi/strapi": "4.3.4"

Hello,

It seems like your plugin doesn't trigger webhooks. Basically when the publish / unpublish event gets triggered, it seems like my webhoobs related to publish and unpublish event are not launched

Another tiny fix: The "Add a publish date" uses the primary variant, but the variant is actually named default, according to here: https://design-system-git-main-strapijs.vercel.app/?path=/story/design-system-components-button--variants

This only prints a warning to the console when run in dev mode with the --watch-admin option, I assume because the warning is suppressed otherwise.

The button component appears to be falling back to the default variant in any case, so this doesn't affect how it actually gets rendered. The main effect is just to get rid of that warning in the console.

I have a list of content with publish dates from the future and I would like to POST them to Strapi through API with the publish date schedule included, this plugin allows me to do this?

• feat(api): add actions
• feat(utils): add isEmpty and getTrad, remove hasResponseData
• feat(trad): add en translation
• feat(hooks): add useReactQuery
• refactor(components): use react-query for state (fixes delete/add edge case)
• chore(assets): add new images for redesign

Hi there, I love the plugin you've written, it has been super easy to set up and use. One feature I'm trying to add to my website is a display showing the upcoming posts and their publish dates. It seems the REST endpoint /publisher/actions has this info, but it requires an admin token and it doesn't seem to be configurable to give access to other roles.

Is this something that could be added, or do you have any pointers for how I could implement it? I wouldn't mind doing it myself but I don't have any experience writing plugins so the overhead of learning all that makes it a bit prohibitive for me.

In config/plugins.js file publisher is set to disable:

    publisher: {
	enabled:  false,
    }

Looking at the log the cron task is executing every minute, regardless of the publisher plugin being disabled. Web console is OK as the publisher buttons are not being showed, but the log shows that the crontask '*/1 * * * *' still executes itself. Cron task should at least verify the plugin is activated in order to avoid not useful executions.

Found out because I'm getting this error:

9|strapi-prod  | 2022-12-20T18:13:00: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
9|strapi-prod  | 2022-12-20T18:13:00:     at Client_PG.acquireConnection (/opt/apps/strapi-prod/node_modules/knex/lib/client.js:310:26)
9|strapi-prod  | 2022-12-20T18:13:00:     at async Runner.ensureConnection (/opt/apps/strapi-prod/node_modules/knex/lib/execution/runner.js:294:28)
9|strapi-prod  | 2022-12-20T18:13:00:     at async Runner.run (/opt/apps/strapi-prod/node_modules/knex/lib/execution/runner.js:30:19)
9|strapi-prod  | 2022-12-20T18:13:00:     at async Object.execute (/opt/apps/strapi-prod/node_modules/@strapi/database/lib/query/query-builder.js:396:22)
9|strapi-prod  | 2022-12-20T18:13:00:     at async Object.findMany (/opt/apps/strapi-prod/node_modules/@strapi/database/lib/entity-manager/index.js:142:22)
9|strapi-prod  | 2022-12-20T18:13:00:     at async Object.findMany (/opt/apps/strapi-prod/node_modules/@strapi/strapi/lib/services/entity-service/index.js:313:20)
9|strapi-prod  | 2022-12-20T18:13:00:     at async Object.findMany (/opt/apps/strapi-prod/node_modules/@strapi-community/strapi-plugin-url-alias/server/admin-api/services/override-query-layer.js:17:28)
9|strapi-prod  | 2022-12-20T18:13:00:     at async Object.*/1 * * * * (/opt/apps/strapi-prod/node_modules/strapi-plugin-publisher/server/config/cron-tasks.js:11:21)

Tried hot patching the cron string to 0 0 */30 * * but it still shows the error with the 1 minute cron string. Also related (but I've seen that this is a common mis-practice in most Strapi development) all propmises are treated in an optimistic way. All Promise based functions use async-await without considering that something can (and will) probably fail, so there's no error catching.

Strapi version: 4.4.3 Publisher plugin version: 1.1.3 (checked vs Github and cront-task.js file is the same I have on my installation).

Hello,

First of all, thank you for the great plugin. I want to request a feature that improves the publication time setting.

The time picker next to the publish date is displayed per minute. Can this be adjusted to 15 minutes intervals? This functionality is supported by the Strapi TimePicker.

Optionally let users configure the interval option.

Screenshot

Have a nice day.