bobbybouwmann

Printers like that normally work through a local network or via a connection via some cable. You need to connect the printer to your server if you want to use it like that.

The tokens are saved by default in the session which is saved on the server itself. You can easily update this the database, so you won't have this issue anymore

You can find more info here: https://laravel.com/docs/6.x/session#driver-prerequisites

Basically you need to run

php artisan session:table
php artisan migrate

And then update your .env to use database as the SESSION_DRIVER.

Most things have stayed the same between releases. There might be some other names for things, but most of it is the same. At least, no features have been removed ;)

The series is still very relevant, even if you work with a newer framework version.

I bet Jeffrey will create a new series for Laravel 7 since that one has a lot of new features ;)

I'm not sure what you mean by "secretive"...

It depends a bit on your system, but normally you just provide an array with available dates or you do an ajax call to check if the date is available or not.

You can make this work using whereRaw, but I understand that you want to reuse the calculated field. I'm not sure if that is possible at all.

Did you try the raw query, so without Eloquent?

I would probably just create a JSON file somewhere and do something like this

$data = json_decode(file_get_contents('data/json-data.json'));

You can set this data in your class and use it from there ;)

$reportables = Reportable::all();

$count = $reportable->groupBy(function ($reportable) {
    return $reportable->reportable_id . $reportable->reportable_type; 
})->count();

You can also use countBy to group them by a key and get the count per ke

Documentation: https://laravel.com/docs/6.x/collections#method-countBy

You need to create a migration and tell which field should be the primary key

Schema::create('your-table-name', function (Blueprint $table) {
    $table->string('identifier');
    $table->string('column')->nullable();
    $table->timestamps();

    $table->primary('identifier'); // This set the primary key which makes it unique as well
});

Most things have stayed the same between releases. There might be some other names for things, but most of it is the same. At least, no features have been removed ;)

The series is still very relevant, even if you work with a newer framework version.

I bet Jeffrey will create a new series for Laravel 7 since that one has a lot of new features ;)

Sure, why wouldn't it be possible ;)

Here is some more info on that: https://stackoverflow.com/questions/4813727/is-string-or-int-preferred-for-foreign-keys

@burimb No problem ;)

You can find the error in your storage/logs directory. Just a 500 error is also not understandable for us.

You say everything is configured correctly. Can you confirm that you have the private and public keys that are needed for passport?

So to be clear. Whenever you remove an image you also want the image_id set to empty in your articles table right?

This sounds like a foreign key constraint issue.

You can find the error in your storage/logs directory. Just a 500 error is also not understandable for us.

You say everything is configured correctly. Can you confirm that you have the private and public keys that are needed for passport?

You only post the project_id, you still need to fetch it

$product = Product::find($request->input('product_id'));

$balances = $product->product_n->balance;

insertOrIgnore is basically bypassing the model methods and directly inserting a model into the database using a regular query. Where create and save also checks for mutators and casts.

If you want it to be JSON I would recommend you to use the normal way of creating a model using the firstOrCreate method which basically does the same thing. It creates it if it doesn't exist or fetches it when it exists.

Can you tell me why you use insertOrIgnore here?

Yeah, you can fork the package, alter the migration, model, and code and then everything should work for you ;)

Your form looks correct, but the URL in dropzone itself is incorrect. Can you post what you have now?

You only post the project_id, you still need to fetch it

$product = Product::find($request->input('product_id'));

$balances = $product->product_n->balance;

I really don't understand your question..

First of all, editing the vendor files is not a good idea. If you run composer update your changes are gone as well! In general, it's better to improve the package by sending in a pull request that add the functionality for the user_id.

Anyway, it seems that the packages don't store any user_id so you won't be able to access it. It also has a fixed table, so it seems that you won't be able to store the user_id because there is no column for it.

What package are you using?

I would personally use another package like https://github.com/spatie/laravel-activitylog

What have you tried? It seems that you just copied this from somewhere and use that so far...

Here is a tutorial you can follow for Laravel: https://www.itsolutionstuff.com/post/laravel-6-dropzone-image-upload-tutorialexample.html

The middleware is only there to set a certain airlock attribute. If that is not there, you're not logged in.If you remove the middleware everyone can access the route.

Then in your controller you can decide what to fetch

if (auth('airlock')->check()) {
    $videos = $this->getPremiumVideos();
} else {
    $videos = $this->getFreeVideos();
}

This should work ;)

AuthenticatesUsers is a trait. All methods of the trait are copied to the class, in this case, the controller. However, you can override the methods from the traits in your class.

So if you want to override the showLoginForm method, you can do something like this

namespace App\Http\Controllers\Auth;

use Illuminate\Foundation\Auth\AuthenticatesUsers;

class LoginController extends Controller
{
    use AuthenticatesUsers;

    public function showLoginForm()
    {
        // You can do here whatever you want because you override the method.
    }
}

This works for all methods in the AuthenticatesUsers trait.

It seems that you're using the pagination functionality in your view. However, the packages relationship is not a pagination object.

You have two options here. Either removing the {{ $packages->links() }} call because you don't want to use pagination. Or make the relationship a paginated object

return view('message.index')->with('messages', $user->messages()->paginate());

Laravel Socialite is built for this. This way you get a token from the user and you can use that to verify the user against Twitter. In general, you should retrieve the token using socialite and it shouldn't be posted to you.

Documentation: https://laravel.com/docs/6.x/socialite

A few months ago someone asked this as well! The best reply from there should put you in the right direction

Thread: https://laracasts.com/discuss/channels/laravel/what-is-queue-connection-name-and-what-is-the-use-of-queue-name-connection

I can highly recommend you to use this package: https://github.com/spatie/array-to-xml

