ftiersch

1. Does it work if you comment out the VerifyCsrf middleware in the Kernel.php?
2. If yes, do your sessions work properly? CSRF saves the token in the session so if they don't work it won't find the token to compare. What sessiondriver are you using?

You have a table "messages" with

• id
• from_user_id
• to_user_id
• message
• created_at

and a view where you display all the messages ordered by "created_at". Depending if the "from_user_id" is the same ID as the user that is logged in you can then give it a different color for example to make it clear which message belongs to who (like in whatsapp or other messengers).

Sure, easy:

1. Fix all bugs you encounter
2. Program any new feature you need

That's about all the help you need with the information available.

First result on googling the error:

https://stackoverflow.com/questions/3872555/fatal-error-class-ziparchive-not-found-in

1. You validate for a field called "avatar" which doesn't exist. Also you're using request()->file('avatar').
2. name="image/*" doesn't make sense. I'm not sure which name the browser will use.

Probably because your field is called "avatar" but you check for "avatar_path" ;-)

@MOUKBEL - If you want to send it via AJAX you can send a header with the CSRF token. I think the header is called X-CSRF-TOKEN and works exactly the same way as csrf_field :)

Oh yeah...

! request()->input('password') === ''

request()->input('password') !== ''

Second one makes more sense :) Or even better:

request()->filled('password')

You'll have to decide which way you want to use... update() or save() :)

How about something like this:

$user->fill(request()->except('password'));

    if (! request()->input('password') === '')
        {
            $user->password = bcrypt(request()->input('password'));
        }
$user->save();

I don't really understand what you want to achieve or what your problem is.

Exactly what @tray2 is saying. It's good that you care about security but that's the whole purpose of HTTPS so no one can intercept the communication and read it.

Otherwise you would have to encode the whole thing in JavaScript. But since your JavaScript is per definition readable from the browser a hacker can still read it.

I think the "displayBoxes is not defined" error could be because the select fires an onchange event for the "initializiation". So basically it fires that event right away but you add the script file only afterwards which means at the moment of the event the function is not there yet.

Try adding the script.js in the head of your HTML or add the onchange event listener in the JavaScript after the function has been defined.

Where are you adding the script.js file to your code? in the HEAD tag or somewhere else?

First my question:

Why are you encoding the data?

You cannot cache routes with closure functions. So your caching fails -> you still have the old version of your routes in the cache -> the new route doesn't exist and throws a 404 :)

Foreign Key fields need to have exactly the same format as the columns they reference. So if you use bigIncrements in your add_years table you need to use a bigInteger for your year_id.

Write a middleware where (if user is logged in) you check the percentage. If it's below 100 redirect the user to the desired page. Add that middleware to every route except for "edit_profile".

Blade just renders to normal HTML...

1. Have you added script tags around it?
2. Have you included the rest of the ads library?

What's the name of your tables? One time you use "Purchases", one time "purchases". Is that the problem?

Yes, you get that error message because you are still using $share->id inside of your commented out code. Making an HTML comment out of it doesn't stop the PHP functionality from being executed. Remove the whole comment.

Where are you checking that? The $request variable shouldn't be null... except of course you're not checking it during a request but during something like a worker call or an artisan command

I don't think that quite exists... But what I could think of would be fill()... So something like:

$food = App\Food::find($id);

$specificFood = new $food->class;
$specificFood->fill($food->all());

(not quite sure if "all" works on models but I'm sure there is a method that gives you an array of all attributes :))

I wouldn't look for the error in the javascript if it's not there, but in the User model :) Do you have the $hidden property set?

First you have to add a parameter to your edit URL

Route::get('edit/{id}', '[email protected]');

Second you have to limit the URL you get in your controller

public function edit(Request $request, $id)

    {
       
        $shares = Url::findOrFail($id);

Third maybe you have to change your route() call

{{ route('shares.edit', ['id' => $share->id]) }}

The formrequest returns a rules array...

Why not just this:

return Validator::make($data, app(StoreUser::class)->rules());

You have to convert it to JSON... right now it literally says [object Object] there :)

{{ json_encode($clients) }}

Either you program the function that whereHas does yourself (which is a subselect) or you use another join to add another where condition. Probably your documents have a connection to "category" so basically you just add another join that adds that connection and then you can have your "where('category.type', 'revenue')" condition

