October: Add a list of optionally supported plugins in theme.yaml

[lautsevich]

Hi.

By developing themes for October CMS websites you must list required plugins in the theme.yaml file. But themes can support some other plugins as an available option. So it can be very useful to add to the theme.yaml file a new block with the list of optional dependencies, e.g.:

name: Awesome theme
description: 'My super-duper theme for October CMS'
author: Lovata
homepage: ''
code: 'awesome-theme'
require:
    - Lovata.Toolbox
    - Lovata.Shopaholic
optional:
    - Lovata.ReviewsShopaholic

And the optional plugins will show on the theme page in the marketplace like the required plugins.

It would be much useful to list optional plugins near the required instead of listing them in the description.

We at LOVATA just started to develop themes for our Shopaholic. And we plan to add a huge amount of themes to the marketplace in the near future. Each theme will support a lot of required and optional plugins. And we prefer to tell in the theme description more about the functionality and benefits of using it instead of stealing the place for listing the optional plugins.

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 30 days. If this issue is still relevant or you would like to see action on it, please respond and we will get the ball rolling.

[lautsevich]

@bennothommo, @LukeTowers, @daftspunk, any updates on this issue?

[bennothommo]

@lautsevich I like the idea very much, but it's something that will need to be primarily developed in the marketplace. It will need to be reviewed by @daftspunk and @alekseybobkov.

[lautsevich]

@bennothommo, got it! Thx for the quick reply. IMO, in this case, it would be better to untag this issue with "Status: Archived". Thx!

[bennothommo]

@lautsevich I'll untag it and give it another 30 days.

[lautsevich]

Thx! I'll post reminders here in comments every 30 days. =)

[36864]

While we're at it, this feature could also make sense for plugins, not just themes.

For example, one of my plugins could use either RainLab\User or Lovata\Buddies, or a custom authentication plugin that conforms to some pre-requisites.

Currently this is difficult to express in a plugin's page.

Also, as an extension, it could be useful to have a "require_one" directive, maybe something like

require_one:
  - Lovata.Buddies, RainLab.User

That might be a bit more difficult to implement / express to users though.

[lautsevich]

@36864, you're right!

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 30 days. If this issue is still relevant or you would like to see action on it, please respond and we will get the ball rolling.

[lautsevich]

@bennothommo, unarchive this issue, please! =) We should continue discussing this issue. @daftspunk, @alekseybobkov, have you checked this issue and last comment by @36864?

[bennothommo]

Done @lautsevich :)

[lautsevich]

Thx!

[daftspunk]

This is an interesting idea except that Themes cannot really depend on optional plugins without Soft Component Support. This would allow for optional pages to exist and also fail gracefully with a page to say "Please install X plugin". At the moment it would cause the website to crash since the plugin is not present in the system.

I would consider this feature blocked by #4539 for the time being.

[lautsevich]

@daftspunk, you're right! We check the installation of optional plugins and render theme UI following that information.

In general, the possibility to show additional plugins used by a theme on its page is about cross-selling and increasing of LTV.

So is there a chance to implement it?

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 30 days. If this issue is still relevant or you would like to see action on it, please respond and we will get the ball rolling.

[lautsevich]

@bennothommo, thx! =)

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 30 days.

• If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue. - If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[lautsevich]

Up 😎

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 30 days.

• If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue. - If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[mjauvin]

ping

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 30 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 30 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

[github-actions[bot]]

This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.