Following the Views Gallery setup I tried to disable views_gallery (and prerequisite content_copy)
in order to reduce the footprint. That resulted in removing also the required imagecache settings.
Would it be possible to make the imagecache settings permanent, so that views_gallery and
content_copy can be disabled?

Comments

skizzo’s picture

skizzo commented

alternatively... is it ok to disable views_gallery and content_copy after
overriding the default Views Gallery imagecache settings?

karens’s picture

karens commented
Status: Active » Fixed

The imagecache settings are created by default presets, see views_gallery.module, 'views_gallery_imagecache_default_presets'. You would have to copy that code into a custom module so the presets still exist after this module is disabled or created your own presets and change the content types and views to use your presets.

That is as much as I can do, I can't alter the way that the default presets work, disabling the module will remove the default presets.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

hanoii’s picture

hanoii
Primary language Spanish
Location 🇦🇷UTC-3
commented
Title: Disabling views_gallery and content_copy after setup » Disabling modules after setup
Version: 6.x-1.2 » 6.x-2.0-beta2
Status: Closed (fixed) » Active

First of all, niced glued together stuff, I have to say I really considered going step by step following the video, I'd like to have control and understanding on what I do with a site, specially being the new one, but then again, why re-inventing the wheel?

Anyway, I also wondered about disabling modules once I installed this one, and this is the most related issue.

I guess disabling views gallery is out of the question because of the imagecache presets on 2.x as well, but what about the other modules?

features, ctools, strongarm, are those needed once everything is setup?

It might be an useful thing to list the modules that might be disabled once everything is setup on the project's page in order to keep the used modules enabled on the site.

Thanks

karens’s picture

karens commented

There is an issue somewhere on the Features site about providing a way to 'release' components from Features once they are set up, but at the moment that won't work. So if you disable Features you will lose the content types it created. That is a Features issue, nothing I can do about it, but basically if you create a feature you need to keep Features enabled. Someone would have to test whether CTools or Strongarm can safely be disabled later. I need them anyway so have not tried it.