mattmangoni / nova-blogify-tool Goto Github PK

I've got this error when using global Nova search. I think it's related to this line:

where it should not be title but maybe body?

I tried creating a new category without filling in a description and the database caught the error, no validation. Does it need to be mandatory to input a description?

Getting error on new Post submission: 'user_id doesn't have a default value'.. Curious what you had setup outside of this package? Are there any requirements?

Hi the error happens after the installation, what can be done to solve this?

thanks

I'm going to rewrite the README file for the new version of the package.

I'm not sure if this is a Mac issue or not, but typing a question mark in the body textarea is a shortcut to jumping to Nova's search feature. This stops the ability to type in a question mark in the body.

This issue is not present in the Title text field.

If you have any suggestion or feature request, this is the right place to do it.

Doing it here is simpler than using external tools, and I'd like to lay down every new feature's details before they get created/sent as PR.

I moved my model to different directory and got this error

when i want published a post show me this error "encoding format(tmp) in not supported"
i dont know that doing?
my problem just is with upload and storage image

Getting the error below when trying push publish articles, just want to report this.

thanks

vendor.js?id=da751a53228a35fab7c4:1 TypeError: Cannot read property 'status' of undefined
at p. (app.js?id=e278aec4bd99815664dd:1)
at y (app.js?id=e278aec4bd99815664dd:1)
at Generator._invoke (app.js?id=e278aec4bd99815664dd:1)
at Generator.e. [as next] (app.js?id=e278aec4bd99815664dd:1)
at o (app.js?id=e278aec4bd99815664dd:1)
at app.js?id=e278aec4bd99815664dd:1
at new Promise ()
at new t (app.js?id=e278aec4bd99815664dd:1)
at p. (app.js?id=e278aec4bd99815664dd:1)
at p. (app.js?id=e278aec4bd99815664dd:1)

On the frontend how do I get the post to use the slug as the route instead of the ID?

Hi,

I noticed that you are not using the standard way of creating migrations. This limits the possibility to make table structure changes when upgrading to a newer version of your package.
It forces you to destroy the tables and recreate them.
What if you had content which you did not want to destroy?