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

[Bug] Test issue #5685

Closed
jcastroa87 opened this issue Oct 8, 2024 · 18 comments
Closed

[Bug] Test issue #5685

jcastroa87 opened this issue Oct 8, 2024 · 18 comments

Comments

@jcastroa87
Copy link
Member

Bug report

What I did

??

What I expected to happen

??

What happened

??

What I've already tried to fix it

??

Is it a bug in the latest version of Backpack?

After I run composer update backpack/crud the bug... is it still there?

Backpack, Laravel, PHP, DB version

When I run php artisan backpack:version the output is:

Copy link

asdf

1 similar comment
Copy link

asdf

Copy link

This issue has been reported and resolved in the past. The problem was that when opening and closing the date filter, sometimes a datepicker window would appear in the top corner of the screen instead of closing. The bug was reproduced both logically and on the demo site.

The fix for this issue has been merged into the Backpack/Pro package. You can get the updated version by running a composer update. The version that contains the fix is 2.2.9.

You can find more details about this issue and its resolution on the Github issue page.

Copy link

This issue has been reported and resolved in the past. The problem was that when opening and closing the date filter, sometimes a datepicker window would appear in the top corner of the screen instead of closing. The bug was reproduced both logically and on the demo site.

The fix for this issue has been merged into the Backpack/Pro version. You can get the updated version by running a composer update. The version with the fix is 2.2.9.

You can find more details about this issue and its resolution on the Github issue page.

Copy link

This issue was reported on the Github page of Laravel-Backpack/CRUD. The problem was that when opening and closing the date filter, sometimes a datapicker window appears in the top corner of the screen instead of closing.

The issue has been addressed and fixed. You can get the updated version by running a composer update. The fix was merged in the version 2.2.9 of backpack/pro.

If you still encounter the issue, please make sure you have the latest version of Backpack. If the problem persists, consider opening a new issue on the Github page.\n\n Relevant sources: \n\n**Github Issue (closed): [Bug] Frontend issue in the filter**
Fix conflict bootstrap-datepicker & jquery-ui
Github Issue (closed): [Bug] select2 filter disappears upon clicking
Github Issue (closed): [Bug] Datepicker invalid dates on mac os Safari browser
Test & fix all filters
Discovered a bug?|Discovered a bug?
PRO for unlimited projects|2.0.4 03-Jul-2023
Github Issue (closed): datepicker - create:5688 Uncaught TypeError: Cannot read property 'length' of undefined
Github Issue (closed): There are problems with button the remove filters and type date_range
Github Issue (closed): [BUG] datepicker field gives js error $(...).datepicker not defined

Copy link

This issue was reported on the Github page of Laravel-Backpack/CRUD. The problem was that when opening and closing the date filter, sometimes a datepicker window would appear in the top corner of the screen instead of closing. This bug was reproduced both logically and on the demo site.

The issue has been addressed and fixed by the contributors. The fix was merged into the backpack/pro version. You can get the updated version by running a composer update. The updated version with the fix is 2.2.9.

For more details, you can refer to the Github issue.

Relevant sources:

Github Issue (closed): [Bug] Frontend issue in the filter
Github Issue (closed): [Bug] select2 filter disappears upon clicking
Github Issue (closed): [Bug] Datepicker invalid dates on mac os Safari browser
PRO for unlimited projects|2.0.4 03-Jul-2023
Github Issue (closed): datepicker - create:5688 Uncaught TypeError: Cannot read property 'length' of undefined
Github Issue (closed): There are problems with button the remove filters and type date_range
Github Issue (closed): [BUG] datepicker field gives js error $(...).datepicker not defined
Github Issue (closed): clear filter button will make date_range filter drop endless loop
Github Issue (closed): There are problems with button the remove filters and type date_range
Github Issue (closed): [Bug] Remove filter button does not hide when select2 filters are cleared.

Copy link

This issue was reported on the Github page of Laravel-Backpack/CRUD. The problem was that when opening and closing the date filter, sometimes a datepicker window would appear in the top corner of the screen instead of closing. This bug was reproduced both logically and on the demo site.

The issue was addressed by a contributor who merged a fix in backpack/pro. Updating to the latest version (2.2.9 at the time of the fix) with a composer update command should resolve the issue.

For more details, you can refer to the Github issue.

Relevant sources:

Github Issue (closed): [Bug] Frontend issue in the filter
Github Issue (closed): [Bug] select2 filter disappears upon clicking
Github Issue (closed): [Bug] Datepicker invalid dates on mac os Safari browser
Github Issue (closed): There are problems with button the remove filters and type date_range
Github Issue (closed): clear filter button will make date_range filter drop endless loop
Github Issue (closed): There are problems with button the remove filters and type date_range
Github Issue (closed): [Bug] Remove filter button does not hide when select2 filters are cleared.
Github Issue (closed): [Bug] First Filter Appears and Won't Go Away When Selecting Any Other Filter
Github Issue (closed): Initial value of date picker can be a day off
Github Issue (closed): [BUG] datepicker field gives js error $(...).datepicker not defined

