piljac1

@larsonator Careful, an auction with a winning bid doesn't mean it's over. It can be seen as the current winning bid as long as the auction hasn't expired.

There are multiple solutions, but I would add a winning_bid_id foreign key to the auctions table as you proposed. Your current code will probably be fine for a while, but as the database entries multiply, it will get slower and slower. As for the how can I update the column ? question, simply update it each time a new bid is submitted (that takes into account that you have a solid validation process to avoid data inconsistency).

There are multiple solutions to this, but if you want to keep everything server side, you could use a {modelClassName}.{id} notation as option values and explode it server side.

Example:

<select name="eventdateable" class="form-control" id="eventdateable_id">
    <option></option>
    @foreach($mergedFamily as $mf)
        <option value="{{ addslashes(get_class($mf)) . '.' . $mf->id }}">{{ $mf->name }}</option>
    @endforeach
</select>

P.S. I know HTML4 is old, but if you want to support it, this won't work because backslashes are not authorized in the older spec. You would need to replace addslashes by class_basename to only get the model class name without the namespace. Then you would append the namespace on the server side when processing your form data.

After doing that, you could explode the value contained within your eventdateable request value and collect the desired info:

// Of course you could (should) add validation to avoid errors if the request value is null or not well formatted
$eventdateablePair = explode('.', $request->eventdateable);

// Your eventdateable_type
$eventdateableType = $eventdateablePair[0];

// Your eventdateable_id
$eventdateableId = $eventdateablePair[1];

When assigning the eventdateable_type to your model (and then your database), you might have an escaping issue. If that's the case, add another addslashes to your existing front-end logic, or add it in the back-end if you want.

@sinnbeck is right you know ;) Thanks in advance (and thanks @sinnbeck)

There are multiple solutions to this, but if you want to keep everything server side, you could use a {modelClassName}.{id} notation as option values and explode it server side.

Example:

<select name="eventdateable" class="form-control" id="eventdateable_id">
    <option></option>
    @foreach($mergedFamily as $mf)
        <option value="{{ addslashes(get_class($mf)) . '.' . $mf->id }}">{{ $mf->name }}</option>
    @endforeach
</select>

P.S. I know HTML4 is old, but if you want to support it, this won't work because backslashes are not authorized in the older spec. You would need to replace addslashes by class_basename to only get the model class name without the namespace. Then you would append the namespace on the server side when processing your form data.

After doing that, you could explode the value contained within your eventdateable request value and collect the desired info:

// Of course you could (should) add validation to avoid errors if the request value is null or not well formatted
$eventdateablePair = explode('.', $request->eventdateable);

// Your eventdateable_type
$eventdateableType = $eventdateablePair[0];

// Your eventdateable_id
$eventdateableId = $eventdateablePair[1];

When assigning the eventdateable_type to your model (and then your database), you might have an escaping issue. If that's the case, add another addslashes to your existing front-end logic, or add it in the back-end if you want.

I agree with @snapey

It makes no sense to me that every foreign key use cases would imply that they should never be null. @snapey gave some excellent examples. I'm waiting for your point of you @bugsysha because I feel like your reasoning might make me understand your side. This is an interesting debate.

As far as I know, this subject has been discussed, but never implemented (at least since summer 2019 for sure).

The only way to accomplish what you want for now would be to create two separate notifications.

Is it possible to detail what you're trying to accomplish exactly. With the info you gave us, we could interpret it many ways. Are you asking if it is possible to validate a field based on an other on form submit ? Are you asking how is it possible to show an error in "real time" for Segment Name when an Industry Name is selected ? Please elaborate. Thanks !

@fabriciog I tried your code and it works as expected, but if you want 42% based on 42.857142857143%, you should use the floor function instead.

I know that you're using booleans, but booleans are represented with 1 and 0 (TINYINT) in the database. You're sending true as a string parameter, which will not match 1. Try replacing your true get params with 1, or add this logic to all your boolean fields in your query builder:

$request['vegan'] == 'true' ? 1 : 0

I know that you're using booleans, but booleans are represented with 1 and 0 (TINYINT) in the database. You're sending true as a string parameter, which will not match 1. Try replacing your true get params with 1, or add this logic to all your boolean fields in your query builder:

$request['vegan'] == 'true' ? 1 : 0

Replace your true strings by 1 and it should solve your issue. If it doesn't, take out the ->get() from your Recipes query and after you've done that, use dd($recipes->toSql(), $recipes->getBindings()) to obtain the generated SQL query and bindings passed to it. If the query looks ok, replace ? in the query with your bindings and try to adjust them until you get desired results. Once you've done that, you'll know what part of your code is incorrect.

Main differences between web and API routes:

1. API routes are prefixed with /api

2. API routes are throttled to avoid abusive numbers of requests in a short sequence

3. API routes are stateless, which means:

