Actions problems

[threecolors-lab]

I have tried all the action button position options but the result is still the same as this. In addition, the map view is not complete. Is there a solution?

[dmandrade]

Sorry for the delay in responding.

This issue seems to be some kind of css issue, perhaps a custom theme you were using?

Let me know if you still have this issue with v3 or have found a solution.

[parelio]

I have the same problem and no custom css. Fresh Filament 3 install with v 3.0.0 of the plugin.

[dmandrade]

We've released version 3.0.1, which includes several layout adjustments. Please test this latest version and let me know if the issue persists. If everything looks good, I'll go ahead and close this issue.

[parelio]

Sorry, not, v 3.0.1 does not fix the problem for me.

Right after loading the page:

After panning the map, the control buttons disappear completely:

[parelio]

By the way, I noticed that the copyright notice is not visible right after loading, but after panning the map it ist visible.

[Mathissou01]

I'm not sure if this will help, but I managed to fix a similar issue in my project by doing a few different things.

The problem started after I installed another plugin, Commentions (used for commenting resources). After that, the maps started acting weird: the action buttons were no longer positioned correctly, and the markers on the map stopped appearing.

I tried fresh installations on different computers and servers, but the issue persisted.

Eventually, I decided to clean up unused plugins. I removed the following packages:

"intervention/image": "^3.11",
"kirschbaum-development/commentions": "^0.6.2",
"lara-zeus/popover": "^1.1",
"barryvdh/laravel-dompdf": "*"

After running composer update, everything started working again: the action buttons were correctly placed, and all the markers reappeared.

Additionally, I upgraded from:

"webbingbrasil/filament-maps": "3.0.0"

to:

"webbingbrasil/filament-maps": "3.0.1"

After that, everything functioned as expected.

I'm still not entirely sure why this fixed the issue, but if you're experiencing something similar, this might help.
Also, don't forget to run:

composer dump-autoload
php artisan optimize:clear

after making those changes.

[dmandrade]

Thanks a lot, @Mathissou01. Your detailed explanation was super helpful! 🙌

@parelio just curious: are you using any of the packages @Mathissou01 mentioned, like commentions or lara-zeus/popover? Wondering if there’s a pattern here.

[parelio]

Thanks a lot, @Mathissou01. Your detailed explanation was super helpful! 🙌

@parelio just curious: are you using any of the packages @Mathissou01 mentioned, like commentions or lara-zeus/popover? Wondering if there’s a pattern here.

Hi @dmandrade, thanks for your curiosity.
I had none of the above mentioned packages involved, but

"dotswan/filament-map-picker": "^1.8",

activated. After removing this package, the buttons are well positioned! Could be some z-index issue?

[hazbu]

Thanks a lot, @Mathissou01. Your detailed explanation was super helpful! 🙌
@parelio just curious: are you using any of the packages @Mathissou01 mentioned, like commentions or lara-zeus/popover? Wondering if there’s a pattern here.

Hi @dmandrade, thanks for your curiosity. I had none of the above mentioned packages involved, but

"dotswan/filament-map-picker": "^1.8",

activated. After removing this package, the buttons are well positioned! Could be some z-index issue?

Same here

[mstfkhazaal]

@threecolors-lab
@hazbu
@Mathissou01
@parelio

You can publish the view
php artisan vendor:publish --tag=filament-maps-views
and in the components/map.blade.php add this absolute z-10 p-2 space-y-2

  {{ $attributes->class([
                        'absolute z-10 p-2 space-y-2 filament-map-actions',
                    ]) }}

filament-maps/resources/views/components/map.blade.php

Line 453 in 4e53b54

'filament-map-actions',

Or check this Pull Request
#36

[dmandrade]

Hi everyone 👋

Thanks again for all the insights and contributions to this thread!

We've just released version 3.0.2, which includes the solution suggested by @mstfkhazaal — could you check if it resolves the issue on your end?