@pxpm pxpm added the v7 label Oct 21, 2024
Copy link

This issue was reported on the Github page of Laravel-Backpack/CRUD. The problem was that when opening and closing the date filter, sometimes a datapicker window appears in the top corner of the screen instead of closing. This bug was reproduced both logically and on the demo site.

The issue was addressed by a contributor who merged a fix in backpack/pro. Updating to the latest version (2.2.9 at the time of the fix) with a composer update command should resolve the issue.

For more details, you can refer to the Github issue.

Relevant sources:

Github Issue (closed): [Bug] Frontend issue in the filter
Github Issue (closed): [Bug] select2 filter disappears upon clicking
Github Issue (closed): [Bug] Datepicker invalid dates on mac os Safari browser
Github Issue (closed): There are problems with button the remove filters and type date_range
Github Issue (closed): clear filter button will make date_range filter drop endless loop
Github Issue (closed): There are problems with button the remove filters and type date_range
Github Issue (closed): [Bug] Remove filter button does not hide when select2 filters are cleared.
Github Issue (closed): [Bug] First Filter Appears and Won't Go Away When Selecting Any Other Filter
Github Issue (closed): Initial value of date picker can be a day off
Github Issue (closed): [BUG] datepicker field gives js error $(...).datepicker not defined

Copy link

Copy link

This issue has been reported and addressed in Backpack. According to the knowledge sources, the bug you're describing with the date filter has been fixed in a recent update.

The issue you reported was acknowledged by the Backpack team. A contributor mentioned that the fix has been merged into backpack/pro version 2.2.9.

To resolve this issue, you should update your Backpack installation. You can do this by running:

composer update

This should update Backpack to the latest version that includes the fix for the date filter bug.

If you're still experiencing the issue after updating, please make sure you're using the latest version of Backpack and consider reporting it again on the GitHub issues page.

Relevant sources:

Github Issue (closed): [Bug] Frontend issue in the filter
Github Issue (closed): [Bug] select2 filter disappears upon clicking
Github Issue (closed): [Bug] Datepicker invalid dates on mac os Safari browser
Github Issue (closed): There are problems with button the remove filters and type date_range
Github Issue (closed): clear filter button will make date_range filter drop endless loop
Github Issue (closed): There are problems with button the remove filters and type date_range
Github Issue (closed): [Bug] Remove filter button does not hide when select2 filters are cleared.
Github Issue (closed): [Bug] First Filter Appears and Won't Go Away When Selecting Any Other Filter
Github Issue (closed): Initial value of date picker can be a day off
Github Issue (closed): [BUG] datepicker field gives js error $(...).datepicker not defined

Copy link

This issue you're describing appears to be a known bug in Backpack that has been reported and addressed. Based on the information provided in the knowledge sources, here's what we know:

  1. The bug you're experiencing with the date filter has been reported and confirmed. It occurs when dismissing the calendar twice via the close (X) button for both date and date_range filters Github Issue 5354.

  2. A fix for this issue has been merged into the Backpack Pro version. According to a contributor's comment, the fix is available in version 2.2.9 Github Issue 5354.

  3. To resolve this issue, you should update your Backpack installation. You can do this by running composer update to get the updated version with the fix.

It's worth noting that date picker issues have been reported and fixed in the past for Backpack. For instance, there was a fix for date picker keys in version 2.0.4 of Backpack Pro PRO for unlimited projects Changelog.

If you're still experiencing this issue after updating to the latest version, it would be advisable to report it on the Backpack GitHub repository, as it might be a new or persisting bug.

Relevant sources:

Github Issue (closed): [Bug] Frontend issue in the filter
Fix conflict bootstrap-datepicker & jquery-ui
Github Issue (closed): [Bug] select2 filter disappears upon clicking
Github Issue (closed): [Bug] Datepicker invalid dates on mac os Safari browser
PRO for unlimited projects|2.0.4 03-Jul-2023
Github Issue (closed): datepicker - create:5688 Uncaught TypeError: Cannot read property 'length' of undefined
Github Issue (closed): There are problems with button the remove filters and type date_range
Github Issue (closed): [BUG] datepicker field gives js error $(...).datepicker not defined
Github Issue (closed): clear filter button will make date_range filter drop endless loop
Github Issue (closed): There are problems with button the remove filters and type date_range

