[Bug]: icon image path error

[mhgtlc]

Error: Uncaught ReferenceError: L is not defined

file: public/js/pimcore/startup.js:962

L.Icon.Default.imagePath = '../bundles/pimcoreadmin/build/admin/images/';

[aryaantony92]

Unable to reproduce the error. It's working now

[mhgtlc]

@aryaantony92

Unable to reproduce the error. It's working now

The error is still there:

https://github.com/pimcore/admin-ui-classic-bundle/blob/1.x/public/js/pimcore/startup.js#L962C1-L962C3
Where does this L come from?

[aryaantony92]

@mhgtlc Could you please try again with the latest version ?

[dvesh3]

@aryaantony92 @mhgtlc L. is a leaflet object (used mainly for Geo datatypes). I'm wondering why this is not part of admin bundle? 🤔

[aryaantony92]

admin-ui-classic-bundle/public/js/pimcore/startup.js

Line 962 in 8846027

L.Icon.Default.imagePath = '../bundles/pimcoreadmin/build/admin/images/';

This is in the admin bundle.

[storbahn]

I still have this error L.Icon.Default.imagePath = '../bundles/pimcoreadmin/build/admin/images/'; (js error in browser console)

We use the pimcore version 11.1.5 and the admin bundle with version 1.3.4

[aarongerig]

Same here. I get a L is not defined error in the console, when loading the Pimcore Backend.

@dvesh3 This issue should be re-opened as it doesn't seem to be fixed, right?

[aarongerig]

@dvesh3 WDYT? 🙂

[sevarozh]

I can also confirm it with:

• pimcore/pimcore 11.1.4
• pimcore/admin-ui-classic-bundle 1.3.1

It looks like the "Leaflet" library is loaded later than L.Icon.Default.imagePath is called in startup.js.
After loading of admin, L is defined in console:

Issue is closed, but I can't find a commit with a bug fix @aryaantony92

[mhgtlc]

@brusch @dvesh3 @aryaantony92
Issue is still there:

• pimcore/pimcore 11.2.2
• pimcore/admin-ui-classic-bundle 1.4.0

And indeed, behaviour is the same as @sevarozh described above (It looks like the "Leaflet" library is loaded later than L.Icon.Default.imagePath is called in startup.js)

[fashxp]

can you share more detailed steps to reproduce?
can it be reproduced on our demo?

[robertSt7]

@mhgtlc @sevarozh @aarongerig @storbahn Could you please test if this patch fix the problem? TIA
#697

[aarongerig]

@robertSt7 This indeed resolves the issue on my side. 👍🏻