Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Just wanting to confirm a suspicion: Is there any point having Layers enabled and not Presets if you don't intend on building maps via code (i.e. using only CCK, Views, etc.)?
Comments
Comment #1
zzolo CreditAttribution: zzolo commentedWell, yes and no. Disabling the Preset UI module at any point will help remove some overhead from your site. But, if you are starting new and do not have any coded presets (or intend on making any), then the Layers module will not do much for you without the interface. The only preset that is supplied use layers in the core module.
Though this makes me think that maybe having a preset module might be a good idea. Well, I think the tough part is that the more popular layers need API keys. Anyway.
Comment #2
BWPanda CreditAttribution: BWPanda commentedSo does this mean you can enable Preset UI, create a custom map using Google Maps or whatever, then disable Preset UI and still have access to the custom map?
This might be handy for sites that just want basic maps, but want to use a different default layer (i.e. Google Maps)...
Comment #3
phayes CreditAttribution: phayes commentedYup you can do that! (theoretically) i have yet to try it.
Comment #4
zzolo CreditAttribution: zzolo commentedThe main idea of this is similar to Views UI. It allows you to slim down the code needed for your site to run, thus increasing performance to a certain degree. Closing.