Customized installation refinement

Created on 8 October 2024, 2 months ago

Problem/Motivation

Manage customized installation when not using vlsuite_shuttle so any media, block or node entity usage is customized & not required default vlsuite ones of shuttle preset.

Steps to reproduce

Enable vlsuite manually instead by vlsuite_shuttle preset. For example:
vlsuite, vlsuite_block, vlsuite_layout, vlsuite_layout_builder, vlsuite_utility_classes, vlsuite_icon_font, vlsuite_media, vlsuite_slider, vlsuite_animations but without any vlsuite_collection nor vlsuite_block or vlsuite_media inner blocks (vlsuite_collection_hero, vlsuite_block_image or vlsuite_media_image).

Proposed resolution

Refine modules or config dependencies in order to preserve current shuttle working the same but allow described installation too.

Feature request
Status

Active

Version

2.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @CRZDEV
  • Adjusted vlsuite_layout dependencies without:
    - vlsuite:vlsuite_media_image
    - vlsuite:vlsuite_media_local_video

    To check:
    - Install vlsuite_shuttle: exact same behavior
    - Customized installation: any vlsuite "basis" module is enabled but without of collection, block or media that generates vlsuite entities (like vlsuite_collection_hero, vlsuite_block_image or vlsuite_media_image).

  • Just to clarify; vlsuite basis may be:
    - vlsuite (main module)*
    - vlsuite_media (main media integration)*
    - vlsuite_block (main block integration)*
    - vlsuite_layout (main layout integration)*
    - vlsuite_layout_builder (main layout builder integration)*
    - vlsuite_utility_classes (main appearance modificators integration)*
    - vlsuite_icon_font (main UI & other uses as field into any entity icon font integration)*
    *Including its dependencies.

  • Maybe this dependencies should not be added by main vlsuite composer file if those modules last too long to achieve core 11 compatibility (when using shuttle installation will request you to install them):
    - layout_builder_at
    - media_responsive_thumbnail

    Related:
    https://www.drupal.org/project/vlsuite/issues/3435575 📌 Automated Drupal 11 compatibility fixes for vlsuite Needs work

  • Maybe vlsuite_shuttle should enable full "basis but complete" integration & new vlsuite_demo should take that "role" for a complete "demo" experience. Of course with customized installation you are responsible to make all entities like "landing" node (existing or not), content blocks & medias & all others configurations needed to have similar experience of enabling shuttle but with complete customization.

  • Done both changes in MR:

    Move composer dependencies optional with customizable installation to suggest:
    - layout_builder_at: Required for VLSuite demo & suggested to resolve layout builder asymmetric translations strategy.
    - media_responsive_thumbnail: Required for VLSuite demo & suggested to skip media entity view layer when using that formatter in a referencing entity.

    New vlsuite demo & shuttle definition:
    - Visual Layout Suite (VLSuite) - Demo. Install this module to automatically setup the VLSuite ready to use.
    - Visual Layout Suite (VLSuite) - Shuttle. Install this module to automatically setup the VLSuite basis for a customized installation with complete integration but without node, block or media entities.

  • Adjusted dependencies to new paradigm

  • Uploading static patch of MR 53 changes to avoid commit iterations with MR gitlab patch or diff

  • Merge request !54Issue #3479416: Unique commit → (Closed) created by CRZDEV
  • 🇪🇸Spain tunic Madrid

    Tests the VLS Demo, it installs ok and seems to work. Good split.

    Moving to RBTC.

  • Pipeline finished with Skipped
    2 months ago
    #304318
  • Great, thanks! Integrating MR changes to 2.x

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

Production build 0.71.5 2024