Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.6.0-alpha.4] Custom sections doesn't working #3627

Closed
afbora opened this issue Aug 10, 2021 · 4 comments
Closed

[3.6.0-alpha.4] Custom sections doesn't working #3627

afbora opened this issue Aug 10, 2021 · 4 comments

Comments

@afbora
Copy link
Member

afbora commented Aug 10, 2021

Describe the bug

The section type "modified" is not valid

I'm getting above error when i try to implement custom sections like following sample. Btw I've tested on 3.6.0-alpha.1 and doesn't working too. But working on 3.5.7.1.

Kirby::plugin('yourname/modified', [
    'sections' => [
        'modified' => [
            'props' => [
                'headline' => function ($headline) {
                    return $headline;
                }
            ]
        ]
    ]
]);

Kirby Version

3.6.0-alpha.4

@afbora
Copy link
Member Author

afbora commented Aug 10, 2021

Source of this issue is pagetable plugin with following error. Also this issue brokes other plugins load. I added to broken list #3485

Uncaught TypeError: Cannot read property 'TYPED_ARRAY_SUPPORT' of undefined

@afbora afbora closed this as completed Aug 10, 2021
@afbora
Copy link
Member Author

afbora commented Aug 10, 2021

@distantnative @bastianallgeier I've tracked down the issue and found the source of issue.
We started to use <script type="module"> in Panel 3.6.0 and parcel doesn't support that: parcel-bundler/parcel#2833
Should I open a separate issue? Seemed like a big problem to me.

@distantnative
Copy link
Member

Yes please. That could be a big issue indeed. As far as I know we need type module for vite to work.

@afbora
Copy link
Member Author

afbora commented Aug 10, 2021

I've created new issue about that #3628

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants