DaybydayCRM an open-source CRM, to help you keep track of your daily workflow.

Overview

======================

GitHub Workflow Status GitHub tag (latest by date) PRs Welcome Twitter URL

DaybydayCRM is an everyday customer relationship management system (CRM) to help you keep track of your customers, tasks, appointments, etc. The CRM is offered as an open-source, self-hosted platform and as a hosted CRM system on daybydaycrm.com.

Demo

Try a demo version of DaybydayCRM at:

demo.daybydaycrm.com

Support the project

If you benefit from and/or like using DaybydayCRM, please consider help drive the future development of the project by:

And i will keep creating new features, releases, keep support running, and fix issues.

Features

  • Tasks & leads management
  • Invoice management
  • Time registration
  • Register user absence and vacation
  • Client & users appointments
  • Role -> permissions management
  • Global search
  • Client overview
  • Upload documents, and keep track of client documents
  • And many more, for more detailed features overview go to daybydaycrm.com/pricing

Get started

For help on getting started, take a look at the wiki.

Feedback

Feel free to send us feedback on Twitter or file an issue. Feature requests are always welcome. If you wish to contribute, please take a quick look at the guidelines!

Contribution Guide

DaybydayCRM follows PSR-2 coding standard.

All tests should pass on Github actions, or the failed test should be rewritten to fit new changes.

Localization

You can help to translate DaybydayCRM into other languages by copying the resources/lang/en folder into, for example, resources/lang/de and translate the file found inside the folder.

Licenses

DaybydayCRM from version 2.0.0 and up is open-sourced software licensed under the GNU GPLv3... FAQ GPL

DaybydayCRM under and not included version 2.0.0 is open-sourced software licensed under the MIT license

