whatsapp share link for website

December 22, 2021 in Tips and Tricks

auth check with guard

if (Auth::guard('api')->check()) {
        $message='Invitation click successfully.';
        //return redirect()->route('admin.dashboard');
        $user = Auth::guard('api')->user();
        $success['user_id']=$user->id;
        
        $success['invitation_id']=$success['id'];
        $success['click_status']='1';
        $success['target_user_id']= $success['user_id'];

        $data = DB::connection($lang)->table('cal_invitation_click')->where('invitation_id',$success['id'])->where('target_user_id',$success['user_id'])->get();
        $success['count']=count($data);        
        if($success['count'] == '0'){
        $success['click_id']= DB::connection($lang)->table('cal_invitation_click')->insertGetId([
          'invitation_id' =>  $success['id'],
          'source_user_id' =>  $success['source_user_id'],
          'target_url' =>  $success['target_url'],
          'click_status' =>  $success['click_status'],
          'target_user_id' => $success['user_id']
      ]);
       } 

December 22, 2021 in Tips and Tricks

Uncaught (in promise) DOMException: Failed to load because no supported source was found.

Automatically playing audio and video on the web is a powerful capability, and one that’s subject to different restrictions on different platforms. Today, most desktop browsers will always allow web pages to begin <video> or <audio> playback via JavaScript without user interaction. Most mobile browsers, however, require an explicit user gesture before JavaScript-initiated playback can occur. This helps ensure that mobile users, many of whom pay for bandwidth or who might be in a public environment, don’t accidentally start downloading and playing media without explicitly interacting with the page.

It’s historically been difficult to determine whether user interaction is required to start playback, and to detect the failures that happen when (automatic) playback is attempted and fails. Various workarounds exist, but are less than ideal. An improvement to the underlying play() method to address this uncertainty is long overdue, and this has now made it to the web platform, with an initial implementation in Chrome 50.

A play() call on an a <video> or <audio> element now returns a Promise. If playback succeeds, the Promise is fulfilled, and if playback fails, the Promise is rejected along with an error message explaining the failure. This lets you write intuitive code like the following:

var playPromise = document.querySelector('video').play();

// In browsers that don’t yet support this functionality,
// playPromise won’t be defined.
if (playPromise !== undefined) {
  playPromise.then(function() {
    // Automatic playback started!
  }).catch(function(error) {
    // Automatic playback failed.
    // Show a UI element to let the user manually start playback.
  });
}

In addition to detecting whether the play() method was successful, the new Promise-based interface allows you to determine when the play() method succeeded. There are contexts in which a web browser may decide to delay the start of playback—for instance, desktop Chrome will not begin playback of a <video> until the tab is visible. The Promise won’t fulfill until playback has actually started, meaning the code inside the then() will not execute until the media is playing. Previous methods of determining if play() is successful, such as waiting a set amount of time for a playing event and assuming failure if it doesn’t fire, are susceptible to false negatives in delayed-playback scenarios.