Snapey

Not sure why this popped up, ITS FIVE YEARS AGO

Write a function that returns the current financial year. If its 19 the the year is 19/20

Write a function that takes the passed in year, eg 19 and returns the start, end, text of fy eg '19/20' etc.

Don't hard code this stuff as I said yesterday

And put in some security. At present its possible for anyone to change the status of any bill

You are doing an ajax call. You should not be redirecting back at the end of the function. Return a response appropriate for your javascript to consume, eg a success or failure state

You can then show a message from your javascript.

If this is too much for you, dont use ajax, just do a regular form submission

what if the connection is pooled?

fine for a 1 user system

Meaning that if you get a collection of models and cast it to an array then it won't contain the data. To return the data you should append the new accessor value to the model.

Make sure you check the number of database queries since you can easily create n+1 issues this way.

ok, now we get useful info.

After you save the data, you return the same view, but it does not have access to the categories.

As a rule never return a view from a post route.

Instead, return a redirect back to the index route.

try

 return view('admin.category.index')->with(['categories' => Category::all()]);

I prefer

 return view('admin.category.index')->withCategories(Category::all());

by the way, NEVER delete with a plain link. Use a form.

try asking on the package issues page?

Probably get the following with the correct user id

show your select element?

The follow() function does not return the created follow;

https://github.com/overtrue/laravel-follow/blob/b7d6c870b1b437122b37499e2f0fce7170dec388/src/Followable.php#L37

Please format your code by putting 3 backticks ``` on a line before and after each code block

Having a foreach loop inside a model is a code smell and will not work when returning a collection of models

ignoring the disgusting act of having html output from your controller (aaarrrrghh), you have not quoted any of the html attributes

$service.='<input type="radio"
                               name="service_type[]"
                               class="radio-input next" 
                                value="'.$fare.'">';

spacing things out with <br> tags is not the best idea. Have a think about whether flexbox and grid would give you a better result.

You don't have to pass the rules in the actual method call, you could setup the rules array then pass it into the validator?

$rules = [
            'best_estimate' => 'nullable|integer',
            'min' => [
                        'bail',
                        'nullable',
			$request->best_estimate > 0 ? 'sometimes':null,
            ];

$this->validate($request, $rules);

or something like that.

You don't have to pass the rules in the actual method call, you could setup the rules array then pass it into the validator?

$rules = [
            'best_estimate' => 'nullable|integer',
            'min' => [
                        'bail',
                        'nullable',
			$request->best_estimate > 0 ? 'sometimes':null,
            ];

$this->validate($request, $rules);

or something like that.

https://peopleperhour.com

or better, created model through relationship

$category = Auth::user()->category()->create($request->all());

but i don't like using all()

Its impossible for anyone reviewing the code to know what might be written to the database

.... and you intend to update and redeploy your code on the exactly the right day each year going forwards?

You have to move the file to local storage first

Fix your hosting public should never appear in your urls. Period.

Articles with hacks like this should be removed from the internet but unfortunately there are too many cowboys out there

use remember() in conjuction with the callback. this will put the value in cache if it does not exist. As @michaloravec points out, your code just uses the second parameter of get as the fallback. Nothing is being written to cache

be wary using dd(). it terminates the current request before anything is written permanently to the cache

Isn't passport a good solution for this?

because your input value does not match an agent slug

Url should be to a route and a controller that handles the request and returns the view partial

Do not do it as a file in public

Also, your url needs to contain the id being loaded

its because you are not maintaining session for some reason

check in your browser tools to see if cookies are being created

Here's a couple of resources that might help

https://chasingcode.dev/blog/laravel-livewire-dynamic-charts-apexcharts/

https://github.com/asantibanez/livewire-charts

@nimrod compact is just as good as any of the 3+ ways of passing data to a view

Usually for select lists I would use pluck() which I'm surprised none of the other sharpshooters have suggested.

$countries = Country::pluck('name','id');
return view('countries.index', compact('countries'));

view

@foreach($countries as $id => $name)
	<option value="{{ $id }}">{{ $name }}</option>
@endforeach

for extra marks, in the event of validation error, don't throw away their choice

<select name="country">
@foreach($countries as $id => $name)
	<option value="{{ $id }}" {{ $id == old('country') ? 'selected': '' }}>{{ $name }}</option>
@endforeach

@nimrod compact is just as good as any of the 3+ ways of passing data to a view

Usually for select lists I would use pluck() which I'm surprised none of the other sharpshooters have suggested.

$countries = Country::pluck('name','id');
return view('countries.index', compact('countries'));

view

@foreach($countries as $id => $name)
	<option value="{{ $id }}">{{ $name }}</option>
@endforeach

for extra marks, in the event of validation error, don't throw away their choice

<select name="country">
@foreach($countries as $id => $name)
	<option value="{{ $id }}" {{ $id == old('country') ? 'selected': '' }}>{{ $name }}</option>
@endforeach

Your `.htaccess' file should be directing all requests to index.php

if the client wants all users to be presented with the login then you need to protect the root page with auth middleware and not the others such as email verification. When the user lands on '/' they are redirected to login then when authenticated sent back to the root page.

Email verification out of the box in Laravel requires that the user is logged in - a stupid decision IMO - so I guess whether the verification page is in or out of the auth middleware depends if you are using the default verification or have your own solution.

Not sure what any of this has to do with ssl though?

Worryingly you don't seem to have ANY routes that require to be an authenticated user?

Your nesting level issue is because mutual followers will keep loading each other's data.

You apply this globally to the user model so user loads followers, each of those models load their followers, each of those followers loads their followers etc etc only one mutual follow and you get into a nested loop.

