I would like to know if your system suits my use case.

**A medium sized screen printing and embroidery company wants to:

• I want to digitize our workflow (paper work and job flow)
• Move most of our work order processes to digital (order communication, statuses, checking in items / stock, art proofing, calendar, notes, etc)
• Have a customer portal so they can check the status of their orders, approve production and communicate through the app/site. (Not looking for any payments or transactions yet)
• Internal calendar for overall work load in the shop, automations and color coding. Possibly automated job timing.**

1. Would it need lot of customization?

2. What was in your mind when you were developing this system?

Describe the bug Hi I am interested in your project, but when I tried to start it, I encountered several fatal error bound with composer autoload. I noticed there are some case typo in the code, PHP is case-insensitive but composer is not. So, I did understand if you designed your software in the way to bypass this limitation(I have no experience on this way) or it is a real issue.

Anyway make case sensitive code also in PHP could be a good practice.

Anymore, often you use workflow but sometimes you refer to Workflow, so maybe it should be used only one style for the whole project.

In particular I would to show you two errors:

• In /dashboard: Get Error Class 'App\Models\workflow\Orders' not found
• In /users: Get InvalidArgumentException View [Users] not found.

So I would like to know what is your idea about this.

To Reproduce In container based on php:7.4-fpm

Steps to reproduce the behavior:

1. composer i
2. php artisan serve --host=127.0.0.1 --port=8000
3. Perform login or navigate to /dashboard

Additional context You can find some of this kind of code in:

• app/Http/Controllers/HomeController.php line 7 substituting workflow with Workflow error on dashboard disappears
• app/Models/User.php line 16
• routes/web.php in several endpoints you refer to App\Http\Controllers\workflow instead of App\Http\Controllers\Workflow

Is your feature request related to a problem? Please describe.

When I was developing some seeders for the database I noticed that it seems there is not a real convention in table columns names: Some name in English, some in French, some uppercase, some snake_case.

I think this standardization in future can improve the maintainability of the code.

Additional for example, for a not french person it is really difficult to deal with French names.

Describe the solution you'd like

Laravel for its tables (like users) use the snake_case in English, maybe it may be used for all tables.

This is only a proposal

Thank for your great work, several of this issues are now solved, there is another issues yet, that I think is correlated to this one.

In some pages I encounter this fatal error

InvalidArgumentException
Unable to locate a class or view for component [infocalloutComponent]. 

For example I find this error in the kanban page /production/kanban

