Snapey

only the storage/app/public folder should be accessible. the storage:link command maps this to public/storage

your custom folder should be in the storage/app/public folder unless you are ok to create your own symlink

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

"invalid route action"

For that, you would need to show the routes...

you can add additional checks to the Auth::attempt method

https://laravel.com/docs/6.x/authentication#authenticating-users

look down to Additional Conditions

Add the additional condition to the login process.

When you use parse you are basically asking carbon to try and make something from a date input. There is not really a wrong answer.

Better to be more prescriptive and use createFromFormat and pass it the expected format. Carbon will then throw an exception if the date does not work

Test it with Tinker so that you know how it behaves

Thats not the behavior I see in tinker;

>>> Carbon\Carbon::parse('01/01/0019')
=> Carbon\Carbon @-61567603200 {#3110
     date: 0019-01-01 00:00:00.0 UTC (+00:00),
   }
>>> 

There may be some other fault

By the way;

The problem is that, if I give some false value (e.g. 01/01/0019), Carbon parsing does not throw an error

01/01/0019 is a perfectly valid date. Why should it throw an error?

It would help if "not working as expected" was explained better!

Letting everyone in, or letting noone in?

You have this route which is not protected at all

Route::get('/admin', '[email protected]')->name('admin');

See the asset helper docs https://laravel.com/docs/6.x/helpers#method-asset

You can configure the asset URL host by setting the ASSET_URL variable in your .env file. This can be useful if you host your assets on an external service like Amazon S3:

// ASSET_URL=http://example.com/assets

$url = asset('img/photo.jpg'); // http://example.com/assets/img/photo.jpg

It would help if "not working as expected" was explained better!

Letting everyone in, or letting noone in?

You have this route which is not protected at all

Route::get('/admin', '[email protected]')->name('admin');

Nope. Don't think so. Not if it needs to be http access to the image

You have not said what 'access' means. Depending on how you access the files now, you will probably have to change every view anyway

Assuming by "access" you mean display it on a web page?

Construct the image tag to point to the other domain.

eg

<img src="http://otheradmindomain.com/product/image.jpg"

suggest you create a config item that can store the protocol and domain of the other site. Then in blade;

<img src="{{ config('admin_domain') }}{{ $product->image }}" />

that way, you have one central place to hold the domain of the other site and you don't need to go hunting through loads of templates if it changes.

Deleting an asset requires the file system path not the URL

and Storage uses specific folders. instead, unlink the file (regular php)

    public function destroy(Brightstudent $brightstudent)
    {
        $image_path = public_path('images/' . $brightstudent->bright_student_photo);

        if (unlink($image_path)){
            return "file deleted";
        }else{
            return "not deleted";
        }

    }

or create a Storage disk that uses public/images

open the network tab in your browser and check if you are getting 301 or 302 redirects

This is not your problem, but beware using joins where you have identical column names in different tables. There can only be one winner. Not sure why you are using joins when you have eloquent relationships setup?

Deleting an asset requires the file system path not the URL

and Storage uses specific folders. instead, unlink the file (regular php)

    public function destroy(Brightstudent $brightstudent)
    {
        $image_path = public_path('images/' . $brightstudent->bright_student_photo);

        if (unlink($image_path)){
            return "file deleted";
        }else{
            return "not deleted";
        }

    }

or create a Storage disk that uses public/images

helpers like request() are super useful but not liked by some as it couples your code too closely to the Laravel framework. They prefer to inject all dependencies into the class.

its your with statement rather than the append that causes the extra query every time you load any user

If you are starting a new project, I can recommend pulling in

https://github.com/laravel-frontend-presets/tailwindcss

as all the auth scaffolding has been converted from Bootstrap

If you need the same functionality in two controllers, consider using a trait.

Review the last comment here https://github.com/laravel/framework/issues/27478 incase this is related

development mode should not matter. Your code runs every time in my project, except when down

Your app is not 'down' is it?

ok?

best you can hope for with shared hosting is to prepare all the files locally and then just upload them (complete with vendor folder) onto the remote server.

What?

clearly, no name on the premis table. So why is it in your query?

Then you say you want the type name what does that mean?

The cookies are only necessary for tracking session and authorising forms. You may not need either?

It has to be asked...

Do you have column name in the premis table ?

but it was throwing an error before, so certainly trying to write to the database. What did you change at that point?

Your public folder should be the document root so that you don't see lsapp/public in your urls

This is done by setting the document root in Apache for the website

I gave you the business logic earlier. You have had 2 days to think about it. Lets see your progress?

BTW, your retirement would have been one day ago if on my team.

make sure you change validation rules also

You cannot use a hash to search the database as you would need to check() every row individually.

MD5 is pretty insecure so this does not seem a good option.

Store the form layout also in the database then render it inside your show.blade.php file.

The slash means that the URL is relative to the root directory. Without it, it means it is in the same folder as the current page. Removal of the backslash will cause problems as the routes get longer, like /post/3/edit since your browser will think the assets are in the /3/ folder

You should try and use the route() and asset() helpers wherever possible, or make sure that your web server is pointing to the public folder (as it should be)

Any other structure is just being lazy

no, since this is a Get request, all parameters must be in the url

How does the router know where name ends and ID starts?

you need a placeholder in the route, eg

Route::get("{name}-{id}", '[email protected]')->name('product');

Now you can pass as abc-123

but the second parameter isnt the query parameter.

Anyway, thats not your issue. You are not chaining onto a query builder object.

¯\_(ツ)_/¯

I should know better by now.

You cannot paginate a collection, you need to paginate a query.

What does teachersRepository contain?

ps. Also, you have two parameters into the paginator?

https://laravel.com/api/6.x/Illuminate/Database/Eloquent/Builder.html#method_paginate

Adjust your query so that the items are not retrieved from the database in the first place rather than dropping them from the collection.

You need to understand where that time is being spent. Try using Laravel Debugbar.

or just write to the column and save it

public function unverify() 
{
    $this->email_verified_at = null;

    $this->save();
}

You also need the options inside a form select element !

Give your data a proper name. Swap the order of the pluck.

    public function create()
    {
        $categories = Category::pluck('ctg_name', 'id');

        return view('admin.blog.add_blog')->with('categories', $categories);
    }

Adjust the view

<tr>
          <td>Category</td>
          <td>
              <select>
              @foreach($categories as $key => $value)
                 <option value="{{ $key }}">{{ $value }}</option>
              @endforeach
              </select> 
          </td>
      </tr>

my tutorial

http://novate.co.uk/allow-user-to-choose-pagination-length-via-dropdown-laravel/

Yes, you should not have that get() statement in a scope (and thats got nothing to do with pagination)

You need to review indexes.

In your posts table make sure user_id and tag are indexed.

redirect is better. You should always avoid returning a view in response to a post/put/patch request

Also look at the abortif helper, hoŵever what you need to do is better handled in an authorisation policy

In your user model, this should be called group

public function users() {

    return $this->belongsTo('App\Group', 'user_id');
}

my tutorial

http://novate.co.uk/allow-user-to-choose-pagination-length-via-dropdown-laravel/

use spatie media library. its so easy to use and automatically creates each image with a relationship back to the model