Stateless means there is no record of previous interactions and each interaction request has to be handled based entirely on information that comes with it.

In your Reservation model, get rid of the "s" in the locations relation :)

Edit : @tisuchi's got a point. Pass the ID to your route and use it to associate.

Also, in your store form, your select is missing a name (type). So your $request->get('type') will return null.

Also, you could just use the $request->type nomenclature to shorten things up.

So you want to get rid of undefined values and keep [2:"5", 3:"4"]or do you wish to only keep [2:"5"] for example ?

If you want to get rid of the undefined items, use an Object instead of an Array. Arrays start from 0, so if for example your IDs would be 75 and 76 instead of 2 and 3, you would have 75 undefined values before the 75 key.

Changing your qnt to an Object would give you {2: "5", 3: "4"}. If you wish to convert the object to an Array afterwards, you can use Object.entries(form.qnt) and it will output :

[
    0: [0: 2, 1: "5"],
    1: [0: 3, 1: "4"]
]

So you want to get rid of undefined values and keep [2:"5", 3:"4"]or do you wish to only keep [2:"5"] for example ?

If you want to get rid of the undefined items, use an Object instead of an Array. Arrays start from 0, so if for example your IDs would be 75 and 76 instead of 2 and 3, you would have 75 undefined values before the 75 key.

Changing your qnt to an Object would give you {2: "5", 3: "4"}. If you wish to convert the object to an Array afterwards, you can use Object.entries(form.qnt) and it will output :

[
    0: [0: 2, 1: "5"],
    1: [0: 3, 1: "4"]
]

Not sure what you're trying to accomplish exactly, but you should use query builders instead of raw SQL

Example (based on your code block) :

DB::table('table_name')
    ->whereIn('iid', $data)
    ->whereIn('iv_status', ["N", "Y", "A"])
    ->get();

You can get rid of your $ids variable. No need to use implode with query builders. As for your array_map, I don't understand what you're trying to accomplish with it, so I'll let you update this piece of code to suit your needs.

You can access your parent component instance directly

this.$parent.computedResults

Or save your computedResults in a Vuex state property and get it in the child.

Error 500 is often caused by a code logic error. So don't rule out your code. There must be some kind of pattern your users are following that you don't. Can your users retrace the steps they took to encounter that error ? That would help you out. Also, the error would be more verbose in a local environment. It will tell you what was the stack of operations and what failed.

Try implementing an existance test on your two declared functions

if (!function_exists('randomPostType')) {
    function randomPostType() {

        $post_type = ['forum','video','image','article'];
        $random_key = array_rand($post_type, 1);
        return $post_type[$random_key];
    }
}

if (!function_exists('randomEmbedCode')) {
    function randomEmbedCode() {

        $embed_code = [
            '<iframe class="embedly-embed-1"></iframe>',
            '<iframe class="embedly-embed-2"></iframe>',
            '<iframe class="embedly-embed-3" ></iframe>'
        ];
        $random_key = array_rand($embed_code, 1);
        return $embed_code[$random_key];
    }
}

Try implementing an existance test on your two declared functions

if (!function_exists('randomPostType')) {
    function randomPostType() {

        $post_type = ['forum','video','image','article'];
        $random_key = array_rand($post_type, 1);
        return $post_type[$random_key];
    }
}

if (!function_exists('randomEmbedCode')) {
    function randomEmbedCode() {

        $embed_code = [
            '<iframe class="embedly-embed-1"></iframe>',
            '<iframe class="embedly-embed-2"></iframe>',
            '<iframe class="embedly-embed-3" ></iframe>'
        ];
        $random_key = array_rand($embed_code, 1);
        return $embed_code[$random_key];
    }
}

@bobbybouwmann It's a time saver for sure and is pretty stable if you're not using in dept features. It can be a good choice for customers with limited budgets, but for bigger budget customers with specific needs, I wouldn't recommend it.

While I agree with @bobbybouwmann, I wouldn't use Nova in production. I personally hated the Nova experience because I feel like Nova itself is a MVP. It's extremely rigid, lacks a lot of basic CMS features and still has a lot of bugs. In addition, the two things that irritated me the most was the UX (way too many clicks and doubtful UX decisions in general), as well as the support behind Nova. I've seen multiple highly pertinent requests get shut down in a pretty harsh way with a pathetic reply.

I've not yet used other Laravel CMS options, but I know that some people moved from Nova to October CMS and enjoyed their experience.

I'm betting that you're not using delegated events. So your dynamically added elements do not benefit from the same logic than your content already present on page load. If you're using jQuery, you can solve that easily :

$(document).on('click', '.your-target-class', function () {
    // Your logic
});

The $(document) part above should be something more specific for better performances (ex. : $('.container')), because binding the listener to the document will capture all clicks made on the page.

.your-target-class would be the class that you would want to target (ex. : .category)

