Boost Union questions 4.4+

Boost Union questions 4.4+

by Wiebke Müller -
Number of replies: 16
Picture of Particularly helpful Moodlers Picture of Testers

Dear users of the Boost Union theme,

as Alex commented in the "old thread" before, we are happy to have published a first release of Boost Union for Moodle 4.4. You will find it on Github and on https://moodle.org/plugins/theme_boost_union/v4.4-r1/32585.

We kindly invite you to use this NEW thread in case of any usage and/or need for support questions you might have. As agreed with Gareth, we will now try to discuss Boost Union with one thread per major version release, since the other thread simply grew too big.

We are a team of many (sometimes power) users of Boost Union and will try to answer collectively according to our measures. If any other users know answers or simply are quicker, don't hesitate to answer! This said - I'd like to express a massive thank you to everyone for all the collective knowledge and experience that has been generously shared so far! This is very helpful and supportive for the Boost Union community smile

Thank you for using Boost Union anyway!

Regards on behalf of the team
Wiebke Müller

Average of ratings:Useful (3)
In reply to Wiebke Müller

Re: Boost Union questions 4.4+

by Clara Pouli -
I am lucky to inaugurate this thread, it is a pity that it is for a problem. T
he course index no longer loads on our moodle V4.4. The developer console tells me:

first.js:746
Uncaught Error: Reactive components needs a main DOM element to dispatch events
at new _exports.default (first.js:746:285)
at new Component (first.js:1812:174)
at Component.init (first.js:1812:259)
at view.php?id=2:2368:15
at Object.execCb (require.min.js:5:12861)
at b.check (require.min.js:5:6615)
at b.enable (require.min.js:5:9363)
at b.init (require.min.js:5:5721)
at require.min.js:5:11235

how can I solve this? How to make jquery launch before the rest?
I tested with the boost and classic theme and the index loads well.
thanks for your help
Average of ratings: -
In reply to Clara Pouli

Re: Boost Union questions 4.4+

by Susana Willemoës -
Hello Clara, I ḿ having the same issue, but in Moodle 4.0.3. Did you find a solution? 
Average of ratings: -
In reply to Clara Pouli

Re: Boost Union questions 4.4+

by Wiebke Müller -
Picture of Particularly helpful Moodlers Picture of Testers
Hi Clara!

I am not able to reproduce this behaviour. You're saying moodle V4.4 could you please tell us which boost union version you are using?
Is this observable in all browsers?
Do you already have any boost union settings activated or altered any of the source code or the appearance?


Best regards
Yvonne&Wiebke
Average of ratings: -
In reply to Wiebke Müller

Re: Boost Union questions 4.4+

by Sourabh Singh -
Getting this issue in moodle 4.2 and when I add section i will present me 3 section in which Add Activity & resource Option there. When I try to Click on Add Activity and Resource it is not click able and in console this error shown up.
After Refreshing page then functionalities working fine.
If I add other section in same course it will work good, but only getting issue when new course added.

