nowendwell / laravel-terms Goto Github PK

PHP 8.1.17 (cli) (built: Mar 14 2023 23:07:43) (ZTS Visual C++ 2019 x64)
Copyright (c) The PHP Group
Zend Engine v4.1.17, Copyright (c) Zend Technologies

E:\xampp\htdocs\PersonalApp>php artisan --version
Laravel Framework 10.37.1

Help me

Here is the composer error:

  Problem 1
    - nowendwell/laravel-terms v2.1.0 requires illuminate/support 6.*|7.*|8.* -> found illuminate/support[v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
    - nowendwell/laravel-terms v2.1.1 requires illuminate/support 7.*|8.* -> found illuminate/support[v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires nowendwell/laravel-terms ^2.1 -> satisfiable by nowendwell/laravel-terms[v2.1.0, v2.1.1].

You can also try re-running composer require with an explicit version constraint, e.g. "composer require nowendwell/laravel-terms:*" to figure out if any version is installable, or "composer require nowendwell/laravel-terms:^2.1" if you know which you need.

Could you bump the script ?
Thanks, denis

Hi

The current page always displays an accept option. This is true even if the user has already accepted the current terms.
adding a route to display terms only. Useful to display to users before login, and if a user wants to review

@cyrillkalita Do you mean the path?

Instead of /latest? Or do you mean the actual route name (terms.show)?

If it is the latter can you give me some background on why this would be needed?

Hello,

I'm having this error message when users are accepting the terms (during the redirect to RouteServiceProvider::HOME or to any url.intended).

Any suggestions ?
Thanks, Denis

model needs to be configurable (i am like a super fan of how spatie does that). something along the lines of config\terms.php

/*
 * The classname of the model to be used. The class should equal or extend
 * Namespace\Contracts\Terms
 */
'model' => \Namespace\Models\Model::class,

Speaking of routes, sometimes is is important to also show the past terms and conditions, when someone has agreed to multiple versions - so that one can record and display the wordings

@cyrillkalita Help me out on this one. Are you just looking for a blade view table that shows the date the model signed?

I would prefer migrations to be publishable. not a problem when I can update the migration later, but since most of the time I know what changes i want to add, publishable migrations work better for me