Looks like that senior used to be a Cobol programmer.

I guess there are no tests written for it either, but if there are, I would ctrl-a delete, and start from scratch.

If not, the I would start by extraction each segment of the if statements to it's own method.

For example

    if ($data['user']['send_email']) {
                $skipResetPassword = array_key_exists('skip_reset_password', $data['user']);
                $withDelay = (array_key_exists('invite_email_with_delay', $data['user']) ? $data['user']['invite_email_with_delay'] : true);
                
                $this->sendInviteEmail($modelResource, $setInviteFlag, $skipResetPassword, $withDelay);
            }

would become something like this

function sendInviteEmailIfNeeded($modelResource, $setInviteFlag, $data)
{
  if (! $data['user']['send_email']) return;

  $skipResetPassword = array_key_exists('skip_reset_password', $data['user']);
  $withDelay = (array_key_exists('invite_email_with_delay', $data['user']) ? $data['user']['invite_email_with_delay'] : true);
  $this->sendInviteEmail($modelResource, $setInviteFlag, $skipResetPassword, $withDelay);
}

I think you should learn how to code, and then use AI as a tool, and not as a developer.

Truncate basically just tell the table that it is empty, doesn't affect the server load at all. It's similar to deleting a file.

I would however suggest that you create a job that removes any log entries older than X days, and then run that every day, then you will not be back in this situation again.

Be aware that you can't just do a DELETE FROM logs WHERE created_at < NOW() - X, that would crash the database. You need to chunk it in iterations of 5-10K records, and I recommend using transactions, because you don't want a commit between each record.

It looks like you are doing a snake sort,

Those are kind of tricky, you need to have another field that decides the order of the ids.

I would suggest using classes, and the cascading effect of CSS.

	.button {
       background-color: grey;
	   color: black;
       font-size: 16px;
       padding: 4px;	
    }

	.button-sm {
		width: 20px;
	}

   .button-md {
		width: 40px;
	}

Yes it is still worth it, and they do have AI dubbed lessons, and Spanish is one of those.

After making the obvious backup, you can try running

php artisan schema:dump

It should create a sql dump of you current schema. Then any changes to the database after that can be done with regular migrations.

https://laravel.com/docs/13.x/migrations#squashing-migrations

You can always give Filament a try, it includes modal support out of the box, you basically just need to remove one line of code to make it a modal.

https://filamentphp.com/

Is this some kind of huge upload of some kind, or is it the processing of something that takes time?

If it is processing and you can't speed it up, you should consider using a background job for it, and release the user request asap, and inform the user when whatever it ism is available.

I agree with @glukinho, you shouldn't mix and match your projects in different branches. Create a repository for each instead.

Sounds to me like you didn't run this properly in the UAT environment.

You didn't specify what the failure was, or any error messages, but it should have failed in dev, and test as well.

What I would do, is either manually roll back the changes made by the first migration, or manually deploy the changes that failed.

You are using a very old method of using layouts, I would suggest using a bit mote modern approach to it, and use blade components, rather than using section and yield.

https://laravel.com/docs/12.x/blade#building-layouts

So I would probably go with this kind of database model.

treasure_hunts

• id
• title

quests

• id
• title

quest_trasure_hunt

• treasure_hunt_id
• quest_id

challanges

• id
• description

challange_quest

• challange_id
• quest_id

riddles

• id
• question
• correct_answer_id

answers

• id
• answer
• riddle_id

riddle_user

• riddle_id
• user_id
• answer_id

quest_user

• quest_id
• user_is

Then progress is tracked through the riddle_user table.

In the beginning there is a notice about upload being reserved. Odd that they haven't fixed the example.

Apparently it is a reserved word in livewire,

In Livewire 3, naming a method upload in your component is a "gotcha" that causes issues because "upload" is a reserved word used internally by Livewire for handling file uploads. Laravel Livewire Laravel Livewire Using upload as a method name conflicts with Livewire's JavaScript-to-server communication, preventing your component from properly storing files or receiving them as null. The Core Issue Reserved Method/Property: You cannot use upload as a method or property name in your Livewire component class. Why it fails: When a file is selected, Livewire's JS makes a request to a temporary "signed" URL. If you have a method named upload, it clashes with this process. Common Error: The wire:submit or wire:click does not trigger the method, or the file input behaves unexpectedly. Laracasts Laracasts +4 How to Fix It Rename your upload() method to something else, such as save(), submit(), or store().

Apparently it is a reserved word in livewire,

In Livewire 3, naming a method upload in your component is a "gotcha" that causes issues because "upload" is a reserved word used internally by Livewire for handling file uploads. Laravel Livewire Laravel Livewire Using upload as a method name conflicts with Livewire's JavaScript-to-server communication, preventing your component from properly storing files or receiving them as null. The Core Issue Reserved Method/Property: You cannot use upload as a method or property name in your Livewire component class. Why it fails: When a file is selected, Livewire's JS makes a request to a temporary "signed" URL. If you have a method named upload, it clashes with this process. Common Error: The wire:submit or wire:click does not trigger the method, or the file input behaves unexpectedly. Laracasts Laracasts +4 How to Fix It Rename your upload() method to something else, such as save(), submit(), or store().

