bugsysha

how can I accept card data safely

2checkout will provide you. Try searching if there is an option to use it with Laravel Cashier. That will reduce the time you need to put in to make it work and definitely reduce the complexity.

do I need to be PCI compliant

Nope.

what is required to become a one?

Simple googling can probably tell you far more than anyone here.

I agree. Running seeders from controllers is a very bad idea.

how can I accept card data safely

2checkout will provide you. Try searching if there is an option to use it with Laravel Cashier. That will reduce the time you need to put in to make it work and definitely reduce the complexity.

do I need to be PCI compliant

Nope.

what is required to become a one?

Simple googling can probably tell you far more than anyone here.

That way you are trying to find a cure for the consequence, not for the root cause of the problem.

Then create a command that will trim all problematic records in the database. I'm suggesting a command cause then you can use it as much as you need until you resolve all your issues.

I'm confused. Is it 8.0.3 or 8.0.5? I guess that is a typo?

Is there a way I can trim the original values before Laravel captures them?

Laravel already trims the input. You can verify it by going to \App\Http\Kernel and in $middleware property you should see \App\Http\Middleware\TrimStrings::class.

If you wan't to hide it from Network tab in Browser Dev Tools, then it isn't possible.

I assume you can extend \Illuminate\Session\Middleware\StartSession middleware and replace it in \App\Http\Kernel::$middlewareGroups['web']. Then within your middleware class you can decide when not to add cookies and when to add them.

Maybe you can start by extracting it to a separate file.

<template></template>

<style src="pathToCssFile"></style>

<script></script>

You have it here on Laracasts. I've ended up building everything manually cause I needed better performance and more control. Depending on what you are planning to build it may or may not make sense for you to do the same.

You have it here on Laracasts. I've ended up building everything manually cause I needed better performance and more control. Depending on what you are planning to build it may or may not make sense for you to do the same.

Also here you can find some different approaches to the same problem.

There are few options here. Depending on what you like.

First option:

User::select($some_select)
	->when($bool, \Closure::fromCallable([$this, 'my_method']))

Second option:

• define the class

class SomeClass
{
    public function __invoke()
    {
    }
}

• use the class

User::select($some_select)
	->when($bool, new SomeClass)

Just note that you'll have problems like following:

$something = 123;

User::select($some_select)
	->when($bool, \Closure::fromCallable([$this, 'my_method']))

You will have no option to do:

User::select($some_select)
	->when($bool, function () use ($something) {})

So for that reason it is better to use the first option so you can do this:

$this->something = 123;

User::select($some_select)
	->when($bool, \Closure::fromCallable([$this, 'my_method']))

protected function my_method()
{
  // you will have access to something property
  $this->something
}

There are few options here. Depending on what you like.

First option:

User::select($some_select)
	->when($bool, \Closure::fromCallable([$this, 'my_method']))

Second option:

• define the class

class SomeClass
{
    public function __invoke()
    {
    }
}

• use the class

User::select($some_select)
	->when($bool, new SomeClass)

Just do <img src="/path-from-public-folder/picture.jpg"/> if the image is located at public/path-from-public-folder/picture.jpg.

I use observers, but I don't think you need them.

I would advise you to invest in English since you will gain so much from it. Almost all communication on all forums is in English, so you will be able to find solutions far easier. Also if you want to work for some company you would probably have to communicate in English, and especially write code in English also. Without it I don't think you would have a shot to apply and get the job which might be paying way more than your local companies.

What is considered better in your mind? If it is performance, then probably not. If it is code readability then yes.

I would advise you to invest in English since you will gain so much from it. Almost all communication on all forums is in English, so you will be able to find solutions far easier. Also if you want to work for some company you would probably have to communicate in English, and especially write code in English also. Without it I don't think you would have a shot to apply and get the job which might be paying way more than your local companies.

What for are you using it? Video is not revealing everything so I don't understand how can you use something that feels unrelated. I'm probably missing some detail.

That is a normal behaviour. Query param page has no use on the show page. It needs to be removed.

Maybe you should move this to updating method on the observer.

Yes it is useful, but I haven't used it since ES6 was available. Just my personal preference to avoid dependencies.

Put dd('something') into render method on your component. That way you will know if the component is the issue or the view. Also try running composer dump-autoload and clearing all caches (php artisan cache:clear, php artisan view:clear, etc...).

I usually break it down into following steps:

1. save the quote request to the database
2. emit the event
3. with listener send email that the request was received, but I don't see the point for this since you can do that with a simple notification on the page that says "request received"
4. notify the site owner that a request has been received

If you create a form request, you can check if the user is authenticated, and which type of a user, and based on that return appropriate rules from the rules method.

