Actions hardcoded

[blondie63]

I've found that Actions button for Crud is hardcoded here:
vendor/backpack/crud/src/resources/views/crud/components/datatable/datatable_logic.blade.php line 1288
Backpack V7.0.6

Beacause i've some override this button is not working on my upgraded app but i'm investigating..

[backpack-ai-bot[bot]]

You’re right that in Backpack 7 the table / actions UI is now driven by the new datatable views, and if you’ve overridden related views from 6.x, that can easily break buttons after upgrade.

From the docs and issues we have, a few important points:

1. List view has been refactored in v7
   In 7.x the List Operation view was split: most datatable logic lives in datatable.blade.php (and related datatable_logic.blade.php), while list.blade.php mostly just includes that component. If you had your own resources/views/vendor/backpack/crud/list.blade.php from 6.x, you now need to move/merge your customizations into the new structure, otherwise core things like the Actions cell can misbehave. [Upgrade views]

2. Check for stale overrides vs new package views
   The upgrade guide explicitly recommends diffing your overridden Backpack views against the new ones in vendor/backpack/crud to catch exactly this type of breakage. For CRUD list / datatable related problems, they suggest:

   anychange resources/views/vendor/backpack/crud vendor/backpack/crud/src/resources/views/crud

   Then inspect differences (especially for list.blade.php, datatable.blade.php, inc/datatables_logic.blade.php, and any overridden button views) and bring your overrides in line with the new structure. [Upgrade views]

3. Buttons are still configurable & overridable

   • Buttons are managed through the Buttons API (CRUD::addButton, removeButton, removeAllButtons, etc.). [7.x buttons]
   • The Actions column visibility is still tied to whether the line stack has buttons. Removing all line buttons (e.g. CRUD::removeAllButtonsFromStack('line') or CRUD::removeAllButtons()) should hide the Actions column. This has been the pattern since earlier versions. [Remove actions; Remove actions 2]
   • Individual operation buttons can still be overridden by putting a blade file with the same name under resources/views/vendor/backpack/crud/buttons. [7.x buttons]

4. If your overrides are from v6, they likely conflict
   Older customizations that directly modified list.blade.php or the table markup can now conflict with the new datatable structure, including the “Actions” logic. The docs specifically warn that if you overrode list.blade.php you must re‑align it with the 7.x version (and move logic into datatable.blade.php where appropriate). [Upgrade views]

5. Related known 7.x button/Actions issues

   • There was a bug where lineButtonsAsDropdown and the Show button didn’t play nicely in 7.x; it was fixed in a later 7.x beta. If you’re on 7.0.6 you may want to update to a newer 7.x release where that PR is included. [Show button bug]
   • There are also recent reports around actions / responsive controls not displaying correctly on some devices – some of that is CSS / markup related in datatables_logic.blade.php. If you’ve overridden that file, it’s even more important to diff it against the package version. [Responsive controls bug]

Given the above and the information we have, the practical steps I’d suggest for your case:

1. Identify all relevant overrides under resources/views/vendor/backpack/crud, especially:

   • list.blade.php
   • components/datatable/*.blade.php
   • inc/datatables_logic.blade.php
   • any custom/overridden button views in buttons/

2. Run anychange / anydiff between your overrides and vendor/backpack/crud/src/resources/views/crud to see what differs, and adjust your overrides to match 7.x structure while keeping your customizations. [Upgrade views]

3. If you just need custom behavior in the Actions column, prefer:

   • using the Buttons API (CRUD::addButtonFromView, removeButton, removeAllButtonsFromStack('line')), and
   • overriding only the specific button blade(s) under resources/views/vendor/backpack/crud/buttons,
     rather than editing the core datatable logic/view, to avoid future breakages. [7.x buttons]

The knowledge sources don’t show the exact snippet at your stated line number in datatable_logic.blade.php, so I can’t comment on that specific line, only on the general pattern and upgrade guidance.

ℹ️ Please note our AI Bot does not reply to follow-ups, this will be the only AI answer in this thread. If the AI helped you find the answer, please mark it as answered or write details below so it can learn. Then close the conversation. If not, please give more information for when a human reads this. ℹ️

Relevant sources:

Github Issue (closed): [Bug] Backpack 7.x show operation button ignores lineButtonsAsDropdown settings
Github Issue (closed): [Bug] Bulk Action Button's alwais disabled
Github Issue (closed): Remove Actions Column
Github Issue (closed): [Feature] Show view
Github Issue (closed): How to add actions under Actions
Github Issue (closed): Hide Action row
Buttons|Creating a Custom Button
Github Issue (closed): [Bug] Separate responsive controls from first column contents not showing
Github Issue (closed): custom button
Buttons|Overriding a Button
Upgrade Guide|Views

[blondie63]

@pxpm I think there is a bug here..

[blondie63]

[pxpm]

Hey @blondie63 thanks for the report.

I've just merged a fix for some line button behavior, but it as not related with what you report here. It was due to open/close events and horizontal positioning. Laravel-Backpack/CRUD#5900

I could not reproduce such "wrong positioning" as you show in the image, so I assume is something related with the upgrade that is still not in sync with the new files.

I am releasing the CRUD version with the fix I mentioned, please pull it with composer update, but I am pretty sure that it will not solve the issue you report here. The issue you seem to be having is most likely missing something in the upgrade process of the views.

If you can find what it is, please let us know so we evaluate if it's something worthwile to add into the upgrade guide 👍

[blondie63]

@pxpm Just tried v7.0.8 and have same two issue:

1. Actions is hardcoded
2. Action menu will open far from button

[pxpm]

Thanks @blondie63

Regarding 1) I've just released a new version that fixes this.

About 2), I think it's something missing on your override, as I am not able to reproduce that.

[blondie63]

@pxpm

1. seen it, ok !
2. i've many overrides that i've fixed yesterday, now i've only this action menu issue, There is a quick way to figure out which of these is interfering with this Action Dropdown Menu?

[pxpm]

It got some changes regarding the positioning of the dropdown as we had known issues in Backpack v6 regarding that.

Specifically here:

https://github.com/Laravel-Backpack/CRUD/blob/05e7f869fb6ca85bcf55f71b8d2eda3dc95aeb1a/src/resources/views/crud/components/datatable/datatable_logic.blade.php#L1297

And around those lines.

[blondie63]

@pxpm i've tried 7.0.10 with same result in one my app, in other no problems!
But how can I find out which override is interfering with this Action Dropdown Menu

UPDATE: i've found that the problem is in config/backpack/theme-tabler.php i'm comparing with original new in v7!
@pxpm The problem is not on theme-tabler.php :(