Uncaught ReferenceError: currentlyReorderingStatus is not defined #1432

jclee100 · 2023-10-20T06:49:16Z

jclee100
Oct 20, 2023

Not sure what am I missing. I can filter but I cannot sort. However, after apply filters, sort starts working.

I am using the latest version with Laravel 10, PHP 8.1+,

Uncaught ReferenceError: currentlyReorderingStatus is not defined
Expression: "currentlyReorderingStatus ? 'laravel-livewire-tables-reorderingMinimised' : ''" ....

lrljoe · 2023-10-23T21:13:36Z

lrljoe
Oct 23, 2023
Collaborator Sponsor

Typically this is one of a couple of things:
If you have previously published the package views, I'd advise removing them. You shouldn't need to publish the views for this package, and it's not advised.

If you are bundling the assets rather than injecting them, then make sure to update your bundle

0 replies

jclee100 · 2023-11-15T07:49:17Z

jclee100
Nov 15, 2023
Author

I don't think I published the views and I am not bundling assets.

I see the scripts injected in head

<head><!-- Rappasoft Core Table Styles -->
    <link href="/rappasoft/laravel-livewire-tables/core.min.css" rel="stylesheet"> <!-- Rappasoft Table Third Party Styles -->
    <link href="/rappasoft/laravel-livewire-tables/thirdparty.css" rel="stylesheet">
        <meta charset="utf-8">
        <meta name="viewport" content="width=device-width, initial-scale=1">
        <meta name="csrf-token" content="7kOYmd7fTxDxROnub2H1TXuwnwXNODvl3jBDb62v">

        <title>Laravel</title>

        <!-- Fonts -->
        <link rel="preconnect" href="https://fonts.bunny.net">
        <link href="https://fonts.bunny.net/css?family=figtree:400,500,600&amp;display=swap" rel="stylesheet">

        <!-- Scripts -->
        <script type="module" src="http://127.0.0.1:5174/@vite/client" data-navigate-track="reload"></script><link rel="stylesheet" href="http://127.0.0.1:5174/resources/css/app.css" data-navigate-track="reload"><script type="module" src="http://127.0.0.1:5174/resources/js/app.js" data-navigate-track="reload"></script>    <!-- Rappasoft Core Table Scripts -->