Comments
  • Class 'App\Department' not found on install

    Class 'App\Department' not found on install

    Went through installation procedures and had some errors as shown below. At the very end I posted my error log as well when attempting to access the CRM.

    When running this during setup:

     php artisan migrate --seed
    

    I received the following issues:

    Seeded: IndustriesTableSeeder PHP Fatal error: Class 'App\Department' not found in /Applications/MAMP/htdocs/git/laravel/flarepoint/database/seeds/DepartmentsTableSeeder.php on line 16 PHP Stack trace: PHP 1. {main}() /Applications/MAMP/htdocs/git/laravel/flarepoint/artisan:0 PHP 2. Illuminate\Foundation\Console\Kernel->handle() /Applications/MAMP/htdocs/git/laravel/flarepoint/artisan:36 PHP 3. Symfony\Component\Console\Application->run() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:122 PHP 4. Symfony\Component\Console\Application->doRun() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/symfony/console/Application.php:117 PHP 5. Symfony\Component\Console\Application->doRunCommand() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/symfony/console/Application.php:186 PHP 6. Illuminate\Console\Command->run() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/symfony/console/Application.php:818 PHP 7. Symfony\Component\Console\Command\Command->run() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Console/Command.php:155 PHP 8. Illuminate\Console\Command->execute() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/symfony/console/Command/Command.php:256 PHP 9. Illuminate\Container\Container->call() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Console/Command.php:169 PHP 10. call_user_func_array:{/Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Container/Container.php:507}() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Container/Container.php:507 PHP 11. Illuminate\Database\Console\Migrations\MigrateCommand->fire() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Container/Container.php:507 PHP 12. Illuminate\Console\Command->call() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php:79 PHP 13. Illuminate\Console\Command->run() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Console/Command.php:185 PHP 14. Symfony\Component\Console\Command\Command->run() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Console/Command.php:155 PHP 15. Illuminate\Console\Command->execute() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/symfony/console/Command/Command.php:256 PHP 16. Illuminate\Container\Container->call() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Console/Command.php:169 PHP 17. call_user_func_array:{/Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Container/Container.php:507}() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Container/Container.php:507 PHP 18. Illuminate\Database\Console\Seeds\SeedCommand->fire() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Container/Container.php:507 PHP 19. Illuminate\Database\Eloquent\Model::unguarded() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Database/Console/Seeds/SeedCommand.php:64 PHP 20. Illuminate\Database\Console\Seeds\SeedCommand->Illuminate\Database\Console\Seeds\{closure}() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php:2279 PHP 21. DatabaseSeeder->run() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Database/Console/Seeds/SeedCommand.php:63 PHP 22. Illuminate\Database\Seeder->call() /Applications/MAMP/htdocs/git/laravel/flarepoint/database/seeds/DatabaseSeeder.php:16 PHP 23. DepartmentsTableSeeder->run() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Database/Seeder.php:39

     [Symfony\Component\Debug\Exception\FatalErrorException]  Class 'App\Department' not found      
    

    When attempting to dummy data commands, also received an error for:

     php artisan db:seed --class=UsersDummyTableSeeder 
    

    [Illuminate\Database\QueryException] SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (flarepoint_crm.role_user, C ONSTRAINTrole_user_role_id_foreignFOREIGN KEY (role_id) REFERENCESroles(id) ON DELETE CASCADE ON UPDATE CASCADE) (SQL: insert intorole_us
    er(role_id,user_id`) values (1, 2))

    [PDOException]
    SQLSTATE[23000]: Integrity constraint violation: 1452 Cannot add or update a child row: a foreign key constraint fails (flarepoint_crm.role_user, C
    ONSTRAINT role_user_role_id_foreign FOREIGN KEY (role_id) REFERENCES roles (id) ON DELETE CASCADE ON UPDATE CASCADE)`

    Error Log

    [31-Aug-2016 21:51:11 America/Los_Angeles] PHP Parse error: syntax error, unexpected '.', expecting '&' or variable (T_VARIABLE) in /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/laravel/framework/src/Illuminate/Foundation/helpers.php on line 475 [31-Aug-2016 21:51:11 America/Los_Angeles] PHP Stack trace: [31-Aug-2016 21:51:11 America/Los_Angeles] PHP 1. {main}() /Applications/MAMP/htdocs/git/laravel/flarepoint/public/index.php:0 [31-Aug-2016 21:51:11 America/Los_Angeles] PHP 2. require() /Applications/MAMP/htdocs/git/laravel/flarepoint/public/index.php:21 [31-Aug-2016 21:51:11 America/Los_Angeles] PHP 3. require() /Applications/MAMP/htdocs/git/laravel/flarepoint/bootstrap/autoload.php:17 [31-Aug-2016 21:51:11 America/Los_Angeles] PHP 4. ComposerAutoloaderInite09a2c4a68b74041a4ebca4fce5bff8c::getLoader() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/autoload.php:7 [31-Aug-2016 21:51:11 America/Los_Angeles] PHP 5. composerRequiree09a2c4a68b74041a4ebca4fce5bff8c() /Applications/MAMP/htdocs/git/laravel/flarepoint/vendor/composer/autoload_real.php:56

    bug 
    opened by mklahorst 13
  • delete user - method not allowed

    delete user - method not allowed

    I've spent much time to find a solution to remove the user. No good results :(

    The form asks the admin, what needs to be done with the existing clients/tasks/leads and who to assign: handlde deletion

    The issue is in this file: resources/views/users/index.blade.php

    I've noticed, that the problem stays in the ajax. The foreach loop does not work here. When I try to fill the select options with Ajax - i receive this error:

    DataTables warning: Non-table node initialisation (SELECT). For more information about this error, please see http://datatables.net/tn/2

    Does anyone have an idea, how to assign other users to the tasks of the removed user? Please please help!

    Zrzut ekranu 2019-07-3 o 23 34 53

    bug 
    opened by SkowronekArt 12
  • Added Extended JSON languages

    Added Extended JSON languages

    Extended the JSON english and spanish languages (The original translations where from @jvas28 credit to him for starting with this).

    General Some strings are still missing like "HR" or "Hi" (Haven't added any new). Ordered all string alphabetically.

    Spanish Have corrected some misspelled word from the @jvas28 PR also (Some may be still broken). Added a insane amount of translated strings

    opened by Edgarborras94 10
  • Contacts

    Contacts

    OK, so I'm not 100% satisfied with this but felt like it was time to ship it. Release early, release often.

    Anyway, I deviated from the way Flarepoint was doing things in a few ways:

    First, my changes avoid the use of the Repository pattern where possible. Unless someone sees a compelling reason to stick with repos, I feel like they just add an extra layer of abstraction that doubles work. Personally, I didn't consider the ability to change database backends as a strong enough reason to keep using repos. The unfortunate effect of this is that we now have a mix of repos and direct Eloquent implementation. My intention at some point in the future is to rewrite all the repo code to be plain old Eloquent. In the meantime, it'll be a little messy.

    Second, contact-related pages are laid out with responsive design in mind, although that's not fully implemented. I'll work more on that soon.

    Third, three new contact permissions were created: contact-create, contact-update and contact-delete. It occurs to me that I may not have implemented these new permissions in the best way (I just added them to PermissionsTableSeeder), since they won't be created if you're upgrading. So I'll have to commit an update to this pull request later to fix that.

    Lastly, I setup a four-level hierarchy for user roles: Administrator, Manager, Sales Representative and Employee. The idea is that Managers can modify all client data, but can't create users. Sales Reps create and edit, but can't delete. And Employees are read-only. These roles are only created for a new install at the moment. No effort was made to migrate your existing roles. I probably should have made this change in another branch, but it's too late now. 😁

    I would recommend against trying to upgrade an existing Flarepoint install at the moment. Especially if you have data you care about.

    opened by jhuebel 10
  • Separate Contacts from Clients

    Separate Contacts from Clients

    Separate the individual contact information from the company information. At the medium and large business scales, there are often multiple contacts involved. The ability to document all those contacts would be ideal.

    Feature 
    opened by jhuebel 10
  • Sidebar menu links

    Sidebar menu links "Projects" "Tasks" etc - don't work: throw browser console error

    Whenever I want to go from Dashboard to any menu item on the left (it seems), I see console error:

    vendor.js:732 Uncaught TypeError: Cannot convert object to primitive value
        at RegExp.test (<anonymous>)
        at HTMLDivElement.<anonymous> (vendor.js:732)
        at Function.each (app.js:65534)
        at jQuery.fn.init.each (app.js:65356)
        at jQuery.fn.init.Plugin [as collapse] (vendor.js:727)
        at HTMLAnchorElement.<anonymous> (vendor.js:765)
        at HTMLDocument.dispatch (app.js:70582)
        at HTMLDocument.elemData.handle (app.js:70386)
    

    See video: https://www.loom.com/share/5946accd32b043a5b0163f4280f54341

    bug 
    opened by PovilasKorop 9
  • APP_URL being ignored causing Mixed Content errors

    APP_URL being ignored causing Mixed Content errors

    I'm running 2.2.1 in a Docker Container with Nginx proxy, and another Nginx proxy on the host, and I have APP_URL set to my public https://crm.example.org URL, but I'm still getting "Mixed content" errors when loading the page:

    image

    But as far as I can tell the APP_URL is the correct setting: https://github.com/Bottelet/DaybydayCRM/blob/3c5ed12e217140859ff980161a742f8f58368151/config/app.php#L36-L42

    According to Laravel docs for URL::asset() function the correct setting is ASSET_URL: https://laravel.com/docs/7.x/helpers#method-asset

    But I tried that as well, and also APP_URI, but none of them work either. And I also have X-Forwarded-Proto and X-Forwarded-Host headers set on the proxy.

    What's up with that?

    opened by jakubgs 7
  • Laravel 5.3 Package Shift

    Laravel 5.3 Package Shift

    This pull request includes the changes for upgrading your Laravel Package to Laravel 5.3. Feel free to commit any additional changes to the laravel-package-5.3-shift branch.

    Before merging, you should:

    • Checkout the laravel-package-5.3-shift branch
    • Review all pull request comments for additional changes
    • Run composer update (if the pre-commands fail, add --no-scripts)
    • Thoroughly test your code

    This Shift is still in beta. If there were changes you feel could have been automated, please leave a comment on this pull request to help improve Laravel Shift.

    opened by laravel-shift 7
  • Error running migration for payments table

    Error running migration for payments table

    i got this error when running the migration:

    SQLSTATE[23000]: Integrity constraint violation: 19 NOT NULL constraint failed: permissions.external_id (SQL: insert into "permissions" ("display_name", "name", "description", "grouping", "updated_at", "created_at") values (Add payment, payment-create, Be able to add a new payment on a invoice, payment, 2020-08-26 12:03:44, 2020-08-26 12:03:44))

    image

    its because on 2020_01_06_203615_create_payments_table.php migration file, the external_id is not set, and the external_id is not nullable on permissions table.

    opened by lakuapik 6
  • can't get the 5.8 branch to work?

    can't get the 5.8 branch to work?

    I just checked out the laravel-5.8 branch, followed the installation instructions and it all went smoothly. I can access the CRM and log in, but then once I'm in the gui seems to not be working. For example when clicking on most of the menu items such as Clients, Tasks, Leads, the sub-menu does not expand and I see this error in my console:

    Uncaught TypeError: Cannot read property 'querySelectorAll' of null
        at e.n._getParent (app.js:1)
        at new e (app.js:1)
        at HTMLDivElement.<anonymous> (app.js:1)
        at Function.each (app.js:1)
        at M.fn.init.each (app.js:1)
        at M.fn.init.e._jQueryInterface [as collapse] (app.js:1)
        at HTMLDivElement.<anonymous> (app.js:1)
        at Function.each (app.js:1)
        at M.fn.init.each (app.js:1)
        at HTMLAnchorElement.<anonymous> (app.js:1)
    

    On top of following the installation instructions, I also ran yarn and yarn prod thinking that this was needed, but this didn't make this problem go away

    Any idea @jhuebel ?

    opened by vesper8 6
  • 🚨 Potential Security Vulnerability - huntr.dev

    🚨 Potential Security Vulnerability - huntr.dev

    ⚠️ Potential Vulnerability in DaybydayCRM

    👋 Hello, @Bottelet - @ranjit-git has disclosed a potential vulnerability in your repository. To validate or invalidate this potential vulnerability, please visit https://huntr.dev/bounties/4-other-DaybydayCRM and join our community in helping secure open-source code.


    ☎️ Need further support?

    Come and join us on our Discord and a member of our team will be happy to help! 🤗

    cc - @JamieSlome

    opened by huntr-helper 5
  • Bump express from 4.17.1 to 4.18.2

    Bump express from 4.17.1 to 4.18.2

    Bumps express from 4.17.1 to 4.18.2.

    Release notes

    Sourced from express's releases.

    4.18.2

    4.18.1

    • Fix hanging on large stack of sync routes

    4.18.0

    ... (truncated)

    Changelog

    Sourced from express's changelog.

    4.18.2 / 2022-10-08

    4.18.1 / 2022-04-29

    • Fix hanging on large stack of sync routes

    4.18.0 / 2022-04-25

    ... (truncated)

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies javascript 
    opened by dependabot[bot] 0
  • Bump qs and express

    Bump qs and express

    Bumps qs and express. These dependencies needed to be updated together. Updates qs from 6.7.0 to 6.11.0

    Changelog

    Sourced from qs's changelog.

    6.11.0

    • [New] [Fix] stringify: revert 0e903c0; add commaRoundTrip option (#442)
    • [readme] fix version badge

    6.10.5

    • [Fix] stringify: with arrayFormat: comma, properly include an explicit [] on a single-item array (#434)

    6.10.4

    • [Fix] stringify: with arrayFormat: comma, include an explicit [] on a single-item array (#441)
    • [meta] use npmignore to autogenerate an npmignore file
    • [Dev Deps] update eslint, @ljharb/eslint-config, aud, has-symbol, object-inspect, tape

    6.10.3

    • [Fix] parse: ignore __proto__ keys (#428)
    • [Robustness] stringify: avoid relying on a global undefined (#427)
    • [actions] reuse common workflows
    • [Dev Deps] update eslint, @ljharb/eslint-config, object-inspect, tape

    6.10.2

    • [Fix] stringify: actually fix cyclic references (#426)
    • [Fix] stringify: avoid encoding arrayformat comma when encodeValuesOnly = true (#424)
    • [readme] remove travis badge; add github actions/codecov badges; update URLs
    • [Docs] add note and links for coercing primitive values (#408)
    • [actions] update codecov uploader
    • [actions] update workflows
    • [Tests] clean up stringify tests slightly
    • [Dev Deps] update eslint, @ljharb/eslint-config, aud, object-inspect, safe-publish-latest, tape

    6.10.1

    • [Fix] stringify: avoid exception on repeated object values (#402)

    6.10.0

    • [New] stringify: throw on cycles, instead of an infinite loop (#395, #394, #393)
    • [New] parse: add allowSparse option for collapsing arrays with missing indices (#312)
    • [meta] fix README.md (#399)
    • [meta] only run npm run dist in publish, not install
    • [Dev Deps] update eslint, @ljharb/eslint-config, aud, has-symbols, tape
    • [Tests] fix tests on node v0.6
    • [Tests] use ljharb/actions/node/install instead of ljharb/actions/node/run
    • [Tests] Revert "[meta] ignore eclint transitive audit warning"

    6.9.7

    • [Fix] parse: ignore __proto__ keys (#428)
    • [Fix] stringify: avoid encoding arrayformat comma when encodeValuesOnly = true (#424)
    • [Robustness] stringify: avoid relying on a global undefined (#427)
    • [readme] remove travis badge; add github actions/codecov badges; update URLs
    • [Docs] add note and links for coercing primitive values (#408)
    • [Tests] clean up stringify tests slightly
    • [meta] fix README.md (#399)
    • Revert "[meta] ignore eclint transitive audit warning"

    ... (truncated)

    Commits
    • 56763c1 v6.11.0
    • ddd3e29 [readme] fix version badge
    • c313472 [New] [Fix] stringify: revert 0e903c0; add commaRoundTrip option
    • 95bc018 v6.10.5
    • 0e903c0 [Fix] stringify: with arrayFormat: comma, properly include an explicit `[...
    • ba9703c v6.10.4
    • 4e44019 [Fix] stringify: with arrayFormat: comma, include an explicit [] on a s...
    • 113b990 [Dev Deps] update object-inspect
    • c77f38f [Dev Deps] update eslint, @ljharb/eslint-config, aud, has-symbol, tape
    • 2cf45b2 [meta] use npmignore to autogenerate an npmignore file
    • Additional commits viewable in compare view

    Updates express from 4.17.1 to 4.18.2

    Release notes

    Sourced from express's releases.

    4.18.2

    4.18.1

    • Fix hanging on large stack of sync routes

    4.18.0

    ... (truncated)

    Changelog

    Sourced from express's changelog.

    4.18.2 / 2022-10-08

    4.18.1 / 2022-04-29

    • Fix hanging on large stack of sync routes

    4.18.0 / 2022-04-25

    ... (truncated)

    Commits

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies javascript 
    opened by dependabot[bot] 0
  • Bump decode-uri-component from 0.2.0 to 0.2.2

    Bump decode-uri-component from 0.2.0 to 0.2.2

    Bumps decode-uri-component from 0.2.0 to 0.2.2.

    Release notes

    Sourced from decode-uri-component's releases.

    v0.2.2

    • Prevent overwriting previously decoded tokens 980e0bf

    https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.1...v0.2.2

    v0.2.1

    • Switch to GitHub workflows 76abc93
    • Fix issue where decode throws - fixes #6 746ca5d
    • Update license (#1) 486d7e2
    • Tidelift tasks a650457
    • Meta tweaks 66e1c28

    https://github.com/SamVerschueren/decode-uri-component/compare/v0.2.0...v0.2.1

    Commits

    Dependabot compatibility score

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies javascript 
    opened by dependabot[bot] 0
  • ERROR: docker compose exec php php artisan migrate --seed

    ERROR: docker compose exec php php artisan migrate --seed

    Dear Casper

    Firstly, thank you very much for your generous work here. I tried to install the software on my Centos 7 but got the error when try to run "docker compose exec php php artisan migrate --seed " The error is like this:

    Illuminate\Database\QueryException

    SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name or service not known (SQL: select * from information_schema.tables where table_schema = daybyday and table_name = migrations and table_type = 'BASE TABLE')

    at vendor/laravel/framework/src/Illuminate/Database/Connection.php:671 667| // If an exception occurs when attempting to run a query, we'll format the error 668| // message to include the bindings with SQL, which will make this exception a 669| // lot more helpful to the developer instead of just the database's errors. 670| catch (Exception $e) {

    671| throw new QueryException( 672| $query, $this->prepareBindings($bindings), $e 673| ); 674| } 675|

      +36 vendor frames
    

    37 artisan:30 Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

    Do you know what is wrong here ? Thank you very much.

    opened by xuelangqingkong 0
  • Install issue

    Install issue

    Hello

    I am trying to install Bottelet and on Ubuntu 20.x and I am having this issue. How can I fix it please?

    php artisan migrate --seed Migration table created successfully. Migrating: 2014_10_12_000000_create_users_table Migrated: 2014_10_12_000000_create_users_table (1.53 seconds) Migrating: 2014_10_12_100000_create_password_resets_table Migrated: 2014_10_12_100000_create_password_resets_table (1.26 seconds) Migrating: 2015_06_04_124835_create_industries_table Migrated: 2015_06_04_124835_create_industries_table (0.45 seconds) Migrating: 2015_10_15_143830_create_status_table Migrated: 2015_10_15_143830_create_status_table (0.46 seconds) Migrating: 2015_12_28_163028_create_clients_table Migrated: 2015_12_28_163028_create_clients_table (3.19 seconds) Migrating: 2015_12_29_154026_create_invocies_table Migrated: 2015_12_29_154026_create_invocies_table (1.81 seconds) Migrating: 2015_12_29_204031_projects_table Migrated: 2015_12_29_204031_projects_table (8.1 seconds) Migrating: 2015_12_29_204031_tasks_table Migrated: 2015_12_29_204031_tasks_table (10.08 seconds) Migrating: 2016_01_10_204413_create_comments_table Migrated: 2016_01_10_204413_create_comments_table (2.19 seconds) Migrating: 2016_01_18_113656_create_leads_table Migrated: 2016_01_18_113656_create_leads_table (7.61 seconds) Migrating: 2016_01_23_144854_settings Migrated: 2016_01_23_144854_settings (0.79 seconds) Migrating: 2016_01_26_003903_documents Migrated: 2016_01_26_003903_documents (1.14 seconds) Migrating: 2016_01_31_211926_invoice_lines_table Migrated: 2016_01_31_211926_invoice_lines_table (2.33 seconds) Migrating: 2016_03_21_171847_create_department_table Migrated: 2016_03_21_171847_create_department_table (0.72 seconds) Migrating: 2016_03_21_172416_create_department_user_table Migrated: 2016_03_21_172416_create_department_user_table (3.25 seconds) Migrating: 2016_04_06_230504_integrations Migrated: 2016_04_06_230504_integrations (0.78 seconds) Migrating: 2016_05_21_205532_create_activities_table Migrated: 2016_05_21_205532_create_activities_table (0.63 seconds) Migrating: 2016_08_26_205017_entrust_setup_tables Migrated: 2016_08_26_205017_entrust_setup_tables (11.41 seconds) Migrating: 2016_11_04_200855_create_notifications_table Migrated: 2016_11_04_200855_create_notifications_table (2.29 seconds) Migrating: 2017_10_28_131549_create_contacts_table Migrated: 2017_10_28_131549_create_contacts_table (2.18 seconds) Migrating: 2019_05_03_000001_create_customer_columns Migrated: 2019_05_03_000001_create_customer_columns (1.13 seconds) Migrating: 2019_05_03_000002_create_subscriptions_table Migrated: 2019_05_03_000002_create_subscriptions_table (1.15 seconds) Migrating: 2019_11_29_092917_add_vat_and_currency Migrated: 2019_11_29_092917_add_vat_and_currency (0.33 seconds) Migrating: 2019_11_29_111929_add_invoice_number_to_invoice Migrated: 2019_11_29_111929_add_invoice_number_to_invoice (0.85 seconds) Migrating: 2019_12_09_201950_create_mails_table Migrated: 2019_12_09_201950_create_mails_table (2.26 seconds) Migrating: 2019_12_19_200049_add_billing_integration_id_to_invoices Migrated: 2019_12_19_200049_add_billing_integration_id_to_invoices (0.54 seconds) Migrating: 2020_01_06_203615_create_payments_table Migrated: 2020_01_06_203615_create_payments_table (2.88 seconds) Migrating: 2020_01_10_120239_create_credit_notes_table Migrated: 2020_01_10_120239_create_credit_notes_table (0 seconds) Migrating: 2020_01_10_121248_create_credit_lines_table Migrated: 2020_01_10_121248_create_credit_lines_table (0 seconds) Migrating: 2020_01_28_195156_add_language_options Migrated: 2020_01_28_195156_add_language_options (3.55 seconds) Migrating: 2020_02_20_192015_alter_leads_table_support_qualified Migrated: 2020_02_20_192015_alter_leads_table_support_qualified (2.66 seconds) Migrating: 2020_03_30_163030_create_appointments_table Migrated: 2020_03_30_163030_create_appointments_table (5.06 seconds) Migrating: 2020_04_06_075838_create_business_hours_table Migrated: 2020_04_06_075838_create_business_hours_table (2.18 seconds) Migrating: 2020_04_08_070242_create_absences_table Migrated: 2020_04_08_070242_create_absences_table (2.49 seconds) Migrating: 2020_05_09_113503_add_cascading_for_tables Migrated: 2020_05_09_113503_add_cascading_for_tables (8.85 seconds) Migrating: 2020_09_29_173256_add_soft_delete_to_tables Migrated: 2020_09_29_173256_add_soft_delete_to_tables (0.67 seconds) Migrating: 2021_01_09_102659_add_cascading_for_appointments Migrated: 2021_01_09_102659_add_cascading_for_appointments (2.17 seconds) Migrating: 2021_02_10_153102_create_offers_table Migrated: 2021_02_10_153102_create_offers_table (2.47 seconds) Migrating: 2021_02_11_161257_alter_invoices_table_add_source Migrated: 2021_02_11_161257_alter_invoices_table_add_source (12 seconds) Migrating: 2021_02_11_162602_create_products_table Migrated: 2021_02_11_162602_create_products_table (0.98 seconds) Migrating: 2021_03_02_132033_alter_comments_table_add_long_text Migrated: 2021_03_02_132033_alter_comments_table_add_long_text (1.69 seconds) Seeding: StatusTableSeeder Seeded: StatusTableSeeder (1.6 seconds) Seeding: UsersTableSeeder Seeded: UsersTableSeeder (0.15 seconds) Seeding: IndustriesTableSeeder Seeded: IndustriesTableSeeder (0.08 seconds) Seeding: DepartmentsTableSeeder Seeded: DepartmentsTableSeeder (0.19 seconds) Seeding: SettingsTableSeeder Seeded: SettingsTableSeeder (0.97 seconds) Seeding: PermissionsTableSeeder Seeded: PermissionsTableSeeder (3 seconds) Seeding: RolesTablesSeeder Seeded: RolesTablesSeeder (0.53 seconds) Seeding: RolePermissionTableSeeder Seeded: RolePermissionTableSeeder (8.1 seconds) Seeding: UserRoleTableSeeder Seeded: UserRoleTableSeeder (0.09 seconds) Database seeding completed successfully. apps:/var/www/apps.professionalsoftwaredevelopment.com/projectmanager# php artisan key:generate Application key set successfully. apps:/var/www/apps.professionalsoftwaredevelopment.com/projectmanager# npm install npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm WARN deprecated [email protected]: This module relies on Node.js's internals and will break at some point. Do not use it, and update to [email protected]. npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410 npm WARN deprecated [email protected]: This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x. npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

    added 1070 packages, and audited 1071 packages in 20s

    1 package is looking for funding run npm fund for details

    62 vulnerabilities (23 moderate, 32 high, 7 critical)

    To address issues that do not require attention, run: npm audit fix

    To address all issues (including breaking changes), run: npm audit fix --force

    Run npm audit for details.

    npm audit fix --force

    npm audit fix --force

    Run npm audit for details. apps:/var/www/apps.professionalsoftwaredevelopment.com/projectmanager# npm audit fix --force npm WARN using --force Recommended protections disabled. npm WARN audit fix [email protected] node_modules/fsevents/node_modules/minimatch npm WARN audit fix [email protected] is a bundled dependency of npm WARN audit fix [email protected] [email protected] at node_modules/fsevents npm WARN audit fix [email protected] It cannot be fixed automatically. npm WARN audit fix [email protected] Check for updates to the fsevents package. npm WARN audit fix [email protected] node_modules/fsevents/node_modules/rc/node_modules/minimist npm WARN audit fix [email protected] is a bundled dependency of npm WARN audit fix [email protected] [email protected] at node_modules/fsevents npm WARN audit fix [email protected] It cannot be fixed automatically. npm WARN audit fix [email protected] Check for updates to the fsevents package. npm WARN audit fix [email protected] node_modules/fsevents/node_modules/minimist npm WARN audit fix [email protected] is a bundled dependency of npm WARN audit fix [email protected] [email protected] at node_modules/fsevents npm WARN audit fix [email protected] It cannot be fixed automatically. npm WARN audit fix [email protected] Check for updates to the fsevents package. npm WARN audit fix [email protected] node_modules/fsevents/node_modules/tar npm WARN audit fix [email protected] is a bundled dependency of npm WARN audit fix [email protected] [email protected] at node_modules/fsevents npm WARN audit fix [email protected] It cannot be fixed automatically. npm WARN audit fix [email protected] Check for updates to the fsevents package. npm WARN audit fix [email protected] node_modules/fsevents/node_modules/mkdirp npm WARN audit fix [email protected] is a bundled dependency of npm WARN audit fix [email protected] [email protected] at node_modules/fsevents npm WARN audit fix [email protected] It cannot be fixed automatically. npm WARN audit fix [email protected] Check for updates to the fsevents package. npm WARN audit Updating axios to 1.1.3, which is a SemVer major change. npm WARN audit Updating laravel-mix to 6.0.49, which is a SemVer major change.

    added 346 packages, removed 285 packages, changed 359 packages, and audited 1131 packages in 18s

    86 packages are looking for funding run npm fund for details

    npm audit report

    glob-parent <5.1.2 Severity: high glob-parent before 5.1.2 vulnerable to Regular Expression Denial of Service in enclosure regex - https://github.com/advisories/GHSA-ww39-953v-wcq6 fix available via npm audit fix node_modules/glob-parent chokidar 1.0.0-rc1 - 2.1.8 Depends on vulnerable versions of glob-parent node_modules/chokidar watchpack 0.2.2 - 1.6.1 Depends on vulnerable versions of chokidar node_modules/watchpack

    loader-utils <=1.4.1 Severity: critical Prototype pollution in webpack loader-utils - https://github.com/advisories/GHSA-76p3-8jx3-jpfq loader-utils is vulnerable to Regular Expression Denial of Service (ReDoS) via url variable - https://github.com/advisories/GHSA-3rfm-jhwj-7488 loader-utils is vulnerable to Regular Expression Denial of Service (ReDoS) - https://github.com/advisories/GHSA-hhq3-ff78-jv3g fix available via npm audit fix --force Will install [email protected], which is a breaking change node_modules/loader-utils resolve-url-loader 1.0.3 - 2.0.0 || 3.0.1 - 4.0.0-beta.2 Depends on vulnerable versions of loader-utils node_modules/resolve-url-loader

    minimatch <3.0.5 Severity: high minimatch ReDoS vulnerability - https://github.com/advisories/GHSA-f8q6-p94x-37v3 fix available via npm audit fix node_modules/minimatch

    minimist <=1.2.5 Severity: critical Prototype Pollution in minimist - https://github.com/advisories/GHSA-xvch-5gv4-984h Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m fix available via npm audit fix node_modules/minimist node_modules/rc/node_modules/minimist mkdirp 0.4.1 - 0.5.1 Depends on vulnerable versions of minimist node_modules/mkdirp

    tar <=4.4.17 Severity: high Arbitrary File Creation/Overwrite on Windows via insufficient relative path sanitization - https://github.com/advisories/GHSA-5955-9wpr-37jh Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links - https://github.com/advisories/GHSA-qq89-hq3f-393p Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning using symbolic links - https://github.com/advisories/GHSA-9r2w-394v-53qc Arbitrary File Creation/Overwrite due to insufficient absolute path sanitization - https://github.com/advisories/GHSA-3jfq-g458-7qm9 Arbitrary File Creation/Overwrite via insufficient symlink protection due to directory cache poisoning - https://github.com/advisories/GHSA-r628-mhmh-qjhw fix available via npm audit fix node_modules/tar

    9 vulnerabilities (1 moderate, 5 high, 3 critical)

    To address issues that do not require attention, run: npm audit fix

    To address all issues (including breaking changes), run: npm audit fix --force

    npm audit report

    glob-parent <5.1.2 Severity: high glob-parent before 5.1.2 vulnerable to Regular Expression Denial of Service in enclosure regex - https://github.com/advisories/GHSA-ww39-953v-wcq6 fix available via npm audit fix node_modules/watchpack-chokidar2/node_modules/glob-parent chokidar 1.0.0-rc1 - 2.1.8 Depends on vulnerable versions of glob-parent node_modules/watchpack-chokidar2/node_modules/chokidar watchpack-chokidar2 * Depends on vulnerable versions of chokidar node_modules/watchpack-chokidar2 watchpack 1.7.2 - 1.7.5 Depends on vulnerable versions of watchpack-chokidar2 node_modules/watchpack

    4 high severity vulnerabilities

    To address all issues, run: npm audit fix

    apps:/var/www/apps.professionalsoftwaredevelopment.com/projectmanager# npm run dev

    dev node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

    [webpack-cli] Error: Unknown option '--hide-modules' [webpack-cli] Run 'webpack --help' to see available commands and options apps:/var/www/apps.professionalsoftwaredevelopment.com/projectmanager# npm run dev

    dev node node_modules/cross-env/dist/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

    [webpack-cli] Error: Unknown option '--hide-modules' [webpack-cli] Run 'webpack --help' to see available commands and options apps:/var/www/apps.professionalsoftwaredevelopment.com/projectmanager#

    opened by ptaylor2 0
  • Bump loader-utils, webpack-cli and resolve-url-loader

    Bump loader-utils, webpack-cli and resolve-url-loader

    Bumps loader-utils to 1.4.2 and updates ancestor dependencies loader-utils, webpack-cli and resolve-url-loader. These dependencies need to be updated together.

    Updates loader-utils from 1.2.3 to 1.4.2

    Release notes

    Sourced from loader-utils's releases.

    v1.4.2

    1.4.2 (2022-11-11)

    Bug Fixes

    v1.4.1

    1.4.1 (2022-11-07)

    Bug Fixes

    v1.4.0

    1.4.0 (2020-02-19)

    Features

    • the resourceQuery is passed to the interpolateName method (#163) (cd0e428)

    v1.3.0

    1.3.0 (2020-02-19)

    Features

    • support the [query] template for the interpolatedName method (#162) (469eeba)
    Changelog

    Sourced from loader-utils's changelog.

    1.4.2 (2022-11-11)

    Bug Fixes

    1.4.1 (2022-11-07)

    Bug Fixes

    1.4.0 (2020-02-19)

    Features

    • the resourceQuery is passed to the interpolateName method (#163) (cd0e428)

    1.3.0 (2020-02-19)

    Features

    • support the [query] template for the interpolatedName method (#162) (469eeba)

    Commits

    Updates webpack-cli from 3.3.9 to 3.3.12

    Changelog

    Sourced from webpack-cli's changelog.

    3.3.12 (2020-06-03)

    Full Changelog

    3.3.11 (2020-02-11)

    Full Changelog

    3.3.10 (2019-10-31)

    Full Changelog

    New Features

    • add new flag and patch sec dep (#1102)

    Commits
    Maintainer changes

    This version was pushed to npm by evilebottnawi, a new releaser for webpack-cli since your current version.


    Updates resolve-url-loader from 3.1.0 to 5.0.0

    Release notes

    Sourced from resolve-url-loader's releases.

    5.0.0

    Breaking changes

    • Require node>=12.
    • Support only webpack>=4.
    • Update to postcss@^8.
    • Remove rework engine (which was deprecated in V4).

    Bugfixes

    • Fix log messages not correctly normalising absolute paths to posix style on Windows platform
    • Fixes to end-to-end tests and test framework.

    5.0.0-beta.1

    Breaking changes

    • Require node>=12.
    • Support only webpack>=4.
    • Update to postcss@^8.
    • Remove rework engine (which was deprecated in V4).

    Bugfixes

    • Fix log messages not correctly normalising absolute paths to posix style on Windows platform
    • Fixes to end-to-end tests and test framework.

    5.0.0-alpha.1

    Breaking changes

    • Require node>=12.
    • Support only webpack>=4.
    • Update to postcss@^8.
    • Remove rework engine (which was deprecated in V4).

    Bugfixes

    • Fix log messages not correctly normalising absolute paths to posix style on Windows platform

    4.0.0

    Features

    • Better resolution of the original source location - You can more successfully use url() in variables and mixins.
    • Dependencies now accept a wider range and explicit dependency on rework and rework-visit has been removed.

    Breaking Changes

    • The engine option is deprecated which means the old rework engine is deprecated.
    • The keepQuery behaviour is now the default, the keepQuery option has been removed.
    • The removeCR option defaults to true when executing on Windows OS.
    • The absolute option has been removed.
    • The join option has changed.

    Migrating

    See the changlog.

    ... (truncated)

    Changelog

    Sourced from resolve-url-loader's changelog.

    resolve-url-loader

    Version 5

    Features

    • Update postcss and completely remove rework parser.

    Breaking Changes

    • Require node@>=12.
    • Support webpack@>=4 (no longer tested for earlier versions).
    • The engine option has been removed.

    Migrating

    Remove the engine option if you are using it.

    Version 4

    Features

    • Better resolution of the original source location - You can more successfully use url() in variables and mixins.
    • Dependencies now accept a wider range and explicit dependency on rework and rework-visit has been removed.

    Breaking Changes

    • The engine option is deprecated which means the old rework engine is deprecated.
    • The keepQuery behaviour is now the default, the keepQuery option has been removed.
    • The removeCR option defaults to true when executing on Windows OS.
    • The absolute option has been removed.
    • The join option has changed.

    Migrating

    Remove the engine option if you are using it - the default "postcss" engine is much more reliable. The "rework" engine will still work for now but will be removed in the next major version.

    Remove the keepQuery option if you are using it.

    Remove the absolute option, webpack should work fine without it. If you have a specific need to rebase url() then you should use a separate loader.

    If you use a custom join function then you will need to refactor it to the new API. Refer to the advanced usage documentation.

    If you wish to still use engine: "rework" then note that rework and rework-visit packages are now peerDependencies that must be explicitly installed by you.

    Version 3

    Features

    • Use postcss parser by default. This is long overdue as the old rework parser doesn't cope with modern css.

    ... (truncated)

    Commits
    • bf01da9 5.0.0
    • 78393f6 update branch references to v5
    • 6787839 github actions for CI
    • 1457038 update changelog and readme
    • a01faf9 5.0.0-beta.1
    • fb09fae remove the engine option harder, ensure deprecation warning is tested
    • 5654fa4 remove the engine option and related tests, use getOptions from loader where ...
    • 10f9cdb 5.0.0-alpha.1
    • b168dd3 adjust deprecation message for engine option
    • 29e142a normalise windows absolute paths to posix format in log messages
    • Additional commits viewable in compare view

    Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


    Dependabot commands and options

    You can trigger Dependabot actions by commenting on this PR:

    • @dependabot rebase will rebase this PR
    • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
    • @dependabot merge will merge this PR after your CI passes on it
    • @dependabot squash and merge will squash and merge this PR after your CI passes on it
    • @dependabot cancel merge will cancel a previously requested merge and block automerging
    • @dependabot reopen will reopen this PR if it is closed
    • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
    • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
    • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
    • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
    • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
    • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

    You can disable automated security fix PRs for this repo from the Security Alerts page.

    dependencies javascript 
    opened by dependabot[bot] 0
Releases(2.2.1)
  • 2.2.1(Dec 1, 2021)

    What's Changed

    • Bump phpseclib/phpseclib from 2.0.28 to 2.0.31 by @dependabot in https://github.com/Bottelet/DaybydayCRM/pull/240
    • Bump y18n from 4.0.0 to 4.0.1 by @dependabot in https://github.com/Bottelet/DaybydayCRM/pull/238
    • Bump axios from 0.18.1 to 0.21.1 by @dependabot in https://github.com/Bottelet/DaybydayCRM/pull/220
    • Bump ssri from 6.0.1 to 6.0.2 by @dependabot in https://github.com/Bottelet/DaybydayCRM/pull/246
    • Bump vis-timeline from 7.3.4 to 7.4.4 by @dependabot in https://github.com/Bottelet/DaybydayCRM/pull/244
    • Bump laravel/framework from 7.25.0 to 7.30.4 by @dependabot in https://github.com/Bottelet/DaybydayCRM/pull/229
    • Bump facade/ignition from 2.3.6 to 2.4.2 by @dependabot in https://github.com/Bottelet/DaybydayCRM/pull/242
    • Bump elliptic from 6.5.3 to 6.5.4 by @dependabot in https://github.com/Bottelet/DaybydayCRM/pull/233

    Full Changelog: https://github.com/Bottelet/DaybydayCRM/compare/2.2.0...2.2.1

    Source code(tar.gz)
    Source code(zip)
  • 2.2.0(Apr 9, 2021)

  • 2.1.0(Aug 25, 2020)

    Added spanish localization Added spain as a country option with currency Upgraded to Laravel 7 Roles can now only be updated and accsed by admin and owners Removed last of the repository pattern

    Upgrade Guide: Very simple Pull down the latest changes into your own project. Do and composer update.

    That should be it.

    Source code(tar.gz)
    Source code(zip)
  • 2.0.0(Jun 23, 2020)

    For detailed information go to: https://medium.com/@casperbottelet/daybydaycrm-becomes-open-source-d40a4041ce6c

    1. Introduced a horizontal calendar for users to see appointments they have and other users have, with the ability to link to a lead, task, or project.
    2. Absence tracking, the ability for users with the “HR permission” to see users’ absence and add absence for given user, all users can add absence on their profile, absences are reflected in the calendar, so it’s easy to get an overview
    3. A lead will start by being unqualified and can now be converted to a qualified lead, to an order/invoice, or be directly closed in the new sidebar view, for unqualified leads which have been re-written to VueJs.
    4. Information and activity sidebar has been added for Tasks, Projects and leads, to easily get an overview of the necessary information, and the flow of a given source.
    5. Added the option to attach files to tasks, clients, and projects, which can be everything from contracts on the customers to wireframes on a given project.
    6. Overall a lot of design changes, new colors, and better flow through different screens.
    7. Added a topbar, to easily access user’s settings, the possibility to register absence, see the notification, actions, etc.
    8. Made Status Polymorphic, so down the road, it’s possible to add your status from the UI for the different sources such as tasks.8.
    9. Made more settings, able to set Company name, country, vat percentage, and open business hours.
    10. Set a starting Invoice number, and the customer number the default is 10000 and will increment for each created invoice, and customer.
    11. It’s now possible to set Currency and vat percentage.
    12. Made invoices more a bit more complex with calculating taxes, adding the currency for the given country.
    13. The first time logging in the user will be prompted to give some basic information from step 9.
    14. Global search, users can activate or deactivate Elasticsearch in config/services if Elasticsearch is disabled(default) it will user query search.
    15. Projects have been introduced as a project is a wrapper for many tasks, and give you the options to move tasks around in their different status on a scrum like board.
    16. Generally, a lot of refactoring of the code, some for better some for worse, add some more tests.
    Source code(tar.gz)
    Source code(zip)
    daybyday-campaign.png(130.79 KB)
  • 1.3.7(Aug 2, 2019)

    This update standardizes the way anyData and myData methods are written for Clients, Contacts, Leads and Tasks. It is not necessary for existing users to upgrade to this version.

    This update also adds the application version to the page title once the user has logged in successfully.

    If you're tracking the master branch using git, issue the following command to update from 1.2 or newer:

    git checkout 1.3.7
    

    No database changes if you're upgrading from 1.2 or newer. If you're upgrading from a version earlier than 1.2, you're strongly encouraged to backup your database and read the release notes for the the newer versions you'll be upgrading through/to. We strongly recommend stepping through each release to make sure you're completing all the upgrade requirements.

    Source code(tar.gz)
    Source code(zip)
  • 1.3.6(Jul 17, 2019)

    This update adds a DummyDatabaseSeeder class which makes it easier for admins installing Flarepoint to quickly seed the database with dummy data. It is not necessary for existing users to upgrade to this version.

    If you're tracking the master branch using git, issue the following command to update from 1.2 or newer:

    git checkout 1.3.6
    

    The wiki page for Insertion of Dummy Data has also been updated to reflect this change.

    No database changes if you're upgrading from 1.2 or newer. If you're upgrading from a version earlier than 1.2, you're strongly encouraged to backup your database and read the release notes for the the newer versions you'll be upgrading through/to. We strongly recommend stepping through each release to make sure you're completing all the upgrade requirements.

    Source code(tar.gz)
    Source code(zip)
  • 1.3.5(Jul 9, 2019)

    fixed #120

    This update simplifies and fixes issues with deleting a user. Please take a look at the tooltip in the Delete User modal for how clients are handled when you choose to delete all clients assigned to the user.

    If you're tracking the master branch using git, issue the following command to update from 1.2 or newer:

    git checkout 1.3.5
    

    No database changes if you're upgrading from 1.2 or newer. If you're upgrading from a version earlier than 1.2, you're strongly encouraged to backup your database and read the release notes for the the newer versions you'll be upgrading through/to. We strongly recommend stepping through each release to make sure you're completing all the upgrade requirements.

    Source code(tar.gz)
    Source code(zip)
  • 1.3.4(Jul 5, 2019)

    This hotfix fixes an issue were user selects in the Delete User modal weren't populated. If you're tracking releases with git, the following command will upgrade you to 1.3.4:

    git checkout 1.3.4
    

    No database changes if you're upgrading from 1.2 or newer. If you're upgrading from a version earlier than 1.2, you're strongly encouraged to backup your database and read the release notes for the the newer versions you'll be upgrading through/to. We strongly recommend stepping through each release to make sure you're completing all the upgrade requirements.

    Source code(tar.gz)
    Source code(zip)
  • 1.3.3(Jul 4, 2019)

    For those who would like to run Flarepoint in a Docker container, the Docker configuration was updated to support PHP 7.2 and simplify the configuration overall. If you're tracking the master branch using git, run this command to update

    git checkout 1.3.3
    

    No database changes if you're upgrading from 1.2 or newer. If you're upgrading from a version earlier than 1.2, you're strongly encouraged to backup your database and read the release notes for the the newer versions you'll be upgraded through/to. We strongly recommend stepping through each release to make sure you're completing all the upgrade requirements.

    Thanks, @slayerbleast for the contribution!

    Source code(tar.gz)
    Source code(zip)
  • 1.3.2(Jul 3, 2019)

    This release fixes issue #118. You can update to this release with the following command, if you're tracking releases with git:

    git checkout 1.3.2

    No database changes if you're upgrading from 1.2 or newer. If you're upgrading from a version earlier than 1.2, you're strongly encouraged to backup your database and read the release notes for the the newer versions you'll be upgraded through/to. We strongly recommend stepping through each release to make sure you're completing all the upgrade requirements.

    Source code(tar.gz)
    Source code(zip)
  • 1.3(Jun 27, 2019)

    This version introduces "my" views for clients, contacts, tasks and leads. These views show only the records assigned to you.

    This update doesn't make any changes to the database. So it's safe to upgrade from Flarepoint 1.2. If you are upgrading from 1.1.6 or older, you are strongly encouraged to make a backup of your Flarepoint database before attempting to upgrade to Flarepoint 1.3. You should also read the notes from the 1.2 release, since that made changes to the Client model and added a new Contact model for separate contact management.

    The upgrade instructions below assume that you cloned this repository using git rather than downloading a release ZIP file. Future versions of Flarepoint may include instructions for installing and upgrading using the ZIP. But at this time, you're on your own.

    To upgrade from 1.2 to 1.3, perform the following steps:

    • Run: git checkout 1.3
    Source code(tar.gz)
    Source code(zip)
  • 1.2(Jun 26, 2019)

    This version introduces separate contact management from the client record. This allows a user to create multiple contacts for a client. If there is only one contact for a client, you may still put primary contact information in the client record.

    Any existing client records you've created in Flarepoint 1.1.6 will be split into a client record and a single contact record when you migrate. For safety, the contact information in the client record is not deleted. It is only copied to a new contact record.

    Also note that end-users should switch to the master branch, since develop will no longer be considered stable enough for production use.

    You are strongly encouraged to make a backup of your Flarepoint database before attempting to upgrade to Flarepoint 1.2.

    The upgrade instructions below assume that you cloned this repository using git rather than downloading a release ZIP file. Future versions of Flarepoint may include instructions for installing and upgrading using the ZIP. But at this time, you're on your own.

    To upgrade from 1.1.6 to 1.2, perform the following steps:

    • Run: git checkout master
    • Run: git pull
    • Run: composer install
    • Run: php artisan migrate
    • In production, make sure APP_DEBUG is set to false in your .env file. Otherwise, Debugbar will show up.
    • Login to Flarepoint as the admin user.
    • Go to Settings -> Overall Settings.
    • Enable the "Create contact", "Update contact" and "Delete contact" permissions for each role that should have those permissions.
    Source code(tar.gz)
    Source code(zip)
  • 1.1.5(Dec 24, 2016)

  • 1.1.4(Dec 18, 2016)

    Vuejs has been upgraded from v1 to v2, the user show blade has been updated to use tabs, and includes graphs aswell now, element-UI has been added, and there is a better use of elixir to include bootstrap Vue Vue-resources etc.

    Source code(tar.gz)
    Source code(zip)
  • 1.1.3(Nov 13, 2016)

  • 1.1(Aug 5, 2016)

  • V1(Jul 13, 2016)

Owner
Casper Bottelet
Casper Bottelet
Crater is an open-source web & mobile app that helps you track expenses, payments & create professional invoices & estimates.

Introduction Crater is an open-source web & mobile app that helps you track expenses, payments & create professional invoices & estimates. Web Applica

Bytefury 6.7k Jan 1, 2023
Simple Laravel Invoice Generator Sling — open-source web application that helps you create invoices and track income.

Simple Laravel Invoice Generator Sling — open-source web application that helps you create invoices and track income. Table of Contents About

Ray Icemont 4 Nov 22, 2022
EspoCRM open source CRM application

EspoCRM is an Open Source CRM (Customer Relationship Management) software that allows you to see, enter and evaluate all your company relationships regardless of the type. People, companies or opportunities - all in an easy and intuitive interface.

EspoCRM - Open Source CRM 1k Dec 29, 2022
OroCRM is an open source Client Relationship Management (CRM) application

OroCRM is an open source Client Relationship Management (CRM) application that allows to create a 360° view of your customers across multiple channels, organize the sales pipeline, manage account and contact information, communicate with customers, run marketing campaigns and track campaign performance.

Oro, Inc. 611 Jan 3, 2023
Our team created for you one of the most innovative CRM systems that supports mainly business processes and allows for customization according to your needs. Be ahead of your competition and implement YetiForce!

We design an innovative CRM system that is dedicated for large and medium sized companies. We dedicate it to everyone who values open source software,

YetiForce Sp. z o.o. 1.3k Jan 8, 2023
CRUD php application to check in and check out employees and show daily building occupation

CRUD php application to check in and check out employees and show daily building occupation. Employees are required to self check their temperature and tick a checkbox to specify whether their temperature is below 38°C else they are invited to stay home. (Implemented in php with bootstrap4 for styling and datatable jquery plugin for table formatting and additional features).

null 2 Feb 20, 2022
Remindle is here to help you remember. Remember everything you want, by the means you prefer, in the frequency you like

platform Personal reminders About Remindle Remindle is a platform which helps you to remember all important events. You can set the means you’d like t

Remindle 4 Dec 23, 2021
Keep your forms alive, avoid `TokenMismatchException` by gently poking your Laravel app.

Poke Keep your forms alive, avoid TokenMismatchException by gently poking your Laravel app. Keep this package free Your support allows me to keep this

Laragear 12 Nov 28, 2022
Dolibarr ERP & CRM is a modern software package that helps manage your organization's activity (contacts, suppliers, invoices, orders, stocks, agenda…).

Dolibarr ERP CRM is a modern software package to manage your company or foundation activity (contacts, suppliers, invoices, orders, stocks, agenda, accounting, ...). It is open source software written in PHP and designed for small and medium businesses, foundations and freelancers. You can freely install, use and distribute it as a standalone application or as a web application to use it from every internet access and media.

Dolibarr ERP & CRM 3.7k Jan 7, 2023
Self-hosted platform to keep and share your content: web links, posts, passwords and pictures.

Shaark is a self-hosted platform to keep and share your content: web links, posts, passwords and pictures. All of your data can be private, public or

MarceauKa 482 Dec 30, 2022
FreeScout — Free self-hosted help desk & shared mailbox (Zendesk / Help Scout alternative)

Free Self-Hosted Zendesk & Help Scout Alternative FreeScout is the super lightweight free open source help desk and shared inbox written in PHP7+ (Lar

FreeScout 1.8k Jan 2, 2023
LiveZilla - a help desk software that offers a help desk solution for small companies to large businesses

LiveZilla includes a live chat software with multi-website support, visitor monitoring and a help desk system that allows you to not only integrate emails that you receive from customers but also messages from Twitter and Facebook in your ticket system.

Maher Amara 9 Nov 10, 2022
This plugin was created to help you migrate your existing gallery from your old site.

WP Migrate Gallery 1. Steps to Import Gallery 1.1. Install ACF PRO 1.2. Create CPT Gallery 1.3. Create Gallery Taxomy 1.4. Copy Gallery media files to

null 3 Jun 23, 2022
CRM project that I developed with ReactJS and Laravel 8.

About Laravel Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable and creative experie

Harun Doğdu 4 Nov 28, 2021
Customer Relationship Management (CRM) portal using PHP Codeigniter 4 & Tailwind CSS framework.

CRM Portal Customer Relationship Management (CRM) portal using PHP Codeigniter 4 & Tailwind CSS framework. Screenshots User (Dashboard) Admin (Employe

Dawood Khan Masood 5 Feb 2, 2022
ZAP CRM is Customer Relationship Management portal built using PHP Codeigniter 4 & Tailwind CSS framework.

ZAP CRM ZAP CRM is Customer Relationship Management portal built using PHP Codeigniter 4 & Tailwind CSS framework. Screenshots User (Dashboard) Admin

Dawood Khan Masood 5 Feb 2, 2022
Track the memory usage of your workers and display them in Filament.

Filament Memory Tracker Track the memory usage of your workers and display them in Filament. Installation Install the package via composer: composer r

Theraloss 22 Oct 9, 2022
Kyle is a web application built with Laravel for web developers and small companies to efficiently track and stay on top of yearly expenses related to services

Kyle Kyle is a web application built with Laravel for web developers and small companies to efficiently track and stay on top of yearly expenses relat

Laravelista 36 Jul 15, 2022