System - Helix Ultimate Framework Version 2.0.6 Causes issues with non-Helix pages

I cannot reproduce the error on your admin site since the problem only presents on th frontpage of my LMS component running from the component position of Helix Ultimate.

I cannot install a uniquely site-licensed LMS to your test site.

The link posted by bouey agrees with the advice set out by the LMS developer, that the solution requires re-sequencing code in the plugin helixultimate.php. From reading Stéphane's link, it seems this is a problem that had once been fixed, but then came back with 2.07. Perhaps this is an issue Joomshaper neeeds to fix again, and release 2.08?

Please read Stéphane's link and advise.

Per my previous comment, I would have to mirror install our LMS system and configured courses to reproduce the conflicts with the LMS component. The LMS is site-licensed and will not function on your domain. This prohibits staging at your domain.

Likewise, I would need to install and mirror our Virtuamart store, categories, and products to reproduce the VM conflicts - which is unfeasible.

I have set up a mirror staging site on our server instead. See details in the hidden dontent of this post.

Regards,

Allen

This will fix the problem of this thread too

https://www.joomshaper.com/forum/question/6957

with the menu not translated.

Hi @bouey,

I read the post you recommended, but there is quite a lot of discussion with several different "fixes" discussed. Could you clarify exactly what you recommend I do to resolve my issues with menu and template conflicts coming from Helix 2.x? Helix 2.x template and/or menu is applying Bootstrap 5 to VirtueMart and my LMS front page, and its messing everything up there since neither is Bootstrap 5 compatible. Even if the HU menu is applied to a page not running HU, the problem exists.

My LMS developer recommended

It is necessary to move the following part:

$this->registerBootstrap();

from the onAfterInitialise trigger into the onAfterDispatch trigger.

Hope this helps.

But I don't know what this means. It seems to relate to the discussion at your post, but I am not competent enough in PHP to understand how. Can you clarify?

Regards,

Allen

Bump. Hello?

Thanks Toufiq.

Is there any way I can track progress? I've learned that issues sometimes "fall through the cracks." This is somthing I've been trying to get resolved since 2.0 first released last year.

Hi Toufique,

Nobody has logged in to the staging site from Joomshaper since you tested access a week ago. I set it up especially for Joomshaper to be able to investigate and resolve this issue.

This staging site is idling along on our server just waiting for Joomshaper develpers to use it. The problem won't fix itself. Please ask your developers to assist.

Regards,

Allen

Bump

Bump

This is an issue I've been trying to get solved since November 2021. This forum post is already a month old, and you originally submitted this issue to the developers over two weeks ago: https://prnt.sc/z-8PuxWQd092.

Can you estimate how long will this take to review and fix?

Over two weeks ago, I set up a staging site for the sole purpose of allowing your developers to easily replicate and investigate the issues I described in this ticket over two months ago, and to determine why the altered helixultimate.php plugin at https://github.com/JoomShaper/helix-ultimate/tree/master/plugins/system/helixultimate seems to largely resolve the issues, even though the plugin is not up-to-date with current 2.0.7 version. The revised plugin shows a fix is possible, and this needs to be investigated to determine what is wrong with the current 2.0.7 plugin. Nobody has bothered to log in and work on the staging site since I set it up for the developers several weeks ago. The staging site is gathering cobwebs. Why have me go to this effort if nobody is going to use it?

I've waited weeks and weeks. Weeks have turned into months. I just had to renew my subscription today in order to post this plea for a fix, and I question why I am continuing to pay for support if nothing is being done to progress this issue. I cannot update my 1.1.4 template or plugin until this is resolved, which has my site stuck in 2021.

Help? Please?

Regards,

Allen

Crickets continue to chirm. Paint is nearly done drying. Bump.

Not sure what your link is for. I already provided info for the staging site I created to for the developers to replicate and diagnose the issue.

The team has been "working on the issue" for months, yet they still haven't even logged into the staging site to begin looking at it. How are they "working on it" if they don't actually work on it? After months of waiting, this is terrible.

Check what? The URL simply shows the Cassiopeia demo, which doesn't have anything to do with this forum post.

What are you wanting me to look at?

I installed 2.0.8 to the staging site I set up for you, the same one that Joomshaper still has not used after setting it up for you over a month ago.

The same problems still exist, despite all of the warm talk of fixes Joomshaper made in its recent 2.0.8 release. No progress.

I see mounting frustration on a related form post at https://www.joomshaper.com/forum/question/6957. Joomshaper will be losing customers since it can't seem to make a relaiable product, and is not repsonsive to actually investigating and fixing reported bugs.

Thank God. Joomshaper finally fixed this issue with 2.0.9. I can finally move off of 1.1.4 after over a year of pleading for a fix.