I'm betting that you're not using delegated events. So your dynamically added elements do not benefit from the same logic than your content already present on page load. If you're using jQuery, you can solve that easily :

$(document).on('click', '.your-target-class', function () {
    // Your logic
});

The $(document) part above should be something more specific for better performances (ex. : $('.container')), because binding the listener to the document will capture all clicks made on the page.

.your-target-class would be the class that you would want to target (ex. : .category)

Post all your concerned migrations please. So we can get a global idea of what's going on.

Which stylesheets are conflicting exactly ? All of them or specific ones ? What happens and what do you expect ? (Just trying to get as much info as I can)

Also you don't need your unsigned() statements

Then this is part of your issue. A foreign key must reference a primary key.

Do you have a primary key defined in your banks table ? (bigIncrements or some sort of primary key)

The error is pretty explicit. You already have an "employees" table. Delete it from your database by doing a migration rollback if it was issued from a migration. Else, delete it manually and re-run your migration.

Have you imported bootstrap stylesheet(s) first and then your theme's stylesheet(s) ?

We can't help you without some code...

What do you mean by CSS overlap ? Styles overwriting others or container overflow ?

You're missing a capital C in your toUpperCase function :)

You can restart your MySQL server and skip grant tables. That way you can reset your root password.

https://www.a2hosting.com/kb/developer-corner/mysql/reset-mysql-root-password

If you need to use your functions outside your bundled JS, you should assign them to the window.

window.initAutocomplete = function() {
    // ...
}

And to use them, prepend window to your already existent calls

window.initAutocomplete()

Try using DB_PASSWORD with empty quotes.

DB_PASSWORD=""

Else, add a password to your root user. It should solve your issue (already solved mine in the past).

@jlrdw I never used the request helper that way, but I know that you can use it to retrieve a specific subset of keys in your request (like he did).

Looking at the source code, it takes the request collection and only keeps specified keys (preserving the key => value pair).

If his input names are the same as his DB column names, it can work.

You're calling update on a collection instead of a model. You should use first() instead of get() to retrieve a single model instance.

 $offtime = Offtime::where('user_id', $id)->whereYear('year', $year)->first();

You're calling update on a collection instead of a model. You should use first() instead of get() to retrieve a single model instance.

 $offtime = Offtime::where('user_id', $id)->whereYear('year', $year)->first();

Have you tried to put a dd inside your if($this->filled_id == NULL) condition ? As of now, if this condition is hit in your loop somehow, a string is returned and you'd be trying do get the property id of a string (which is not an object), and it will throw the error you're getting.

I don't know what your code base is, but I guess something like that would work (UNTESTED)

// Your final collection
$families = collect();

// The $adults variable here represents your retrieved adults collection
$adults->each(function($adult, $key) use (&$families)) {
    /****** THIS PART COULD BE OPTIMIZED WITH A QUERY BUILDER ******/
    $adults = Adult::where('family_id', $adult->family_id)->get();
    $children = Child::where('family_id', $adult->family_id)->get();
    $family = $adults->merge($children);
    /***************************************************************/

    $families->put($adult->family_id, $family);
});

Are you 100% sure that your console location really is your Laravel project root folder ? Because this error occurs when you're not.

I see. There is a lot of work to do and it's kinda hard to do it blindfolded (without testing). But I'll try and give you a heads up later today (gotta go back to bed if I don't want to fall asleep while working).

Btw, just realized that the following

$brand=brands::where("segment_id",$segment) ->pluck('brands.brand_name,brands.brand_id')->all();

Should be (in correct Laravel standards)

$brands = Brand::where('segment_id', $segment)->select('brand_name', 'brand_id')->get();

Product::where('category', $yourCategory)->sum('price');

Edit : I answered too late, @tisuchi was quicker lol

If you rename your variables/relations correctly like @nakov suggested,

this would show the latest entry (like @goldtaste suggested) :

$ticket->activities->latest()->first();

P.S. The above code is based on the created_at timestamp. If you wish to use another column, you can specify it (here I'm using purchased_at as an example :

$ticket->activities->latest('purchased_at')->first();

We personally use factories when applicable (test counts for example). We tend to avoid automated generation in cases were we need to test interactions with models. That way we can easily see what the original data was and what should be expected.

If you rename your variables/relations correctly like @nakov suggested,

this would show the latest entry (like @goldtaste suggested) :

$ticket->activities->latest()->first();

P.S. The above code is based on the created_at timestamp. If you wish to use another column, you can specify it (here I'm using purchased_at as an example :

$ticket->activities->latest('purchased_at')->first();

Add a slash to the front of your routes URLs. It will most likely solve your issue (because currently your routes don't start from your website root). If it still doesn't work, let us know !

Route::get('/display','[email protected]');

Route::post('/add','[email protected]');

Route::delete('/delete/{Pnumber}','[email protected]');