public function rules(): array
{
    $rules = [
        'name' => 'required|boolean',
    ];

	if ($this->user()) { // this is to check if they are logged in
		$rules['something'] = 'required|string';
	}

	if ($this->user()->isSomething()) { // here you check for a type
		$rules['something-else'] = 'required|string';
	}

    return $rules;
}

Have you tried embedding it?

Also if you need more control then maybe you should use JavaScript version of fingerprint.

Yeah. It is based on couple of things. You can find it here. I've used it for some projects while ago. It worked fine.

What might be better, but not perfect, is fingerprint on the request object. So try $request->fingerprint().

Have you tried <x-queryUrl::sort sort="Group"/>?

You can probably use firstOrCreate() on the model in to simplify the code.

That depends on what do you want to allow your users to do. I don't think you can go right or wrong here. You can present to them all profile pictures from social accounts and let them pick the one that they like the most. Only limit is your imagination.

I don't thing anyone can give definite answer to what is better. Depends what the criteria for better is. If it is speed of development, I guess that depends on the team and what they are proficient with. If it is less work, then probably blade files. But you would still have to do the routing for the API and probably use API resources or some other way to transform the data so it is API compliant. If someone says one way is better than the other, then they are probably biased cause of their familiarity or what they are used to.

I don't thing anyone can give definite answer to what is better. Depends what the criteria for better is. If it is speed of development, I guess that depends on the team and what they are proficient with. If it is less work, then probably blade files. But you would still have to do the routing for the API and probably use API resources or some other way to transform the data so it is API compliant. If someone says one way is better than the other, then they are probably biased cause of their familiarity or what they are used to.

It was a poor name choice on the part of the authors in my opinion, as a 'Form' from the front-end is typically associated with a POST request.

Yeah, I also find that naming bit strange. But once you learn what it is used for you just roll with it.

Then something about it being a GET request will cause the request to continually attempt to redirect if overTime is not equal to 1, 2, or 3. I want it to return a validation error. Is there a way I can do this?

You've specified that the value of overTime needs to be 1, 2 or 3. That is why you get redirected back. If you are using blade you can do following:

@error('overTime')
<p>overtime is wrong</p>
@enderror

I had situations were we had separate user for every social account and in the end we wanted to merge them. And also the opposite. So it depends on what do you need from business perspective. I would rather go with single user with multiple accounts.

I think it all depends on wether you want to show apps related to those social accounts. If you have a calendar in your app for which you pull data from Google Calendar or Microsoft Calendar then it depends on the use cases you want to cover. If you want to show data from both GC and MC at the same time, then one user account should be "linked" to multiple social accounts. If that is not what you want/need, then other approach might be better where you have one user per social account.

Not sure I fully understand your question but I would either create an API from start and combine it with an SPA, or go down the traditional route where I return HTML. Combining two never worked for larger projects, and I assume this will be a larger project as you are planning iOS/Android apps.

It seems like bad design to make a FormRequest since, as far as I understand, form requests should only be used for POST requests.

That is a wrong assumption in my mind. I create them always.

I've tried to reply but I got an error saying Spam detected. Please rephrase.. Sorry but I guess my solution can not be suggested :D

public static function firstOrCreate(array $attributes = [], array $values = [])
{
  $result = parent::query()->firstOrCreate($attributes, $values);

  // top secret work

  return $result;
}

Overriding of built in functions/methods as firstOrxxx() is NOT RECOMMENDED.

Might be useful:

• https://github.com/calebporzio/parental
• https://tighten.co/blog/extending-models-in-eloquent/

@laracoft updated per your liking sir 🥳

@mst526 great find. It (wire:key) sounds familiar but I've forgot about it definitely.

public static function firstOrCreate(array $attributes = [], array $values = [])
{
  $result = parent::query()->firstOrCreate($attributes, $values);

  // top secret work

  return $result;
}

Overriding of built in functions/methods as firstOrxxx() is NOT RECOMMENDED.

Might be useful:

• https://github.com/calebporzio/parental
• https://tighten.co/blog/extending-models-in-eloquent/

Don't get me wrong. I don't suggest it.

Shouldn't it be:

public function firstOrCreate(array $attributes = [], array $values = [])
{
  $result = parent::firstOrCreate(array $attributes = [], array $values = []);

  // top secret work

  return $result;
}

I would argue that what you are doing right now is an overkill. Or even worse cause you are wasting your time on things that don't matter. Or if possible even worse, you are wasting your time over and over again on the things that don't matter.

As I said, for the same price you are paying right now you can get a VPS. Probably there won't be any difference cause hardware will be pretty much the same.

Is there a way to override firstOrNew() of a model?

Yes, just inside of your model (or maybe better trait) define a method with same name.