<script src="/rappasoft/laravel-livewire-tables/core.min.js"></script> <!-- Rappasoft Third Party Scripts -->
<script src="/rappasoft/laravel-livewire-tables/thirdparty.min.js"></script>
<!-- Livewire Styles --><style>[wire\:loading], [wire\:loading\.delay], [wire\:loading\.inline-block], [wire\:loading\.inline], [wire\:loading\.block], [wire\:loading\.flex], [wire\:loading\.table], [wire\:loading\.grid], [wire\:loading\.inline-flex] {display: none;}[wire\:loading\.delay\.none], [wire\:loading\.delay\.shortest], [wire\:loading\.delay\.shorter], [wire\:loading\.delay\.short], [wire\:loading\.delay\.default], [wire\:loading\.delay\.long], [wire\:loading\.delay\.longer], [wire\:loading\.delay\.longest] {display:none;}[wire\:offline] {display: none;}[wire\:dirty]:not(textarea):not(input):not(select) {display: none;}:root {--livewire-progress-bar-color: #2299dd;}[x-cloak] {display: none;}</style><style>/* Make clicks pass-through */

I see currentlyReorderingStatus in the injected core.min.js but the console says ReferenceError: currentlyReorderingStatus is not defined. I am guessing the method is called before it's being initialised/loaded which can explain why it works after performing some manual actions such as filtering.

Still not sure what I am doing wrong.

4 replies

lrljoe Nov 19, 2023
Collaborator Sponsor

Make sure to update to the latest version of the package.

Let me know if this is still throwing any errors for you, as there's a few different fix/approaches for similar issues.

jclee100 Nov 21, 2023
Author

It was v3+ and I have now updated to 3.1.3. Still the same errors.

livewire.js?id=2b77c128:1234 Alpine Expression Error: currentlyReorderingStatus is not defined

Expression: "currentlyReorderingStatus ? 'laravel-livewire-tables-reorderingMinimised' : ''"

lrljoe Nov 27, 2023
Collaborator Sponsor

Check in resources/views/vendor to make sure the table views aren't in there.

If they're not then I'll take another closer look.

If you open the browser straight to the table, or refresh the page with the table, do you still get the error?

jclee100 Dec 2, 2023
Author

Check in resources/views/vendor to make sure the table views aren't in there.

Just checked. I don't have a vendors directory in views.

If you open the browser straight to the table, or refresh the page with the table, do you still get the error?

Yes error still occurs.

ChrisThompsonTLDR · 2023-11-20T22:40:30Z

ChrisThompsonTLDR
Nov 20, 2023

@lrljoe I am also encountering this issue after updating Laravel and a few packages.

I have v3.1.3 of this package installed.

I do not have the package's view files in my application

I have asset caching disabled in my browser

I still receive the error

3 replies

ChrisThompsonTLDR Nov 20, 2023

Digging deeper, I think this is an issue with the bundling of assets, specifically Alpine.

janglapuk Nov 29, 2023

I think the problems are in their public assets changes for current version (v3.1.3). Make sure to check resources directory in this repository.

If you enabling inject_core_assets_enabled and inject_third_party_assets_enabled in config/livewire-tables.php, then:

script_base_path is /rappasoft/laravel-livewire-tables by default, should be /rappasoft/livewire-tables (or /vendor/rappasoft/livewire-tables)

Asset names are core*.css, thirdparty*.css, core*.js, and thirdparty*.js by default, should be laravel-livewire-tables*.css and laravel-livewire-tables*.js. Still don't know how to override this. Need bugfixes in

laravel-livewire-tables/src/Mechanisms/RappasoftFrontendAssets.php

Lines 25 to 57 in c5f0539

    
           public function boot(): void 
        
           { 
        
               // Set the JS route for the core tables JS 
        
               app($this::class)->setRappasoftTableScriptRoute(function ($handle) { 
        
                   $scriptPath = '/rappasoft/laravel-livewire-tables/core.min.js'; 
        
                   return Route::get($scriptPath, $handle); 
        
               }); 
        
               // Set the CSS route for the core tables CSS 
        
               app($this::class)->setRappasoftTableStylesRoute(function ($handle) { 
        
                   $stylesPath = '/rappasoft/laravel-livewire-tables/core.min.css'; 
        
                   return Route::get($stylesPath, $handle); 
        
               }); 
        
               // Set the JS route for the third party JS 
        
               app($this::class)->setRappasoftTableThirdPartyScriptRoute(function ($handle) { 
        
                   $scriptPath = '/rappasoft/laravel-livewire-tables/thirdparty.min.js'; 
        
                   return Route::get($scriptPath, $handle); 
        
               }); 
        
               // Set the CSS route for the third party CSS 
        
               app($this::class)->setRappasoftTableThirdPartyStylesRoute(function ($handle) { 
        
                   $stylesPath = '/rappasoft/laravel-livewire-tables/thirdparty.css'; 
        
                   return Route::get($stylesPath, $handle); 
        
               }); 
        
               static::registerBladeDirectives(); 
        
           }

As a temporary solution, you need to disabling inject_core_assets_enabled and inject_third_party_assets_enabled, and includes the assets manually in your blade.

<link rel="stylesheet" href="{{ asset('vendor/rappasoft/livewire-tables/css/laravel-livewire-tables.min.css') }}">
<link rel="stylesheet" href="{{ asset('vendor/rappasoft/livewire-tables/css/laravel-livewire-tables-thirdparty.min.css') }}">
...
<script src="{{ asset('vendor/rappasoft/livewire-tables/js/laravel-livewire-tables.min.js') }}"></script>
<script src="{{ asset('vendor/rappasoft/livewire-tables/js/laravel-livewire-tables-thirdparty.min.js') }}"></script>

lrljoe Dec 5, 2023
Collaborator Sponsor

Thanks for the detailed description, will get a fix out in the next day hopefully.

StuBlackett2022 · 2024-01-15T10:45:03Z

StuBlackett2022
Jan 15, 2024

Hi @lrljoe any updates on this. We seem to have a clash between livewire and this Vue tables package

0 replies

Uh oh!

Uncaught ReferenceError: currentlyReorderingStatus is not defined #1432

Uh oh!

Uh oh!

jclee100 Oct 20, 2023

Replies: 4 comments · 7 replies

Uh oh!

lrljoe Oct 23, 2023 Collaborator Sponsor

Uh oh!

Uh oh!

jclee100 Nov 15, 2023 Author

Uh oh!

lrljoe Nov 19, 2023 Collaborator Sponsor

Uh oh!

jclee100 Nov 21, 2023 Author

Uh oh!

Uh oh!

lrljoe Nov 27, 2023 Collaborator Sponsor

Uh oh!

jclee100 Dec 2, 2023 Author

Uh oh!

Uh oh!

ChrisThompsonTLDR Nov 20, 2023

Uh oh!

ChrisThompsonTLDR Nov 20, 2023

Uh oh!

janglapuk Nov 29, 2023

Uh oh!

lrljoe Dec 5, 2023 Collaborator Sponsor

Uh oh!

StuBlackett2022 Jan 15, 2024

jclee100
Oct 20, 2023

Replies: 4 comments 7 replies

lrljoe
Oct 23, 2023
Collaborator Sponsor

jclee100
Nov 15, 2023
Author

lrljoe Nov 19, 2023
Collaborator Sponsor

jclee100 Nov 21, 2023
Author

lrljoe Nov 27, 2023
Collaborator Sponsor

jclee100 Dec 2, 2023
Author

ChrisThompsonTLDR
Nov 20, 2023

lrljoe Dec 5, 2023
Collaborator Sponsor

StuBlackett2022
Jan 15, 2024