I would suggest reading the upgrade guide, it will likely have that issue covered.

Without more code it's hard to say, but there was a change made between version 2 and 3, regarding how you set the model, in version 2 you could do the whole form, but in version 3 you need to set the model on each input.

If you are using HTTPS (as you should) the traffic is already encrypted.

I would probably take this a step further, and bring it down to a single query. Since this is some kind of index page, and those are more or less read only, I would create a view in the database, and use that to fetch the orders and the related tables.

Excuse my old school way of writing JOINS in SQL. This is just an example not an exact rendition of the table and fields used in the video

CREATE VIEW order_index_views AS
SELECT o.id, o.placed_at, oi.product_id, p.name, u.name, u.email
FROM orders o,
            order_items oi,
            products p,
			users u
WHERE o.id = oi.order_id
AND oi.product_id = p.id
AND o.user_id = u.id;

Then I would create a Model for the view called OrderIndexView

And in the controller do

$orderItems = OrderIndexView::orderBy('placed_at')->paginate(50);

This approach will give me a single query, and it will prevent the loading of fields you don't use, and that solves the N+1 and saves memory.

The only issue with this approach, is that you can't really use the nice syntax of the Schema Builder, you need to use a DB:statement to create and drop the view.

If you want more information about how to create and use views in your database, you can check this post out.

https://tray2.se/posts/use-a-view-instead-of-a-complex-eloquent-query-in-your-laravel-application

I would start by making sure that the JS and CSS is in the /public/assets directory, because they likely aren't.

You need to run npm run build and make sure you deploy those files.

@terdoo-mzer Simple, anything between the {} is treated like a wildcard.

That means the /ideas/{idea} catches /ideas/create, so it tries to look from a idea with the id of create.

Check out the following posts, they will give you some ideas.

https://tray2.se/posts/database-design

https://tray2.se/posts/database-design-part-2

https://tray2.se/posts/properly-formed-foreign-keys-are-your-best-friends

https://tray2.se/posts/use-a-view-instead-of-a-complex-eloquent-query-in-your-laravel-application

https://tray2.se/posts/using-table-triggers-to-log-changes-in-your-database-tables

Check out the following posts, they will give you some ideas.

https://tray2.se/posts/database-design

https://tray2.se/posts/database-design-part-2

https://tray2.se/posts/properly-formed-foreign-keys-are-your-best-friends

https://tray2.se/posts/use-a-view-instead-of-a-complex-eloquent-query-in-your-laravel-application

https://tray2.se/posts/using-table-triggers-to-log-changes-in-your-database-tables

Just think on this.

A user is a user, don't overthink, or over engineer.

Use a single login page, and handle it with roles/types of users.

This is what I do.

1. Write code to a make a feature work.
2. Refactor/ clean up the code of said feature.
3. Start with the next feature and repeat.

If you push on and finish the product, it is likely that you never clean up the code.

So I'd say C. clean up some code, write a feature, clean up some more code until you are done. Make small improvements of the code in iterations, don't try to clean it up all at once, it will likely be overwhelming.

Yes, it will likely slow down the import.

You should only have as many indexes as you need, and as few as you can get away with.

Quote from Aaron Francis.

Think of an index as a alphabetically sorted box of cards, and the box is then divided into section A - Z. So every time you need to insert something into the index, you need to first find the section, and then the exact place for it within the section. Now imagine doing that 28 times for each card.

If you are then using MySQL or MariaDB then each time you insert something and the index is refreshed, the table is locked, so you can't insert into it until all indexes are up to date. This will be fairly fast per index, but 28 is a lot, and the indexes will likely cause deadlocks between each other.

Indexes should basically only be used on column that you use in WHERE, ORDER BY, and foreign keys.

Sound like a strange thing to do to me, unless they are dev only routes, and if so they shouldn't be pushed to prod at all.

Why would you want to differentiate between local and prod when coming to routes?

However, I would probably put that kind of check in the controller, that way I don't need to pollute the routes file with logic.

So I would probably go with this kind of database model.

treasure_hunts

• id
• title

quests

• id
• title

quest_trasure_hunt

• treasure_hunt_id
• quest_id

challanges

• id
• description

challange_quest

• challange_id
• quest_id

riddles

• id
• question
• correct_answer_id

answers

• id
• answer
• riddle_id

riddle_user

• riddle_id
• user_id
• answer_id

quest_user

• quest_id
• user_is

Then progress is tracked through the riddle_user table.

@JakovljevicFilip You are correct, they are both viable options. I however, am more in the camp of letting the database handle any kind of filtering, sorting, counting, and such, much rather than letting php handle that.