@pxpm pxpm closed this as completed Oct 30, 2024
@jcastroa87 jcastroa87 reopened this Nov 8, 2024
Copy link

I apologize, but I am specifically designed to answer questions about Backpack, which is a toolkit for building admin panels and back-office applications using the Laravel framework. Your question about why the sky is blue in code doesn't appear to be related to Backpack. If you have any questions about Backpack's features, usage, or configuration, I'd be happy to assist you with those.

Relevant sources:

Make routes and sidebar links blue
added blue bundle as alternative to electric purple default
Github Issue (closed): Ability to easily change primary secondary colors everywhere (opting out of electric purple color theme)
Github Issue (closed): Install & test Backpack v6 - report all bugs and quirks we find
Github Issue (closed): Ability to easily change primary secondary colors everywhere (opting out of electric purple color theme)
Github Issue (closed): Ability to easily change primary secondary colors everywhere (opting out of electric purple color theme)
Github Issue (closed): Ability to easily change primary secondary colors everywhere (opting out of electric purple color theme)
Github Issue (open): Switch to using accessible colours - a darker purple [Feature Request]
Tab
DevTools|ERROR: Illuminate\Database\QueryException could not find driver
Global styles and scripts
Github Issue (closed): [Bug] Unable to produce the same look with CoreUI following instructions from docs
Having trouble using Backpack?|Having trouble using Backpack?
remove double closing tags in inline create button
Themes

Copy link

Bot is not sure about this answer. Please verify.

I apologize, but I don't have enough context to provide a complete answer based solely on the partial message you've shared. The email snippet "CrudPanel.php - 492 CrudPanel.php - 492" doesn't provide enough information about the specific issue or question related to Backpack.

If you have more details from the email about a specific problem or question regarding Backpack's CrudPanel, please share it. That way, I can try to provide a more helpful and accurate response based on the available knowledge sources.

Relevant sources:

Github Issue (closed): Editing, creating and showing enteties in pop-up
Github Issue (closed): Problems with ckeditor and elfinder
Github Issue (closed): Couldn’t work out with the DevTool
Github Issue (closed): devtools buttons not working
Introduction|Introduction Part 1
Github Issue (closed): Develop Tests
Added a CRUD Facade
Introduction|Introduction Part 1
Fix docblock in CrudController
Github Issue (closed): [Bug]
Github Issue (closed): [V6][Bug] Getting error "No hint path defined for [backpack]."
Github Issue (closed): [4.0][Proposal] Maybe move CrudPanel configuration to its own object?
Basics|Basics
[4.1] Clean up Request usage inside CrudController and CrudPanel
Github Issue (closed): [Bug] Tabs feature launches dozens of duplicate queries

Copy link

Currently, Backpack does not have a built-in feature to directly sum column values and display them in the header or footer of a table in the list operation. However, there are a few workarounds and community-contributed solutions that you can consider:

  1. Custom Widget: You can create a custom widget to display the sum of a particular column. This approach is recommended by the Backpack team for displaying totals or summaries Community Forum Discussion.

  2. Custom JavaScript: A community member shared a code snippet that you can add to your custom list.blade.php file to display a total in a div that you can position as needed CRUD Issue #1441.

  3. DataTables Sum Plugin: Since Backpack uses DataTables, you can create a custom list.blade.php file and implement the DataTables sum plugin CRUD Issue #1441.

  4. Model Accessor: You can use a Laravel accessor in your model to calculate the total, and then add it as a column in your CRUD controller CRUD Issue #316.

  5. Custom Controller Method: You can overwrite the index function in your controller to calculate the total value and pass it to the view CRUD Issue #316.

For a more detailed implementation, you might want to check out the code snippet shared by a community member, which you can find in this gist: Backpack Column Sum Gist.

Remember that these are community-contributed solutions and may require some customization to fit your specific needs. The Backpack team has discussed this feature request, but it's not currently part of the core functionality Community Forum Discussion.

Relevant sources:

Sum specific table column
Github Issue (closed): [Feature Request] Ability to change the column title based on the results
Github Issue (closed): [Improvement] Getting sum of particular columns
Github Issue (closed): [Improvement] Getting sum of particular columns
Github Issue (closed): (Question) Output extra value to view or add own method and view in crud controller
Github Issue (closed): (Question) Output extra value to view or add own method and view in crud controller
Github Issue (closed): (Question) Output extra value to view or add own method and view in crud controller
Github Issue (closed): [Enhancement] ListOperation calculates total without local scopes
Laravel-backpack show total of column
Github Issue (closed): [Enhancement] ListOperation calculates total without local scopes
Github Issue (closed): [Enhancement] ListOperation calculates total without local scopes
Github Issue (closed): Error in counting the number of records when grouping by fields in AjaxTable
Github Issue (closed): [Enhancement] ListOperation calculates total without local scopes
Github Issue (closed): Error in counting the number of records when grouping by fields in AjaxTable
Github Issue (closed): [Bug] Need to override List Behaviour "order by" , "Limit XX"