Uncaught Error: Reactive components needs a main DOM element to dispatch events
at new _exports.default (first.js:423:285)
at new _default (first.js:1571:1)
at new Component (first.js:1386:186)
at new Component (first.js:3408:144)
at Component.init (first.js:3408:222)
at :3:15
at Object.execCb (require.min.js:5:12861)
at b.check (require.min.js:5:6615)
at b.enable (require.min.js:5:9363)
at b.init (require.min.js:5:5721)
_exports.default @ first.js:423
_default @ first.js:1571
Component @ first.js:1386
Component @ first.js:3408
init @ first.js:3408
(anonymous) @ VM2176:3
execCb @ require.min.js:5
check @ require.min.js:5
enable @ require.min.js:5
init @ require.min.js:5
(anonymous) @ require.min.js:5
setTimeout
(anonymous) @ require.min.js:5
o @ require.min.js:5
requirejs @ require.min.js:5
(anonymous) @ VM2176:2
b @ jquery-3.6.0.min.js:2
He @ jquery-3.6.0.min.js:2
append @ jquery-3.6.0.min.js:2
runTemplateJS @ first.js:920
domReplace @ first.js:920
replaceNodeContents @ first.js:920
(anonymous) @ first.js:423
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
add @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
Deferred @ jquery-3.6.0.min.js:2
then @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
add @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
Deferred @ jquery-3.6.0.min.js:2
then @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
add @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
Deferred @ jquery-3.6.0.min.js:2
then @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
Promise.then
I @ jquery-3.6.0.min.js:2
when @ jquery-3.6.0.min.js:2
get_strings @ first.js:180
(anonymous) @ first.js:920
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
add @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
Deferred @ jquery-3.6.0.min.js:2
then @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
add @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
Deferred @ jquery-3.6.0.min.js:2
then @ jquery-3.6.0.min.js:2
Renderer.doRender @ first.js:920
(anonymous) @ first.js:920
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
add @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
Deferred @ jquery-3.6.0.min.js:2
then @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
fire @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
fireWith @ jquery-3.6.0.min.js:2
s. @ jquery-3.6.0.min.js:2
e @ jquery-3.6.0.min.js:2
t @ jquery-3.6.0.min.js:2
setTimeout
(anonymous) @ jquery-3.6.0.min.js:2
c @ jquery-3.6.0.min.js:2
add @ jquery-3.6.0.min.js:2
(anonymous) @ jquery-3.6.0.min.js:2
Deferred @ jquery-3.6.0.min.js:2
then @ jquery-3.6.0.min.js:2
(anonymous) @ first.js:920
execCb @ require.min.js:5
check @ require.min.js:5
enable @ require.min.js:5
init @ require.min.js:5
(anonymous) @ require.min.js:5
setTimeout
(anonymous) @ require.min.js:5
o @ require.min.js:5
requirejs @ require.min.js:5
Renderer.render @ first.js:920
renderForPromise @ first.js:920
(anonymous) @ first.js:423
renderComponent @ first.js:423
_createSection @ first.js:3432
listener @ first.js:432
callWatchersHandler @ first.js:432
dispatchStateChangedEvent @ first.js:1375
(anonymous) @ first.js:412
_publishEvents @ first.js:412
setReadOnly @ first.js:412
processUpdates @ first.js:412
addSection @ first.js:1547
await in addSection
dispatch @ first.js:432
dispatch @ first.js:1525
_requestAddSection @ first.js:1451
_dispatchClick @ first.js:1451Understand
Average of ratings: -
In reply to Sourabh Singh

Re: Boost Union questions 4.4+

by Alexander Bias -
Picture of Core developers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers
Hi Sourabh,

I am sorry, but neither Moodle 4.2 nor Boost Union 4.2 is supported nowadays in any way. If you can reproduce this issue on a supported Moodle release, we will try our best to help you.

Cheers,
Alex
Average of ratings: -
In reply to Wiebke Müller

Re: Boost Union questions 4.4+

by Ezzeddin Hamed -
Hi Wiebke,

I believe it's better to have a new discussion, but I think it would be better if there is a way to split it more at question level like github, which separates each case; by turn the length makes it difficult to reach older issues & answers, it would be nice if there is a search specific to the discussion.

What I am trying to do is add some text like instructions to the registration form, the location I want could be within the user custom fields, but I could not find anyway like a plug to allow html/text field locked to editing, so my idea was to use any field type and make it read only.

I came up with this CSS, so that only the required field would be read only without affecting other fields using the field id, but this is not working:
#id_profile_field_some .form-control:disabled, .form-control[readonly] {
background-color: blue !important;
opacity: 1 !important;
border: 0 !important;
}

I tried different scenarios, this worked in "inspect", but did not work in Moodle. Could be something missing? I tried #id_profile_field_some & #profile_field_some for the field id.
 
Any help to make it work is much appreciated.

Thanks,
Average of ratings: -
In reply to Ezzeddin Hamed

Re: Boost Union questions 4.4+

by Gareth J Barnard -
Picture of Core developers Picture of Particularly helpful Moodlers Picture of Plugin developers

Dear Ezzeddin,

Looks like /login/signup_form.php calls 'core_login_extend_signup_form' in /login/lib.php which is:

 /** Inject form elements into signup_form.
  * @param mform $mform the form to inject elements into.
  */
function core_login_extend_signup_form($mform) {
    $callbacks = get_plugins_with_function('extend_signup_form');
    foreach ($callbacks as $type => $plugins) {
        foreach ($plugins as $plugin => $pluginfunction) {
            $pluginfunction($mform);
        }
    }
}

Thus in the theme's lib.php add a function 'extend_signup_form($mform)' and you'll be able to add Moodle form elements there.