In this case I would have created a table that contain the statuses, and with a simple join select the count of each instance, that way I don't need to use any map to get what I need.

Use a multi select dropdown for the roles, or use a checkbox group. They both give you an array of roles.

Do you have more than one id for the same invoice?

I would suggest doing ->toSql() on the query and then run explain on it.

It fails because of this line $user = $users->find(1);

When you refresh the database, you don't reset the internal sequence of the id. That means that the first time you run it, it creates id 1, and 2, the next time it creates id 3 and 4, and so on.

Truncating the table resets the internal sequence, thus giving you id 1 and 2 every time you run the test.

So changing the line to

$user = $user->first();

Or to

$user = $user->find($users[0]->id);

Should solve your issue.

One important thing when creating routes like that, is the order.

Route::get('/ideas/create', [IdeaController::class, 'index']);

Must be defined before

Route::get('/ideas/{idea}', [IdeaController::class, 'show']);

Or you will scratch your head as to why you get a 404 when trying to navigate to the create Idea route.

They are basically the same thing, but two different ways to learn.

As a STA try downloading the lesson and run it offline.

If you are referring to the Laravel From Scratch 2026 and 30 Days To Learn Laravel, well they are basically the same thing, it doesn't really matter that much which one you choose. I would go with the From Scratch one.

I would suggest reading the docs

https://cloud.laravel.com/docs/network#x-robots-tag

I would suggest using a better tool than phpmyadmin.

If you are using MySQL/MariaDB you don't need to add it manually like that, it's added automatically.

I just created this migration.

 public function up(): void
    {
        Schema::create('books', function (Blueprint $table) {
            $table->id();
            $table->foreignId('user_id')->constrained()->onDelete('cascade');
            $table->timestamps();
        });
    }

And when I run show index from books

I get the following

  {
    "Table": "books",
    "Non_unique": 0,
    "Key_name": "PRIMARY",
    "Seq_in_index": 1,
    "Column_name": "id",
    "Collation": "A",
    "Cardinality": 0,
    "Sub_part": null,
    "Packed": null,
    "Null": "",
    "Index_type": "BTREE",
    "Comment": "",
    "Index_comment": "",
    "Visible": "YES",
    "Expression": null
  }

  {
    "Table": "books",
    "Non_unique": 1,
    "Key_name": "books_user_id_foreign",
    "Seq_in_index": 1,
    "Column_name": "user_id",
    "Collation": "A",
    "Cardinality": 0,
    "Sub_part": null,
    "Packed": null,
    "Null": "",
    "Index_type": "BTREE",
    "Comment": "",
    "Index_comment": "",
    "Visible": "YES",
    "Expression": null
  }

If I add the index name like you did

 public function up(): void
    {
        Schema::create('books', function (Blueprint $table) {
            $table->id();
            $table->foreignId('user_id')->constrained(indexName: 'FK_BOOK_USER')->onDelete('cascade');
            $table->timestamps();
        });
    }

Then I get

  {
    "Table": "books",
    "Non_unique": 1,
    "Key_name": "FK_BOOK_USER",
    "Seq_in_index": 1,
    "Column_name": "user_id",
    "Collation": "A",
    "Cardinality": 0,
    "Sub_part": null,
    "Packed": null,
    "Null": "",
    "Index_type": "BTREE",
    "Comment": "",
    "Index_comment": "",
    "Visible": "YES",
    "Expression": null
  }

not really, you only have to define it once.

<nav>
	<a href="#" >Link 1</a>
	<a href="#" >Link 2</a>
</nav>

<script>
	let navs = document.querySelectorAll('nav a');

    navs.forEach((nav) => {
		nav.addEventListener('click', (event) => {
		    event.target.parentNode.classList.add('hidden');
	});
   });
</script>

just add hidden to the sidebars classList.

I would start by running composer update, since that will most likely handle the issue.

If it doesn't check the GitHub page for the project, and see if they implemented a fix for it.

I would start by running composer update, since that will most likely handle the issue.

If it doesn't check the GitHub page for the project, and see if they implemented a fix for it.

I would suggest trying them both, and make a decision from that.

Like Lary states, PHPStorm has Laravel Idea which is awesome.

The Official Laravel VS Code plugin might work with Cursor, but that is not as good as Larvel Idea.

Since the code you have shown only passes those to the view, then it makes sense to use a view composer. If you just to use them for some logic in other methods in the controller, then I would set them in a constructor method.

class PagamController extends Controller
{
	protected int $minYear;
	protected int $maxYear;

    public function __construct()
    {
        $this->minYear = Pagam::whereNotNull('etoscreated')->min("etoscreated");
		$this->maxYear = Pagam::whereNotNull('etoscreated')->max("etoscreated");
    }

You can use a view composer to share that information

https://laravel.com/docs/12.x/views#view-composers

I would also suggest that you code in English, you will get a lot of help from the framework.

I would start looking at your database queries