Our powerful JS Calendar component

Post by cooper »

Project uses Calendar 5.4.1 for one page as well as a declaration for a splitter and a panel:

   (blah blah snip)>

(blah blah snip)>


Have now also added scheduler 5.5.2 on a different page. Since doing so, the calendar page does not function and console shows error:

Multiple components match node with tagname bryntum-splitter: BryntumSplitterComponent and BryntumSplitterComponent.

If I remove the splitter declaration and leave the panel it is:

Multiple components match node with tagname bryntum-panel: BryntumPanelComponent and BryntumPanelComponent.

If I remove both splitter and panel declarations, all is well and both the calendar and scheduler work fine on their respective pages.

I've seen a few posts with similar issue. One where someone is using scheduler and Gannt but on the same page. I need to remove or uninstall one of these packages to eliminate redundant declarations? Something like that?

    "@bryntum/calendar": "^5.4.1",
    "@bryntum/calendar-angular": "^5.4.1",
    "@bryntum/scheduler": "^5.5.2",
    "@bryntum/scheduler-angular": "^5.5.2",

Post by marcio »

Hey cooper,

Perhaps this ticket is what you're looking for https://github.com/bryntum/support/issues/4670 as we currently don't support multiple products in the versions that you're using.

If you need more clarification, please share a sample project with your configuration for us to assist you.

You can have more information by checking our guidelines https://www.bryntum.com/forum/viewtopic.php?f=1&t=772

Best regards,

Post by cooper »

This is from just having a splitter? Or a panel? Weird. They don't fail when it's just the calendar and just the scheduler.

I had no idea that I wouldn't be able to use two different products, both of which cost good money, as standalone entities in the same application. Did I miss the pre-sales documentation that calls this out? I don't recall seeing anything, but I certainly could have overlooked such a warning.

I guess now I will have to go through the process and hope those alpha thin versions both work correctly and won't cause any of the customization I've implemented in either one to break, or I could take the certain to work option, would be to move either calendar or grid to its own project and deploy it somewhere else, and then revisit this issue when the thin versions are out of testing? I dunno. This is not great news.

Post by alex.l »

Hi cooper,

We are sorry about that, we released beta today and stable version is planned to be released shortly, hopefully in a week or so. I believe you could start to play with thin versions now and we will be there with 5.6.0 asap.

All the best,

Post Reply