deansatch

Well yes it just sounds like cache. Use versioning. It isn’t difficult and will take you less than a minute to set up.

https://laravel.com/docs/7.x/mix#versioning-and-cache-busting

Well yes it just sounds like cache. Use versioning. It isn’t difficult and will take you less than a minute to set up.

https://laravel.com/docs/7.x/mix#versioning-and-cache-busting

So if you load the page http://laravel6.test/css/app.css does it show what you want??

If not does this show it http://laravel6.test/css/app.css?v=1

It is difficult to understand exactly what you are trying to do but I think this might be it?

return $user->directs()->with('user')->get();

Also why do you want a perfectly good line of code which returns the correct results to be replaced with a different line of code that has an apparently different meaning?

Your user model relationship looks wrong. Should it not be this?

 public function directs()
    {
        return $this->hasMany('App\Sponsor' );
    }

sorry...remove the brackets.

return $user->directs;

You don't need ->with('user') as directs() is the users.

return $user->directs();

//should return user with 'directs' (which are also users)

I wouldn’t say I was attacking you. I was just recommending trying a workflow that the majority of Laravel devs use as it would solve the issue you now have. Take it or leave it, but don’t take it to heart

I know most people like to work they way they have always worked and changing is a nightmare, but writing your own migrations is just as 'visual' as any other way really and it would be well worth your time to use this problem as an excuse to start doing it that way. It will make life easier on any dev that might come in on one of your projects if it is done in a more standardised way, as well as giving you more opportunities to work on other projects with devs/agencies that work this way too.

Migrations would be perfect for this. Any table changes made during development if done via migrations would then be available to run on deployment. So you make your local changes, push to repo, deploy however and run migrate. If you are using envoyer you can set it to run migrate on every deployment

I haven’t used table plus for a while but I’m pretty sure you can export structure only

Like nfms I assumed you would export and import. Why would you “sync” two databases like that? That sounds no different to simply sharing the same dB credentials on local and remote???

Take a look at table plus. The limitations of the free version might not even be an issue for you

Not the right way to do it. You shouldn’t need to open it up completely.

oh...well probably the most popular although not free is https://tableplus.com/ - price is very low though. You can also use it for free with some limitations (2 tabs max etc...) https://tableplus.com/blog/2018/10/tableplus-free-vs-paid.html

https://www.sequelpro.com/

chown the storage folder

It won’t.

why don't you just use the ID? You can prepend the "PER-" to your output. Why the leading single zero? Are there only going to be a maximum of 99?

You should be able to use laravel to provide the api endpoints for a gatsby site to pull from, yes.

Look at this - your laravel project would basically be your headless cms https://www.gatsbyjs.org/docs/sourcing-from-private-apis/

It takes a bit more fiddling to get things pointing to the right places on shared hosting. Look...

https://laravelarticle.com/deploy-laravel-on-shared-hosting

your two where statements seem like they wouldn't work well together anyway - one or the other it seems. Here is one anyway which should help in doing the other

 ->where('customer_id',$customer_id)
		->whereRaw(" DATE_FORMAT(created_at,'%Y-%m-%d %H:%i') >= ? ", [$fromDate]);
        }

or maybe this...

 ->where('customer_id',$customer_id)
		->where(\DB::raw("(DATE_FORMAT(created_at,'%Y-%m-%d %H:%i'))"), ">=", $fromDate);
        }

assuming the credentials are correct try 127.0.0.1 instead of localhost

<script>
    $(document).ready(function(){
        $(".custom-select").change(function(){
            var OrderSelection = $(this).val();
		//or for text instead of value
		 //var OrderSelection = $(this).find("option:selected").text()
            alert("You have selected - " + OrderSelection);
        });
    });
</script>

<script>
    $(document).ready(function(){
        $(".custom-select").change(function(){
            var OrderSelection = $(this).val();
		//or for text instead of value
		 //var OrderSelection = $(this).find("option:selected").text()
            alert("You have selected - " + OrderSelection);
        });
    });
</script>

use Illuminate\Support\Str;

public function validateArticle() {
 $validate = request()->validate([
      'title' => 'required',
      'excerpt' => 'nullable',
      'body' => 'nullable'
    ]);

    $validate['slug'] = Str::slug($validate['title'], '-');

return  $validate;
 }

That code doesn't upload an image - you need to show more code

use Illuminate\Support\Str;

public function validateArticle() {
 $validate = request()->validate([
      'title' => 'required',
      'excerpt' => 'nullable',
      'body' => 'nullable'
    ]);

    $validate['slug'] = Str::slug($validate['title'], '-');

return  $validate;
 }

if you dump $news are you sure they all have a slug? What you have should work provided all articles in the loop have an id and slug.

public function index() {
    $news = News::latest()->get();
	dd($news);

    return view('news.index', ['articles' => $news]);
  }

if you dump $news are you sure they all have a slug? What you have should work provided all articles in the loop have an id and slug.