Copy link

Currently, Backpack does not have a built-in feature to directly sum column values and display them in the header or footer of a table in the list operation. However, there are a few workarounds and community-contributed solutions that you can consider:

  1. Custom Widget: You can create a custom widget to display the sum of a particular column. This approach is recommended by the Backpack team for displaying totals or summaries Community Forum Discussion.

  2. Custom JavaScript: A community member shared a code snippet that you can add to calculate and display the sum of a column. You can implement this by adding it as a general script or as a widget directly on the operation Community Forum Discussion.

  3. DataTables Sum Plugin: Since Backpack uses DataTables, you can create a custom list.blade.php file and add the DataTables sum plugin to calculate totals Github Issue Comment.

  4. Custom Method: You can overwrite the index function in your CrudController to calculate the total value and pass it to the view Github Issue Comment.

Here's an example of how you might implement the custom method approach:

protected function recordsTotal() {
    $count = $this->crud->model->where(`your_condition_here`)->count();
    return $count;
}

Then in your list.blade.php file:

@if(isset($entries->total))
    Total - {{$entries->total}}
@endif

Keep in mind that these are workarounds and not official features. The Backpack team has discussed this feature request, and it might be considered for future implementations if there's enough demand from the community Github Issue.

Relevant sources:

Sum specific table column
Github Issue (closed): [Feature Request] Ability to change the column title based on the results
Github Issue (closed): [Improvement] Getting sum of particular columns
Github Issue (closed): (Question) Output extra value to view or add own method and view in crud controller
Github Issue (closed): [Enhancement] ListOperation calculates total without local scopes
Laravel-backpack show total of column
Github Issue (closed): Error in counting the number of records when grouping by fields in AjaxTable
Github Issue (closed): [Bug] Need to override List Behaviour "order by" , "Limit XX"

Copy link

🚨_Bot is not sure about this answer. Please verify._🚨

I apologize, but I don't have enough context to provide a complete answer based solely on the partial message you've shared. The email snippet "CrudPanel.php - 492 CrudPanel.php - 492" doesn't provide enough information about the specific issue or question related to Backpack.

If you have more details from the email about a specific problem or question regarding Backpack's CrudPanel, please share it. I'd be happy to help if you can provide more context about what the user is asking or experiencing with Backpack.

Relevant sources:

Github Issue (closed): Editing, creating and showing enteties in pop-up
Github Issue (closed): Problems with ckeditor and elfinder
Github Issue (closed): Couldn’t work out with the DevTool
Github Issue (closed): devtools buttons not working
Github Issue (closed): Develop Tests
Introduction|Introduction Part 1
Added a CRUD Facade
Introduction|Introduction Part 1
Fix docblock in CrudController
Github Issue (closed): [Bug]
Github Issue (closed): [V6][Bug] Getting error "No hint path defined for [backpack]."
Github Issue (closed): [Bug] crudpanel error while Generating crud with Backpack for Laravel
Github Issue (closed): [4.0][Proposal] Maybe move CrudPanel configuration to its own object?
Basics|Basics
Github Issue (closed): [Bug] Tabs feature launches dozens of duplicate queries

Copy link

🚨 Bot is not sure about this answer. Please verify. 🚨

I apologize, but I don't have enough context to provide a complete answer based solely on the partial message you've shared. The email snippet "CrudPanel.php - 492 CrudPanel.php - 492" doesn't provide enough information about the specific issue or question related to Backpack.

If you have more details from the email about a specific problem or question regarding Backpack's CrudPanel, please share it. I'd be happy to help if you can provide more context about what the user is asking or experiencing with Backpack.

Relevant sources:

Github Issue (closed): Editing, creating and showing enteties in pop-up
Github Issue (closed): Problems with ckeditor and elfinder
Github Issue (closed): Couldn’t work out with the DevTool
Github Issue (closed): devtools buttons not working
Github Issue (closed): Develop Tests
Introduction|Introduction Part 1
Added a CRUD Facade
Introduction|Introduction Part 1
Fix docblock in CrudController
Github Issue (closed): [Bug]
Github Issue (closed): [V6][Bug] Getting error "No hint path defined for [backpack]."
Github Issue (closed): [Bug] crudpanel error while Generating crud with Backpack for Laravel
Github Issue (closed): [4.0][Proposal] Maybe move CrudPanel configuration to its own object?
Basics|Basics
Github Issue (closed): [Bug] Tabs feature launches dozens of duplicate queries

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants