Hello!

I have cloned this project and followed install steps but I only have a white screen. Debugbar dont throw any info.

How I can proceed to solve it?

My repository is here: https://github.com/jjmontalban/Enso

Any advice will be well received

Best regards!

Add replace note about date-fns move (used for custom components & in "transition" state for resources/js/components/enso

note: marking as draft pull until fully upgraded, to group all further missing changes/notes here. (almost through everything though, so I don't expect anything more significant missing from the changelog/upgrade steps)

Hi, I'm facing problems with meta information after updating to 2.3.x version. In particular, meta.appName is blank and I'm getting authentication errors related to CSRF token (this is the message gotten after a successful authentication: "can't assign to property "csrfToken in enso.js line 323").

From where can I set meta tags? Thanks

I have a table where I use a renderer for a column. The renderer is defined as:

customRender(row, column) {
	            switch (column.name) {
		            case 'document_url':
		                return row[column.name] ? `<a href="${row[column.name]}" target="_blank" class="button is-small is-table-button is-primary"><span class="icon is-small"><fa icon="cloud-upload-alt"></fa></span>`
		                    : ``;
		            default:
		                toastr.warning(`render for column ${column.name} is not defined.`);
		                return this.__(row[column.name]);
	            }
	        }

At the moment the icon is not displayed correctly (and in dom its still <fa icon="cloud-upload-alt"></fa> instead of svg tag.

If I use the icon anywhere else on the same page it works (means it is imported correctly)

I am attempting to login using the [email protected] and password credentials. I seeded my tables and I see the entry on the users table for [email protected]

Nothing happens after I hit Login.

My URL for testing Enzo SPA is: http://admin.digihometour.com/login

Output: ERROR Failed to apply patch for package bulma-rtl

This happened because the patch file patches\bulma-rtl+0.7.1.patch could not be parsed.

If you just upgraded patch-package, you can try running:

cd patches\bulma-rtl+0.7.1.patc
patch -p1 -i h
npx patch-package bulma-rtl
cd ../..

Otherwise, try manually creating the patch file again.

If the problem persists, please submit a bug report:

https://github.com/ds300/patch-package/issues/new?title=Patch+file+parse+error&body=%3CPlease+attach+the+patch+file+in+question%3E

error Command failed with exit code 1. child_process.js:650 throw err; ^

Error: Command failed: yarn run postinstall

ERROR Failed to apply patch for package bulma-rtl

This happened because the patch file patches\bulma-rtl+0.7.1.patch could not be parsed.

If you just upgraded patch-package, you can try running:

cd patches\bulma-rtl+0.7.1.patc
patch -p1 -i h
npx patch-package bulma-rtl
cd ../..

Otherwise, try manually creating the patch file again.

If the problem persists, please submit a bug report:

https://github.com/ds300/patch-package/issues/new?title=Patch+file+parse+error&body=%3CPlease+attach+the+patch+file+in+question%3E

error Command failed with exit code 1.

at checkExecSyncError (child_process.js:607:13)
at execSync (child_process.js:647:13)
at Object.<anonymous> (D:\paradox\Programming\OpenServer\domains\enso\CLIENT\node_modules\postinstall-postinstall\run.js:15:5)
at Module._compile (module.js:653:30)
at Object.Module._extensions..js (module.js:664:10)
at Module.load (module.js:566:32)
at tryModuleLoad (module.js:506:12)

This is a feature request.

Prerequisites

• [X] Are you running the latest version?
• [X] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
• [X] Did you check the documentation?
• [X] Did you perform a cursory search?

Description

tailwindcss theme

a clone of the current bulma theme using tailwind

this theme is using TailwindCss V1.0.0-beta4, so it will be ready for the final verstion with this configurations, only to keep the look

this is only a mockup using Vue and tailwindcss to divide it for each enso component, so it will be easy to add it.

const defaultTheme = require("tailwindcss/defaultTheme");

module.exports = {
  theme: {
    // Some useful comment
    extend: {
      colors: {
        white: {
          default: "#ffffff",
          smoke: "#f5f5f5"
        },
        gray: {
          ...defaultTheme.colors.gray,
          290: "#4a4a4a",
          480: "#7a7a7a",
          860: "#dbdbdb"
        },
        blue: {
          ...defaultTheme.colors.blue,
          450: "#3273dc"
        },
        green: {
          ...defaultTheme.colors.green,
          450: "#23d160"
        }
      },
      fontFamily: {
        enso: ["Montserrat", "sans-serif"]
      },
      height: {
        13: "3.25rem"
      },
      inset: {
        13: "3.25rem"
      },
      boxShadow: {
        bnavbar: "0 1px 1px rgba(10, 10, 10, 0.35)",
        bbookmarks: "0 1px 1px rgba(10, 10, 10, 0.2)",
        bsidebar: "0 2px 3px rgba(10, 10, 10, 0.35)"
      }
    }
  },
};

if there is an other idea for a different theme, i can change it. if its ok, i can start merging it with enso and make a PR.

ps: there is no :bug: https://github.com/laravel-enso/Enso/issues/125#issue-348854265

This is a question.

Prerequisites

• [x] Are you running the latest version?
• [x] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
• [x] Did you check the documentation?
• [x] Did you perform a cursory search?

Description

I use an own custom theme. In general everything works like expected but I have 2 questions:

1. How is the default theme for login choosen? I deleted/commented every occurence of light/dark theme in code but still the light theme and not my default is choosen (after deleting cache and everything). If I log in and out my custom theme is choosen for login screen. I also set the theme in index.blade.php
2. What's the source for theme selector (...mapState('layout', ['themes']),). The light/dark selector is shown in my app (what means that more than one theme is available)

This is a bug.

Prerequisites

• [x] Are you running the latest version?
• [x] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
• [x] Did you check the documentation?
• [x] Did you perform a cursory search?

Description

Steps to Reproduce

1. Upgrade to 11.12[.2]
2. Follow CHANGELOG.md upgrade steps (maybe related to #152? couldn't find anything to change as we didn't extend applicable packages yet; except for core usage of them)
3. Log in, note a blank menu & above errors

Expected behavior

App to work

Actual behavior

Enso-part of app mostly non-functional (blank menu, notification menu broken, ...)

I did the icon update as described but as you can see in screenshots not all icons are working. Some are for my new menu items this is ok, I have to change them manually but some are from the default items like tachometer in dashboard.

Did I forgot something? Additionally the spaces between the cards are also missing. This can be a problem in combination with the missing icons?

This is a bug.

Prerequisites

• [x] Are you running the latest version?
• [x] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
• [x] Did you check the documentation?
• [x] Did you perform a cursory search?

Description

I use the following config:

• I run laravel enso in docker
• I mapped port 8001 to 8080 in docker
• I access laravel enso with http://localhost:8001/login
• In my .env File in client folder I defined API_URL=http://localhost:8001/

Expected behavior

Browser should show login screen after calling http://localhost:8001/login

Actual behavior

I get the following error for: http://localhost:8001/api/meta Proxy error: Could not proxy request /api/meta from localhost:8001 to http://localhost:8080/ (ECONNRESET).

Bumps tinymce from 5.10.3 to 5.10.7.

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.

Bumps decode-uri-component from 0.2.0 to 0.2.2.

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.

This is a bug.

Prerequisites

• [x] Are you running the latest version?
• [x] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
• [x] Did you check the documentation?
• [x] Did you perform a cursory search?

Description

• Login to https://www.laravel-enso.com/
• Clear your cookies.
• Logout.

Expected result: redirect to login page. Actual result: nothing happens.

Note: If you click on another menu, it will redirect to login.

Bumps terser from 4.8.0 to 4.8.1.

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.

This is a bug.

Hi,

You have set a while ago a composer.json dependency for

        "symfony/http-client": "^6.0",
        "symfony/mailgun-mailer": "^6.0"

Which at that time was matching with version 6.0.X which was required PHP >=8.0.

Both http-client and mailgun-mailer have released 6.1.X which bumped PHP requirements to >=8.1

Now, upgrading (late) to Laravel-enso 5.0.0 will force (due to these 2 dependencies) an upgrade to 8.1, or force user investigate which dependencies are asking for the upgrade, and try lowering the versions to a compatible version.

In our case we went for

        "symfony/http-client": "6.0.*",
        "symfony/mailgun-mailer": "6.0.*"

This is a feature request.

Prerequisites

• [x] Are you running the latest version?
• [x] Are you reporting to the correct repository? (enso is made of many specialized packages: https://github.com/laravel-enso)
• [x] Did you check the documentation?
• [x] Did you perform a cursory search?

Description

Any plans on upgrading to FA6? I've updated to 6 locally, but Enso still has dependencies in some modules with 5.13...

Thanks!