You can use the get method of the collection for this

$value = $collection->get('item');

Documentation: https://laravel.com/docs/6.x/collections#method-get

But you're running it through InertiaJS which is doing an ajax post request for you in the browser whenever you click on the button. Because of that, you're not allowed to just go to another website.

Can you post the full exception here? It should say which line is failing.

Anyway, I think the error is in here:

$mimetype = $image->getClientMimeType(); //Get MIME type

You only create this property in the iff statement. If you get past the if statement without creating the variable, updating the picture won't work as well.

Instead, you need to do this

$data = mediaLibrary::findOrFail($id);

if ($request->hasFile('image')) {
    if ($request->file('image')->isValid()) {
        $image = $request->file('image');
        $extension = $image->getClientOriginalExtension();//Getting extension
        $originalname = $image->getClientOriginalName();//Getting original name

        if(file_exists($data->filename)) {
            unlink($data->filename);
        }
                        
        $path = $image->move('uploads/media/mainMedia/', $originalname);
        $imgsizes = $path->getSize();
        $data = getimagesize($path);
        $width = $data[0]; 
        $height = $data[1];
        $mimetype = $image->getClientMimeType();//Get MIME type

        $data->mime = $mimetype;
        $data->imgsize = $imgsizes;
        $data->original_filename = $originalname;
        $data->extension = $extension;
        $data->width = $width;
        $data->height = $height;
        $data->filename = $path;

        $data->save();
    }
}

Do you see and understand the difference? The property are now always available. In your example this is not the case!

You can use the get method of the collection for this

$value = $collection->get('item');

Documentation: https://laravel.com/docs/6.x/collections#method-get

From where do you call the Redirect::away call in your controller. It sounds to me that you're doing this in your frontend. However, your frontend is not allowed to redirect you. Instead, you need to send the payment url to the frontend and replace the URL or open it in a new tab. A redirect won't work here.

redirect()->to($payment->getRedirectUrl()) should work as well ;) (At leas that is what I use with Mollie)

This really is an annoying issue, believe me!

Normally you get this message when there is a , or in your email address which makes it invalid. Those email addresses normally pass the email validation but are not correct for Swift_Message that sends the email.

So my advice would be checking if the email contains any character that seems wrong like a comma or a space.

This really is an annoying issue, believe me!

Normally you get this message when there is a , or in your email address which makes it invalid. Those email addresses normally pass the email validation but are not correct for Swift_Message that sends the email.

So my advice would be checking if the email contains any character that seems wrong like a comma or a space.

It seems that you're using the pagination functionality in your view. However, the packages relationship is not a pagination object.

You have two options here. Either removing the {{ $packages->links() }} call because you don't want to use pagination. Or make the relationship a paginated object

return view('message.index')->with('messages', $user->messages()->paginate());

AuthenticatesUsers is a trait. All methods of the trait are copied to the class, in this case, the controller. However, you can override the methods from the traits in your class.

So if you want to override the showLoginForm method, you can do something like this

namespace App\Http\Controllers\Auth;

use Illuminate\Foundation\Auth\AuthenticatesUsers;

class LoginController extends Controller
{
    use AuthenticatesUsers;

    public function showLoginForm()
    {
        // You can do here whatever you want because you override the method.
    }
}

This works for all methods in the AuthenticatesUsers trait.

I can highly recommend you to use this package: https://github.com/spatie/array-to-xml

This is a basic one-to-many relationship, right? You create multiple tokens in the database that are connected to the user. For authentication, you just check if the token exists and you know what user is logged in.

That doesn't make any sense to me. It's working fine for me at least. Do you have a like a middleware that is alternating the response?

@booni3 Yeah, that is the way to go. To be sure, you can build in a check if the exists or not. For the rest, this looks pretty good ;)

I would probably just fetch all records and use the collection methods to get the correct count and groups ;)

You need to run some commands in your command line to get it all up and running. I find this a very good video to follow: https://www.youtube.com/watch?v=nxBmmcCjbho

Let me know if you have any trouble

If you use the correct relationship you can check against it using the exists method

$user->profile()->exists(); // true or false

It seems that the path is incorrect. You need to point to where you stored the file. If this is the public directory use this

$pdf->setSourceFile(public_path('/pdfs/example.pdf'));

If you stored it in the storage directory use this instead

$pdf->setSourceFile(storage_path('/pdfs/example.pdf'));

Well, you get the idea ;)

Yeah this is fine in 90% of the cases. You might need to upgrade the server if you get a lot of traffic or if the application is doing a lot of stuff on the background. But this should be fine to start with for sure ;)

Well, that is correct, because after clicking the button you are verified and redirected to the home page. Or in your case the dashboard. The verified page itself doesn't exist by default.

If you want to redirect to another page, you need to override the show method of the app/Http/Controllers/Auth/VerificationController.php controller. Something like this

class VerificationController extends Controller
{
    use VerifiesEmails;

    protected $redirectTo = RouteServiceProvider::HOME;

    public function __construct()
    {
        $this->middleware('auth');
        $this->middleware('signed')->only('verify');
        $this->middleware('throttle:6,1')->only('verify', 'resend');
    }

  public function show()
  {
     // return your view here
  }
}

It seems that the path is incorrect. You need to point to where you stored the file. If this is the public directory use this

$pdf->setSourceFile(public_path('/pdfs/example.pdf'));

If you stored it in the storage directory use this instead

$pdf->setSourceFile(storage_path('/pdfs/example.pdf'));

Well, you get the idea ;)

If you use the correct relationship you can check against it using the exists method

$user->profile()->exists(); // true or false

Have you tried a different status code to see if that works? 409 is a really specific code that the resource is busy and is not used often.