And you don't have to reply to this thread to ask a question, you can if you wish make a separate post to 'self contain' the issue in one post with replies.

Gareth

Posting as self (registration answer) and as a moderator (discussion answer).

Average of ratings: -
In reply to Wiebke Müller

Re: Boost Union questions 4.4+

by Sandra Janisch -
Hello!
We like to use the info banners for quick information to our users. Would it be possible to restrict the visibility of the banners to individual system roles?
This would be extremely useful and practical for us.
Best regards
Sandra
Average of ratings: -
In reply to Sandra Janisch

Re: Boost Union questions 4.4+

by Wiebke Müller -
Picture of Particularly helpful Moodlers Picture of Testers

Hi Sandra, 

thanks for reaching out. This is a valid feature request and already has a ticket https://github.com/moodle-an-hochschulen/moodle-theme_boost_union/issues/500 in the github repository which also contains some discussion on the topic and a possible work around. 

Regarding the implementation, as for now we are concentrating on bug fixes and maintenance of existing features in order to keep the limited resources focused on adhering to the moodle update cycle.

Best regards
Wiebke

Average of ratings: -
In reply to Wiebke Müller

Re: Boost Union questions 4.4+

by Reinhard STAUDINGER -

Hello Wiebke and Team!

1st of all – I really appreciate the work you do and like the features and possibilities boost union offers really great.

But I found a somehow strange behaviour when I use breadcrumbs in a wiki …  this looks like …
coursename / section-title / name of wiki / <- this would be fine but is extended by 
coursename / section-title / name of wiki / selected "action" in wiki / selected subpage / selected "action" in wiki <- this is strange

I hope there is a solution to get a fix for this? Or a hint what I should do to get rid of these "action" in my loved breadcrumb? Should i report a bug on GitHub?

regards! reinhard

Average of ratings: -
In reply to Reinhard STAUDINGER

Re: Boost Union questions 4.4+

by Wiebke Müller -
Picture of Particularly helpful Moodlers Picture of Testers

Dear Reinhard,

thanks for reaching out, my first reaction was is this related to boost union or maybe a boost core issue regarding the wiki itsself? I tried to verify on https://school.moodledemo.net/ but then very quickly ran into these questions: 

  • Which moodle version?
  • If not Boost, which Boost union version?
  • Which format did you use in the wiki? See choice below. 
  • If HTML - TinyMCE oder still Atto?

grafik.png

In case this prooves to be a Boost union thing and you report it is an issue in github we would need those questions answered anyway plus the exact steps to reproduce are always very helpful.

Best regards and thank you!
Wiebke

Average of ratings:Useful (1)
In reply to Wiebke Müller

Re: Boost Union questions 4.4+

by Reinhard STAUDINGER -
Dear Wiebke,
 
Thanks for your reply – very much appreciated! I took a look at your questions and would like to provide my answers as follows …
  • Moodle: 4.4.3+
  • Boost Union: v4.4-r1 <- this is used 
  • Boost: Build 2024042200 (Standard with 4.4.3+)

  • Wiki format: tried all and there was no difference to be seen in the screenshots
  • Editor: used tiny mce and simple text – again there was no difference in the screenshots
  • Breadcrumbs are activated: theme_boost_union | categorybreadcrumbs YES

and as i was writing this i realised, that all Boost Union does is to provide a breadcrumb link to the category-page, so this seems to be a moodle core / boost bug and is not related to Boost Union … THX! 
best regards,
reinhard

Average of ratings:Useful (1)
In reply to Wiebke Müller

Re: Boost Union questions 4.4+

by David Pasadas -
Hello and thx for the theme.

I read in the readme file that only authenticated users can see the additional blocks
"As soon as an additional block region is enabled, it is visible for all authenticated users and editable by teachers and managers "

I would like guest and unauthenticated users to be able to see the additional blocks.
Is that somehow possible ?

I don't know how to code but I know how to modify code with the proper instructions.
Average of ratings: -
In reply to David Pasadas

Re: Boost Union questions 4.4+

by Wolfgang Hummel -
Picture of Core developers
Hello David,

with site admins users/permissions management you can adjust capability "theme/boost_union:viewregion..." to your indiv. needs.
Adjusting that capability enables you to show spec. regions to intended role.
e.g.: yourMoodle/admin/roles/manage.php

best regards
Wolfgang
(Boost Union Team)
Average of ratings: -