block_navbuttons
Maintained by Davo Smith
Add customisable navigation buttons (next/prev/etc.) to the bottom of each activity page (Moodle 1.9/2.0+)
408 sites
20 fans
Moodle 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 3.0, 3.1, 3.2, 3.3, 3.4

Navigation buttons (for Moodle 1.9 / 2.0+)
This block adds customisable navigation buttons (first/previous/next/etc.) to the bottom of each activity/resource page in a course.

It is based on an idea from Penny Mondani: http://pennymondani.com
Thanks also to the US company that sponsored the development, who wish to remain anonymous.

Installation:

2. On your server, in the 'blocks' folder, create a subfolder called 'navbuttons'
3. Upload all the files inside the 'davosmith-moodle-navbuttons-???????' folder to this new 'navbuttons' folder on your server.
5. You need to make a small change to one Moodle core file to make this work (the change is different between Moodle 1.9 & Moodle 2.0 - see the included README.txt for details).
7. Customise the button appearance by clicking on 'Edit the Navigation Button settings' in the newly created block.
8. Check the message at the bottom of the screen (under the 'Save changes' button) - it should read "Navbuttons self-test: required core modifications have been completed successfully". If not, then go back to step 5 above and check carefully.

Note: The block is only visible to users who are able to edit courses modules. Deleting the block will remove the navigation buttons (they can also be disabled through the settings).

For a quick demo, there is a screencast available here:

### Awards

• Thu, 21 Dec 2017, 5:45 AM
Hi Davo,

I modified the outputrenders.php file as instructed in the readme file but mine still does not work. I am running Moodle 3.3 with the Adaptable 1.5.3 theme.

The output says Navbutton self-test: The line "$output = draw_navbuttons().$this->container_end_all(true);" has not been correctly added to outputrenderers.php - see README.txt for further instructions

This is what I put in the php file:

public function footer() {
global $CFG,$DB, $PAGE; // Give plugins an opportunity to touch the page before JS is finalized.$pluginswithfunction = get_plugins_with_function('before_footer', 'lib.php');
foreach ($pluginswithfunction as$plugins) {
foreach ($plugins as$function) {
$function(); } } require_once ($CFG->dirroot.'/blocks/navbuttons/footer.php');
$output = draw_navbuttons().$this->container_end_all(true); {
// Change this line to enable the navigation buttons
}

$footer =$this->opencontainers->pop('header/footer');

• Thu, 21 Dec 2017, 3:01 PM
Please switch to one of the standard themes (boost or clean) and see if it works. If it does, then to get it working with essential, you'll need to find where that theme overrides the 'footer()' function and add the core change there instead.
• Fri, 23 Mar 2018, 6:21 AM
Sidenote. If you're using the essential theme, the line of code you need is in: public_html/theme/essential/classes/output/core_renderer.php
• Tue, 15 May 2018, 4:43 PM
Hi Davo, I think there's an error in the latest zip folder. For the plugin version 3.4+ (Build: 2017100900) (2018042100), when I click the green download link, the zip folder that I download is completely empty.
• Wed, 16 May 2018, 3:46 AM
Thanks Stewart - it's a problem with the github import not working properly as the plugin has been moved into the 'other' category, rather than the 'blocks' category (which breaks a lot of features of the plugins DB). Unfortunately, the plugin still needs a tiny core (or theme) modification to work, so it doesn't get to go anywhere else ...
• Wed, 16 May 2018, 3:46 AM
• Fri, 25 May 2018, 4:26 AM
Hi Davo!
I have a question about the plugin. When I click on Navigation Button settings, I see this message: Navbutton self-test: The line "$output = draw_navbuttons().$this->container_end_all(true);" has not been correctly added to outputrenderers.php - see README.txt for further instructions.

Can you helpme to fix this? I really want to use your plugin.

Thanks!
• Fri, 25 May 2018, 4:51 AM
Hi Angela,

Have you read through the README.txt file included with this plugin (as it suggests in the error message)? If so, is there a particular bit of the instructions that you are struggling with?
• Sun, 3 Jun 2018, 6:25 PM
A note for users using Adaptable theme, The line "$output =$this->container_end_all(true);" is located in :

It's on line 1467 (but obviously this may change as the theme version changes).
• Wed, 29 Aug 2018, 4:02 PM
Hi Davo,
since weve updated our test-system to moodle 3.5 we have some trouble with the Plugin.

Our problem is, that we get an error when we try to change the "Buttons-type" to "Text" or "Simplified text:
Fehler: Argument 1 passed to file_get_all_files_in_draftarea() must be of the type integer, null given, called in [dirroot]/lib/form/filemanager.php on line 336

All the other settings can be edited without getting that error...

Is there a solution for this error?

• Thu, 6 Sep 2018, 4:12 AM
Hi Sebastian,

I've had a quick look at this, but I've not been able to reproduce the error with my plugin and Moodle 3.5. Looking at the code, I can't find a function file_get_all_files_in_draftarea() - the closet I can see is file_get_draftarea_files().

I'm afraid that without being to reproduce this locally, I can't really offer any insight as to what might be going wrong. If you were able to offer any extra details or some step-by-step instructions about how to reproduce this on a clean installation of Moodle 3.5, then I might be able to offer a fix.

Davo
• Mon, 17 Sep 2018, 4:22 PM
Hi Davo,
i haven't tried to reproduce this error on a clean moodle yet, but i can find the function "file_get_all_files_in_draftarea()" in my "filemanager.php".

Here is the class with the function/error inside (line 302):
https://codeshare.io/2jrLJg

Maybe this helps you to understand what the problem is.

But I guess this error is caused by one or more updated plugins which don't like each other...
On the live-system, which runs moodle 3.4 and the same plugins, you're plugin works well.

Sebastian
• Wed, 26 Sep 2018, 3:00 PM
Hi Davo,
the Plugin works now!

After the moodle update from 3.5.1 to 3.5.2+ it works.

Sebastian
• Fri, 28 Sep 2018, 5:42 PM
Hi, whenever we update our moodle, this plugin does not seem to carry over to the new version. As a result we have to re-add the navbutton block to every course each time we update moodle.

Is there something we should be doing instead? How do we make the navbutton blocks for each course carry over to the new moodle?

Also, is there a way to change the default icons on navbuttons? We tried replacing the png files in moodle/blocks/navbuttons/pix but it doesn't do anything. As we need to add the block to each course, then add our own icons for each block, this seems to be taking more effort than it should have. Is there an easier way to do it?
• Fri, 28 Sep 2018, 5:51 PM
Hi Chye Siaw,

I can think of no reason why the block would need adding to every course when upgrading - certainly my local test copy of Moodle has been upgraded a great many times without ever needing to do this.

Replacing the blocks/navbuttons/pix/* files is the correct way to change the default icons - if that doesn't change anything, then you need to clear your site or browser cache to see the difference.

Ideally if I was rewriting this plugin now, I'd introduce a better way of handling configuration across multiple courses, but it was written a long time ago and I'm unlikely to overhaul it anytime soon.