I not able to understand if it is always correlated to missmatch case. It looks that the code is right. This is the first project in Laravel I ever study, sorry :(

Originally posted by @RobertoBochet in https://github.com/billyboy35/WebErpMesv2/issues/7#issuecomment-1017570464

Describe the bug I tried to run the project on local without using docker , so i found out some errors , when i used laragon latest version or even php 7.4 Class App\Models\Companies\CompaniesAddresses located in D:/laragon/www/WebErpMesv2/app\Models\Companies\companiesAddresses.php does not comply with psr-4 autoloading standard. Skipping. Class App\Models\Companies\CompaniesContacts located in D:/laragon/www/WebErpMesv2/app\Models\Companies\companiesContacts.php does not comply with psr-4 autoloading standard. Skipping.

Describe the bug the modal of modification of the technical division is not displayed

To Reproduce Steps to reproduce the behavior:

1. Go to quote page and create new one
2. Go to quote line tab and add one line
3. display BOM detail
4. add teck cut 5 try to diplay modal for update

Expected behavior

Start modal : <div class="modal fade" id="#TechnicalCutUpdateModal41" tabindex="-1" role="dialog" aria-labelledby="TechnicalCutModalTitle" aria-hidden="true">

Call modal <div class="btn-group btn-group-sm">   <a href="#" data-toggle="modal" data-target="#TechnicalCutUpdateModal41" class="btn btn-info"><i class="fa fa-lg fa-fw fa-edit"></i></a>   </div> Additional context Same for product page, but all working for BOM modal update

Describe the bug This page return 419 error http://demo.wem-project.org/companies http://demo.wem-project.org/purchases/request http://demo.wem-project.org/quotes/504 (new quote)

** log ** [2022-06-08 09:01:49] production.ERROR: SQLSTATE[HY093]: Invalid parameter number (SQL: select * from companies order by id limit 5) {"userId":947,"exception":"[object] (Illuminate\Database\QueryException(code: HY093): SQLSTATE[HY093]: Invalid parameter number (SQL: select * from companies order by id limit 5) at /homepages/10/d912969182/htdocs/demo/vendor/laravel/framework/src/Illuminate/Database/Connection.php:712) [stacktrace]

[previous exception] [object] (ErrorException(code: 0): Attempt to read property "id" on null at /homepages/10/d912969182/htdocs/demo/app/Http/Livewire/PurchasesRequest.php:122) [stacktrace]

[2022-06-08 11:09:52] production.ERROR: Class "App\ServiceS\QuoteCalculator" not found {"userId":947,"exception":"[object] (Error(code: 0): Class "App\ServiceS\QuoteCalculator" not found at /homepages/10/d912969182/htdocs/demo/app/Http/Controllers/Workflow/QuotesController.php:62) [stacktrace]

Screenshots

Describe the bug ErrorException Trying to access array offset on value of type null (View: C:\laragon\www\WebErpMesv2\resources\views\print\print-sales.blade.php) http://127.0.0.1:8000/print/invoice/1

To Reproduce Steps to reproduce the behavior:

1. Go to invoince section
2. clik on print button 3 See error

Screenshots

Additional context

Describe the bug if we add new order line, without kanban board statu in companie setting, we can't seed statu_id for create new task

@include('include.Main-procces', ['route' => route('task.store', ['id' => $OrderLine->orders_id]),'id_page' => $OrderLine->orders_id, 'id_type' => 'order_lines_id', 'id_line' => $OrderLine->id, 'status_id'=>$status_id['id'] ,'task' => $OrderLine->Task])

'status_id'=>$status_id['id'] is empty

define on Orderline.php

$this->status_id = Status::select('id')->orderBy('order')->first();

Describe the bug Warning in docker terminal

Class Database\Factories\companiesAddressesFactory located in www/WebErpMesv2/database/factories\companiesAdressesFactory.php does not comply with psr-4 autoloading standard. Skipping. Class App\Http\Controllers\StatusController located in www/WebErpMesv2/app\Http\Controllers\Planning\StatusController.php does not comply with psr-4 autoloading standard. Skipping. Class App\Http\Controllers\workflow\DeliverysController located in www/WebErpMesv2/app\Http\Controllers\Workflow\DeliverysController.php does not comply with psr-4 autoloading standard. Skipping. Class App\Http\Controllers\workflow\OrderLinesController located in www/WebErpMesv2/app\Http\Controllers\Workflow\OrderLinesController.php does not comply with psr-4 autoloading standard. Skipping. Class App\Http\Controllers\workflow\OrdersController located in www/WebErpMesv2/app\Http\Controllers\Workflow\OrdersController.php does not comply with psr-4 autoloading standard. Skipping. Class App\Http\Requests\workflow\StoreOrderRequest located in www/WebErpMesv2/app\Http\Requests\Workflow\StoreOrderRequest.php does not comply with psr-4 autoloading standard. Skipping. Class App\Http\Requests\workflow\UpdateOrderRequest located in www/WebErpMesv2/app\Http\Requests\Workflow\UpdateOrderRequest.php does not comply with psr-4 autoloading standard. Skipping. Class App\Services\OrderCalculator located in www/WebErpMesv2/app\Services\InvoiceCalculator.php does not comply with psr-4 autoloading standard. Skipping.

Describe the bug Since the composer version 2.0 the property name in composer.json should be lowercase

This error prevents to run composer i with composer version greater than 2.0

status

• New
• assigned
• In progress
• Converted
• Lost

Infos company

• Company
• Website

Infos contact

• Phone number
• E-mail
• Last name
• First name
• Function

Infos Address

• Address
• Postal code
• Town
• Region
• Country

setup -Rejected calls

• Refusal of emails

Comment

Have a salary contract management (informative without generating them)

must contain the following aspects

• Status:

On trial Asset Closed

• Employee choice

Service - list of choices coming from the method? Signature Date Type of Contract Use

-Organization

Start date Duration trial period End date Weekly Duration

• Position / Salary

Position Coefficient Hourly gross salary Minimum monthly salary Annual gross salary

• End of the contract

End of contract reason Coment