ismaile

Maybe, you can check this one out then: https://github.com/google/ReCAPTCHA

Besides, it's the Google one and it's a PHP one, so it's not specific to Laravel

Here is a video: https://www.youtube.com/watch?v=mE6NU5ABel4

I wouldn't redirect to login, I would redirect back instead. Indeed, guest users posting a contact form must be redirected back. However, if an authenticated user performs an action for authenticated users only, there will be the back redirect and the auth middleware can take care of the login redirection.

When the page expires, a TokenMismatchException is thrown.

A TokenMismatchException is also thrown when someone tries to post data to your site from another site.

So, if you don't mind that in both cases, it would redirect to a page, you might override the render method in the app/Exceptions/Handler.php like this:

public function render($request, Throwable $exception)
    {
        if ($exception instanceof TokenMismatchException) {
            return back()->with('custom-error', 'The page has expired');
        }
        return parent::render($request, $exception);
    }

And make sure to add the imports:

use Illuminate\Session\TokenMismatchException;
use Throwable;

Basically, the code says to redirect back when there is a TokenMismatchException and use the default logic from therender method in the parent class otherwise. If this method changes in the framework, you would still be calling it without worrying too much about the changes.

Please note the custom-error sent with the response, indeed, you must let the user know what happened.

Hope this helps

They will give you the same result but they work differently:

• $settings = Setting::first(); will return directly the first record from the database running : select * from settings limit 1;
• $settings = Setting::all()->first(); will call all that returns a collection after running: select * from settings;, then it will call first to take the first element in the collection: https://laravel.com/docs/8.x/collections#method-first

You should use the first one.

Source: I used https://laravel.com/docs/8.x/database#listening-for-query-events to confirm my first thought. toSql gave a different result in this specific use case, it gave select * from settings in both cases

You shouldn't put your Regex between double quotes, here is how it should be:

var emailRegex = new RegExp(/([\s]*)([_a-zA-Z0-9-]+(\.[_a-zA-Z0-9-]+)*([ ]+|)@([ ]+|)([a-zA-Z0-9-]+\.)+([a-zA-Z]{2,}))([\s]*)/i, "g");

Perfect, you're welcome :)

Do you use https://github.com/spatie/laravel-activitylog ?

Since you use a One to Many, I would expect department instead of departments in your with call. I assume you have a method department using belongsTo in your Order model.

Besides, just to confirm it, you use orderBy with variables, I would call the second variable$direction. Indeed, it may be confusing in the future. As you may know, orderBy is used like this: orderBy('name', 'desc')

Do you use https://github.com/spatie/laravel-activitylog ?

Since you use a One to Many, I would expect department instead of departments in your with call. I assume you have a method department using belongsTo in your Order model.

Besides, just to confirm it, you use orderBy with variables, I would call the second variable$direction. Indeed, it may be confusing in the future. As you may know, orderBy is used like this: orderBy('name', 'desc')

You're welcome, the display might be confusing at the beginning :)

Actually, you had the right result, it's just formatted in a different way.

array:2 [▼
  0 => "date"
  1 => "user_id"
]

is equivalent to:

[
  "date",
  "user_id"
]

They will give you the same result but they work differently:

• $settings = Setting::first(); will return directly the first record from the database running : select * from settings limit 1;
• $settings = Setting::all()->first(); will call all that returns a collection after running: select * from settings;, then it will call first to take the first element in the collection: https://laravel.com/docs/8.x/collections#method-first

You should use the first one.

Source: I used https://laravel.com/docs/8.x/database#listening-for-query-events to confirm my first thought. toSql gave a different result in this specific use case, it gave select * from settings in both cases

From the information I have so far, I would reach for a Many to Many relationship. Indeed, we can say that a department has many orders and an order belongs to many departments.

Imagine you have a specific order Order, let's call it O.

The order goes from department A to C:

• A makes the order
• B verifies it
• C confirms it.

Now, imagine that you have a One to Many relationship, so, the order belongs to C at the end. But, what if you want to know if it has been processed by A. That's where the Many to Many is handy, you can still get a record that says that it has been processed by A, I'm referring to the pivot table record. Besides, you can put a status flag and for example, a completed_at date which is null by default.

I would need to understand the Order business logic. What is the life cycle of an order ? I guess it's initiated by a department but you said that a department should be able to pass it to another one. Could you give me an example ?

An example like the following would be perfect: "IT department makes 5 orders to buy laptops ... " :)