A different approach is required, and I suggest you KISS it (Keep it Simple Stu..)

If a user wants to see who follows them, just load them?

$followers = Auth::user()->followers;

or the other way

$follows = Auth::user()->follows; for people this user follows.

Your nesting level issue is because mutual followers will keep loading each other's data.

You apply this globally to the user model so user loads followers, each of those models load their followers, each of those followers loads their followers etc etc only one mutual follow and you get into a nested loop.

A different approach is required, and I suggest you KISS it (Keep it Simple Stu..)

If a user wants to see who follows them, just load them?

$followers = Auth::user()->followers;

or the other way

$follows = Auth::user()->follows; for people this user follows.

is the token (of 746 digits) then base64 encoded, encrypted or is it double-byte? dd() the length of the key just before it is written.

You want to prevent the site from working?

Do you really want to use a script that uses globals and echos javascript to the view? Why are you here on a Laravel site?

Ideally store lowest denomination only, ie 5 dollars and 25 cents would be stored as 525 and displayed as 5.25 in the view only.

To make sure money does not go missing, increment the number, this way another thread cannot be changing the value at the same time as this one.

ie, $wallet->increment('amount',300); adds 3 dollars

if you read the wallet, then add to the value, then save the wallet then the value can be corrupted

ie,

session 1 reads wallet, $amount = 500

Session 2 reads wallet, amount = 500

Session 1 adds 300, wallet = $800

Session 1 wallet->save(), wallet in DB = $800

Session 2 adds 250, wallet = $750

Session 2 wallet->save(), wallet in DB = $750 ! Overwrote $800

This might be a contrived example with a single user's wallet amount. But suppose this was an amount of stock in a warehouse and you have multiple shoppers buying things. Two people going through checkout at the same time can seriously screw your balances.

You need to get in the habit of thinking through situations like this, however unlikely they might be.

increment() reads, updates and writes the new value in one operation so it cannot be interspersed with other activities.

For more complex operations, consider record locking.

It will be cached when you run php artisan config:cache which you should do as part of a deployment script anyway

The 'leaderboard members' have absolutely no input into the design of Laracasts. Just saying.

Either mark the question as 'Follow', then you can see it in Following or use your own personal bookmarks

Looks like php from 10 years ago unfortunately...

Viewing requests, you would need something like wireshark https://www.wireshark.org/ or other network packet sniffer

Web pages use http, other technologies use all sorts of protocol, like VOIP for instance

or better php artisan view:clear

Its a pain to keep doing during development, and is a good reason to switch to components

by the way, I wrote a piece on including your commit hash in the view in this article. It might be of use;

https://talltips.novate.co.uk/laravel/versioning-your-laravel-project

With this setup, you could show the hash as {{config('version.hash')}}

change this (you have only one quote), and probably needs to use $bookdays

<td onclick="showMsg('{{$bookdays->id}}'>{{$bookdays->name}}</td>

or if the id is numeric, then no quote

<td onclick="showMsg({{$bookdays->id}}>{{$bookdays->name}}</td>

console.log in your method to show it is being called with the correct id

function showMsg(id)
{
	console.log(id);

read this

https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch

in the then method you need to merge the returned html into the modal, then show the modal.

Bear in mind that there will be a time delay between the click and the modal showing as you make the ajax call to the server.

Ideally store lowest denomination only, ie 5 dollars and 25 cents would be stored as 525 and displayed as 5.25 in the view only.

To make sure money does not go missing, increment the number, this way another thread cannot be changing the value at the same time as this one.

ie, $wallet->increment('amount',300); adds 3 dollars

if you read the wallet, then add to the value, then save the wallet then the value can be corrupted

ie,

session 1 reads wallet, $amount = 500

Session 2 reads wallet, amount = 500

Session 1 adds 300, wallet = $800

Session 1 wallet->save(), wallet in DB = $800

Session 2 adds 250, wallet = $750

Session 2 wallet->save(), wallet in DB = $750 ! Overwrote $800

This might be a contrived example with a single user's wallet amount. But suppose this was an amount of stock in a warehouse and you have multiple shoppers buying things. Two people going through checkout at the same time can seriously screw your balances.

You need to get in the habit of thinking through situations like this, however unlikely they might be.

increment() reads, updates and writes the new value in one operation so it cannot be interspersed with other activities.

For more complex operations, consider record locking.

Here's a couple of resources that might help

https://chasingcode.dev/blog/laravel-livewire-dynamic-charts-apexcharts/

https://github.com/asantibanez/livewire-charts

Have a look at Spatie media library

You give it the uploaded file and it will store it and create any transformations you require. Then provide methods where you can ask for the URL or Path of a particular file size, eg thumb

Its a very mature package, now on version 9 and should handle all your needs.

https://spatie.be/docs/laravel-medialibrary/v9/introduction

Don't confuse it with Media Library Pro which is a paid for package and contains tools to actually manage the images (more like an asset manager)

Have a look at Spatie media library

You give it the uploaded file and it will store it and create any transformations you require. Then provide methods where you can ask for the URL or Path of a particular file size, eg thumb

Its a very mature package, now on version 9 and should handle all your needs.

https://spatie.be/docs/laravel-medialibrary/v9/introduction

Don't confuse it with Media Library Pro which is a paid for package and contains tools to actually manage the images (more like an asset manager)

I would go for

www.mydomain.com/product-category/12/a-pretty-long-seo-friendly-product-name

www.mydomain.com/{slug1}/{id}/{slug2}

Yes, you need to design an api for your application, put those routes in the api.web and use something like passport or JWT to authenticate the 3rd party