public function index() {
    $news = News::latest()->get();
	dd($news);

    return view('news.index', ['articles' => $news]);
  }

do your query as normal and set the format on your output:

$model = YourModel::all();

$formattedDate = \Carbon\Carbon::parse($model->created_at)->format('Y m d');//any format you watn

Did you restart Apache?

Did you restart Apache?

This is beyond the scope of a simple forum question - you need a full tutorial unless you are just asking for a general method, which would basically be...

1. if your select dropdown is populated from your database, make sure to include the hex code when sending it to your view
2. use radio buttons instead of a select dropdown
3. use css and js to replace the default radio button with a circle and set each colour to match the hex code.

Use something like this to create your radio styling - add border-radius: 50%; on the label span to make them circles https://codepen.io/wildbeard/pen/eZZPZr

I'm assuming you are trying to do something like this:

https://i.pinimg.com/originals/ce/fe/c0/cefec04405d1810f566a1eeff44b850c.png

This is beyond the scope of a simple forum question - you need a full tutorial unless you are just asking for a general method, which would basically be...

1. if your select dropdown is populated from your database, make sure to include the hex code when sending it to your view
2. use radio buttons instead of a select dropdown
3. use css and js to replace the default radio button with a circle and set each colour to match the hex code.

Use something like this to create your radio styling - add border-radius: 50%; on the label span to make them circles https://codepen.io/wildbeard/pen/eZZPZr

I'm assuming you are trying to do something like this:

https://i.pinimg.com/originals/ce/fe/c0/cefec04405d1810f566a1eeff44b850c.png

For reasons I won't go into, I have had to make the email column on the users table nullable. My question is, is this still safe if there are rows of 'users' with email and password both set as null (which should never be able to login - dead user accounts basically).

I feel the validation wouldn't let me login without an email and at least some sort of string for a password but just wanted some reassurance on this one if anyone is 100% sure it is still safe

Thanks

That is how variables and views work.

Do you mean you want to create a session variable to store a dynamically generated value?

// store the value
request()->session()->put('key', 'value');

$view_variable = request()->session()->get('key');

That is how variables and views work.

Do you mean you want to create a session variable to store a dynamically generated value?

// store the value
request()->session()->put('key', 'value');

$view_variable = request()->session()->get('key');

if your route calls a method which doesn't return anything it just simply won't return anything other than a white screen - it will still process stuff, just never actually present it to the user (unless the download is directly within the same method - calling it from a different method is the issue).

You probably don't need to return there...if you return a view after your if statement it might present the download along with that view

No need for the subquery + your < and > were the wrong way round:

$now = Carbon::now('Asia/Kolkata')->toDateTimeString();
$qry = Posts::where('status', 'live')
	->where('start', '<=', $now )
	->where('expiry', '>=', $now)
         ->get();

That should work although in your example assuming 12:01am is start and 11:59pm is expiry. Also, are you db dates datetime?

ok, maybe it is because you aren't returning it:

if ('apotek' == $data['txtCabang']) {
            return self::exportApotek($begin, $end, '5044', 'AP5044');
        } else {
            return self::exportDokter($begin, $end, '5135', 'PK5135');
        }

ok, maybe it is because you aren't returning it:

if ('apotek' == $data['txtCabang']) {
            return self::exportApotek($begin, $end, '5044', 'AP5044');
        } else {
            return self::exportDokter($begin, $end, '5135', 'PK5135');
        }

Why not just wrap the whole thing in an if statement?

if( strlen($search) > 0 ){

	//your query

}else{

	$posts = 'no posts';

}

Yes, you can't set a php cookie value as true or false. False would delete the cookie. 1 or 0 as a string is correct behaviour. If you MUST pass a boolean value, handle it like this...

    Cookie::queue(Cookie::forever(request()->name, request()->value ? '1' : '0'));

Yes, you can't set a php cookie value as true or false. False would delete the cookie. 1 or 0 as a string is correct behaviour. If you MUST pass a boolean value, handle it like this...

    Cookie::queue(Cookie::forever(request()->name, request()->value ? '1' : '0'));

Sorry, I still don't understand what you mean

That should work so it must be how you are passing the values from your ajax to your cookie function - can you share more code?

This seems like a new issue so possibly best starting a new thread with full explanation. Not sure exactly what you mean with this one but the second code block looks wrong and should probably be...

$q->whereHas('comments', function ( $q ) use($search, $sort){
                        $q->where('content',  'like', '%'.$search.'%' );
                        if($sort == 'answered'){
                            $q->where('answered', '=', 1);
                        }
                        if($sort == 'new'){
                            $q->where('answered', '=', 0);
                        }
                })

This will base it off the headers so if that is ok (i.e. content type is application/json)...

if(request()->isJson()){
	//it is json, continue
}

This will base it off the headers so if that is ok (i.e. content type is application/json)...

if(request()->isJson()){
	//it is json, continue
}