whereHas only works for Models, joining works on tables. So what Eloquent does is use the where syntax because it thinks you want to check for the column "has" (like you could do wherePrice(10) to check the "price" column).

So if you need to use a join instead of a whereHas in your original query you need to put that where differently and cannot use whereHas.

@TECHGURU - To be honest I haven't used phpmyadmin in years. Usually I use something like HeidiSQL (or SequelPro if you are on a Mac) and then connect to the database through an SSH tunnel for security reasons.

But if you make sure that your phpmyadmin is password secured I don't see a problem with it.

You need more than one relationship for that.

First relationship is POSSIBLE SIZES / COLORS for a shirt (and probably even the combination of both). So "this shirt is available in red (S, M, L), blue (M, L, XL)" and so on...

Second thing (I'm gonna assume it's about an online shop) is the choice a user made. So user X chose shirt 15 in green with size XXXXL (probably a customer from USA ;-)). That's a second relationship you need (something like a cart).

If you have set your document root to be in /my_project/public the webserver starts looking there for your subfolders (that's why it's called "root"). So either you need to put your phpmyadmin into your public directory or you need a vhost for phpmyadmin with a different root directory.

I'm confused... do you get 419 or 404?

Either way... add @csrf (if you have Laravel 5.8) right after your form HTML tag.

Exactly what @vilfago says.

You probably have objects of the type "Service" in your $services array. So if you @foreach twice over that you get the title in your $service variable. And a string (title) doesn't have another variable "title".

I would guess your $services array doesn't have "rows" underneath it... you'll have to structure your arrays that way if you want to use two foreach loops

The backtick is important :)

The problem is, that MySQL interprets users u literally as the tablename... so it doesn't rename your table for the query (that would be users u - see the difference?).

Either you just use "users" everywhere in your query or I think it should work with DB::raw().

->table(DB::raw('users u'))

Probably the joined tables have a user_id column too that's null. Since every key can only be used once the latest value "wins" and overwrites the earlier ones.

So your "user_id" key will first be (for example) the 3 of your concern_user table and then administrative_points comes along and overwrites that value to null.

Use select() to select specifically which columns you need from which table.

class MyController {
    public function index() {
        $myArray = ['test' => 'Hello'];

        return view('index', ['myArray' => $myArray]);
    }
}

With this you can use it with $myArray in your blade view.

I have no idea what you are asking.

The error isn't in the JavaScript... a 500 response code means there is an error happening on the server. Check your logs to see the error message otherwise it's only guessing...

The error is on your server side. Check your Laravel logs for the error message.

Try this:

return response()->json(['message' => 'task was successful']);

but not sure if that is the source of the error.

Yes, because that's not how arrays work :)

$input['inventory'][0]['amount']

But you can use Laravel functions for that.

request()->filled('inventory.0.amount');

Should do what you need.

You called your variable in the array $users...

return view('userlist',['$users' => $users]);

The key needs to be 'users', then you can use $users in the blade.

Yes, for the user that's the best way :)

But be careful with events. If you handle them via a queue on a worker server the user might not actually be there in the event! Depends on your configuration and server structure :)

Thanks for the shout out ;-)

@foreach ($users as $user)
    // display one "user" here
@endforeach

@for($i = 3 - $users->count(); $i > 0; $i--)
    // display one "space filler" here
@endfor

That should do it :) Just dynamically start the for() loop where you need it to start. If you want a different number than "3 per row" you can just change the 3 to 5 for example.

@MUNAZZIL - Man, are you even READING the questions? Your answer has nothing to do with it...

@splendidkeen What does your "meeting" method do? Did you write your own collection logic there?

No... I mean your VueJS code that actually sends a request to the backend

That code doesn't help unfortunately, we need the code that reacts to your messagesent event :)

because you concatenate strings in javascript with +, not . ;-)

You were in PHP brain :)

I think you posted the same code twice :)

But I guess you add the message instantly to the array of messages (in the code that's missing). To get the created_at you need to send it to the server first and then add the result because laravel creates that timestamp for you when it adds your message to the database.

@BOBBYBOUWMANN - Ah crap, google showed me a third party page :D Thanks!

Still not the right use case here