From what I understand, I would use a regular one.

I am assuming you have the following tables:

• employees or users
• departments
• orders

And I am assuming that all departments have the same attributes except for the type: "Sales", "HR", ... So, with a where constraint, you can filter departments and you can get all employees for a specific type of department. As for the orders, it's pretty similar, you can get all orders passed from a specific department and from one to another.

I would have reached for polymorphism in a scenario in which a user works in a Company or a School and each one of them is completely different and each correponding table has its own set of attributes in the database.

You are welcome :)

I think you should use an @if statement like this:

@if ($post->created_at->format('Y-m-d') === date('Y-m-d'))
<span style="color: #ff3c00" class="blink_me"><i>BARU</i></span>
@endif

date is a PHP function : https://www.php.net/manual/fr/function.date.php When you call it like this: date('Y-m-d'), it returns today's date formatted with Y-m-d and you format your article created_at date the same way

I've just installed it and tested it a bit, I love it. Thanks a lot :)

@sinnbeck Nice image :)

Actually, you had the right result, it's just formatted in a different way.

array:2 [▼
  0 => "date"
  1 => "user_id"
]

is equivalent to:

[
  "date",
  "user_id"
]

I am surprised the following configuration keys are within an array:

    'date_format' => 'd/m/Y',
    'date_format_js' => 'dd/mm/yy',

You should try to put them outside of the array and remove the array.

I would recommend to take a look at this tutorial, it looks pretty well explained: https://www.itsolutionstuff.com/post/laravel-7-multiple-file-upload-tutorialexample.html

You should adapt it to your images use case as you did in your HTML with:

accept="image/png, image/jpeg"

and modify the controller validation part:

'images.*' => 'mimes:jpeg,png'

And other details such as your images storage folder.

At first sight, it might be related to the configuration file filesystems.php. I think this can help you: https://laracasts.com/discuss/channels/laravel/driver-is-not-supported-1

@snapey Yeah, having 2 routes with the same endpoint is clearly irrelevant. Just wanted to point out that detail since we were giving different explanations. When I think about it, this might have been confusing.

You are welcome :)

@snapey I have just tested using the same endpoint and it's the second one that is used. I guess you were thinking about the typical use case posts/{post} vs posts/create

Actually, if you have 2 routes with the same endpoint, the second one overwrites the first. So, the agenda method is going to be called but the index method never. So, the code is not useful.

However, maybe Route::resource can help you sometimes to avoid to have a lot of route declarations in your route file.

Maybe, you can do this in your controller:

$msgs = Message::where('de_user_id', $request->user()->id)->orWhere('para_user_id', $request->user()->id)->get()
// ...

You'll have both type of messages sent and received. Then you'll have to return only $msgs and loop through msgs only in Vue, no need to have 2 loops. Then, you can check at each iteration if the id is equal to the one of the user so that you can put the message to the left or to the right.

Maybe, you can do this in your controller:

$msgs = Message::where('de_user_id', $request->user()->id)->orWhere('para_user_id', $request->user()->id)->get()
// ...

You'll have both type of messages sent and received. Then you'll have to return only $msgs and loop through msgs only in Vue, no need to have 2 loops. Then, you can check at each iteration if the id is equal to the one of the user so that you can put the message to the left or to the right.

@msslgomez You're welcome. Actually, the variable can have any name but I think App is pretty common

In i18n.js, you can use window.App.locale if you use the example above. In this case, App is a global variable. Since it is pretty small, you can put it in your layout master file in the HTML header and it would be available in any JavaScript file.

Is it not what you need ?

@snapey yeah totally, I focused entirely in the standard non ajax way. You are right, if it's an ajax call, then just return;. Otherwise, the full HTML is returned and it's not useful at all.

@hendrasaputra2323 By default, in Laravel, for a Papan model, the corresponding table should bepapans.

Usually, people leave it in the plural form but you can update the table associated with a model in your Papan Model file:

protected $table = 'papan';

https://laravel.com/docs/8.x/eloquent#eloquent-model-conventions

@hendrasaputra2323 By default, in Laravel, for a Papan model, the corresponding table should bepapans.

Usually, people leave it in the plural form but you can update the table associated with a model in your Papan Model file:

protected $table = 'papan';

https://laravel.com/docs/8.x/eloquent#eloquent-model-conventions

In your database/migrations folder, do you have a file called something like: ...create_papans_table.php ?

Please run php artisan migrate if you have not so that your latest migrations are taken into account.

