dbnschools / moodle-theme_fordson

Theme for Moodle 3.3+
42 stars 40 forks source link

'Sticky blocks' not working in version 2019111003 / moodle 3.6 #85

Closed infinitesunrise closed 4 years ago

infinitesunrise commented 5 years ago

Typically, moodle blocks with a '*' asterisk in their pagetypepattern table field are considered sticky blocks, and will show up on any page at a hierarchical level that matches the pattern provided. I am administering multiple sites on moodle 3.6.4 running theme_fordson 2019111003 and on all of these sites I am seeing that the sticky blocks seem to break under the Fordson theme. These blocks were all set to side-post, and as I know Fordson introduces A/B/C block columns I tried switching blocks from side-post to column C, but the issue persists.

Upon turning on site debugging, I get the following messages in the browser console on page load in courses where these blocks should display but don't:

moodle-core-event: Global event published: FORM_ERROR yui_combo.php:5828:31  
moodle-core-event: Global event published: BLOCK_CONTENT_UPDATED yui_combo.php:5828:31  
warn: The moodle-core-notification parent module has been deprecated. Please use one of its subclasses instead. yui_combo.php:5828:31  
moodle-core_blocks: Block drag and drop initialised for the blocks method. yui_combo.php:5828:31  
Initialising drag and drop for blocks. yui_combo.php:5828:31  
Block region 'side-pre' initialising yui_combo.php:5828:31  
block region known about but no HTML structure found for it. Guessing structure. yui_combo.php:5828:31  
Block region 'fp-a' initialising yui_combo.php:5828:31  
Block region 'fp-b' initialising yui_combo.php:5828:31  
Block region 'fp-c' initialising yui_combo.php:5828:31  
Initialisation of drag and drop for blocks complete. yui_combo.php:5828:31  
moodle-core-event: Event fired: filter-content-updated

The 'block region known about but no HTML structure found for it.' warning seems like a red flag that block content is being loaded and an attempt is being made to apply the content to the page, before page HTML is finished loading. Could this be the issue that I'm seeing? And if so, is there a way to address this? TY!