First of all, you probably know it, the proper way is with return back();

Here is the back helper definition in the framework:

* @return \Illuminate\Http\RedirectResponse
     */
    function back($status = 302, $headers = [], $fallback = false)
    {
        return app('redirect')->back($status, $headers, $fallback);
    }

It returns a RedirectResponse and by default it uses 302. Now, in practice, after the 302, you'll get a 200 if the target route exists and everything goes well, since it's a redirection.

When you don't use return back();, it's as if you do:

back();
return;

The RedirectResponse object is built at some point with back() but never returned and by default, when there is no return, it's as if the method ends with return; which means, it ends returning null, so nothing went wrong, hence 200 directly.

In i18n.js, you can use window.App.locale if you use the example above. In this case, App is a global variable. Since it is pretty small, you can put it in your layout master file in the HTML header and it would be available in any JavaScript file.

Is it not what you need ?

A common practice is to send the data you need in an App variable :

// In your blade file
<script>
window.App = {!!
 json_encode([
   'authenticated' => Auth::check(),
   'locale' => config('app.locale')
  ])
!!}
</script>

I added authenticated to illustrate how you could put other information

Otherwise, maybe you can have your localein your html tag:

<html lang="{{app()->getLocale()}}">

Then use something like this in Javascript:

document.documentElement.lang

For a list of available JavaScript libraries, you can check this: https://github.com/sorrycc/awesome-javascript#tours-and-guides That's the section related to tours and guides.

The awesome lists have a lot of nice package/library suggestions.

Here is a correction for your code, I haven't tested it:

public function store(Request $request) {
  $people = $request->all();
  $duplicate = People::where('name',$people['name'])->where('surname', $people['surname'])->first();  
  if($duplicate) {
    return response()->json(
      PeopleDuplicate::create([
        'people_id'=> $duplicate->id,
        'name'=> $people['name'],
        'surname'=> $people['surname']
      ]), 201);
    } 
  // ...  
}

It's just a first step, the code can obviously be optimized but you can notice that:

• request->all() can't be used, you should either use the global helper request() like this request()->all() or the variable $request like this $request->all()
• since $request->all() returns an array, $people is accessed like this $people['name']

Hope this helps

Here is a correction for your code, I haven't tested it:

public function store(Request $request) {
  $people = $request->all();
  $duplicate = People::where('name',$people['name'])->where('surname', $people['surname'])->first();  
  if($duplicate) {
    return response()->json(
      PeopleDuplicate::create([
        'people_id'=> $duplicate->id,
        'name'=> $people['name'],
        'surname'=> $people['surname']
      ]), 201);
    } 
  // ...  
}

It's just a first step, the code can obviously be optimized but you can notice that:

• request->all() can't be used, you should either use the global helper request() like this request()->all() or the variable $request like this $request->all()
• since $request->all() returns an array, $people is accessed like this $people['name']

Hope this helps

The error Class NoCaptcha not found is due to the usage of NoCaptcha in your blade file. The class is not loaded or doesn't exist.

What does your composer.json look like ?

And more importantly, in your vendor directory, do you have anhskohbo/no-captcha ?

By the way, you can try to run: composer dump-autoload

@swimmer you forgot the link :)

By the way, it seems like Google provides some test keys: https://developers.google.com/recaptcha/docs/faq#id-like-to-run-automated-tests-with-recaptcha.-what-should-i-do

As many frameworks, Laravel uses the MVC pattern and calling a controller from another one is clearly not something you should do. So, you should avoid Option B.

That's exactly what I was checking. I was investigating if the package has really been installed properly. You can try the configuration steps and let me know what is the outcome

Please run:

php artisan vendor:publish --provider="Anhskohbo\NoCaptcha\NoCaptchaServiceProvider"

and tell me what happens.

Try to replace:

{!! NoCaptcha::display() !!}

with:

{!! Anhskohbo\NoCaptcha\Facades\NoCaptcha::display() !!}

And

{!! NoCaptcha::renderJs() !!}

with:

{!! Anhskohbo\NoCaptcha\Facades\NoCaptcha::renderJs() !!}

Are you sure ? Instead of fr at the end, it is rf

I think there is a typo, it's called @csrf

Before moving forward, let's do something simple, please run:

composer remove anhskohbo/no-captcha

then when it's done:

composer require anhskohbo/no-captcha

I would take a look at your route definition, after Route::get, you should have something like:

'articles/{article}'

having {article} is important