Bglinks (also known as BIBLE GATEWAY REFERENCE TAGGING TOOL) transforms all plain-text Scripture references on a webpage into hyperlinks to the appropriate Bible passage from When you hover the mouse pointer over the hyperlinked text, the text of the Bible passage appears in a popover window, allowing the visitor to view the passage without leaving the current web page. Inside the pop-over window are links to view the passage on as well.

The original version is located here. This is a modified version for Wikians to use, primarily for Bible Wiki.


See also: Help:JavaScript and CSS Cheatsheet, Help:Including additional JavaScript and CSS
  • For site-wide use, an administrator can add the code snippet below to the wiki's MediaWiki:Wikia.js page. Note that Wikia's content review extension must be installed on the wiki. For personal use, add the code snippet below to your global.js page (for use on all wikis) or your common.js page on your wiki (for use on a single wiki).
    type: 'script',
    articles: [
importArticles — Best Practices for installing JavaScript on FANDOM

The importArticles statement is designed to combine multiple HTTP requests into a single data transfer, allowing multiple scripts to load and execute faster. If you've been installing several different scripts, your JavaScript file has probably accumulated unnecessary import statements. Click "Expand" to learn how to efficiently batch import scripts to speed up performance and make your code look cleaner. One other approach is by using the MediaWiki:ImportJS.

If your JavaScript file has several lines of code that say importScript, importScriptPage, or importArticles, you may be able to combine them! By batch importing a collection of scripts with a single import, your JavaScript code will load faster and look cleaner. Consider the example below. On the left is an example of what your JavaScript file might currently look like. On the right is how you could improve that code.

Multiple imports — messy and slow One import — clean and efficient
  type: 'script',
  article: 'u:dev:FloatingToc/code.js'
importScriptPage('page1.js', 'wikiname');
importScriptPage('page2.js', 'wikiname');
  type: 'script',
  articles: [

Note: In this example, pay close attention to the placement of commas and other punctuation. For people who aren't familiar with programming (and even those who are!), a common mistake when writing code is to accidentally delete, forget, or misplace critical symbols like commas or quotation marks. This can cause a syntax error that breaks the code. Carefully follow the convention shown here when using importArticles.

But there's much more to importArticles than just this! For more examples and advanced usage, see the help page at Help:Including additional JavaScript and CSS.


There are some configuration options that if used, must be placed above the installation code (see above)

Here are the configuration options that you must use (Replace <version> with any available version of your choice, see here for available versions):

BGLinks.version = "<version>";

There are also some custom configuration options that you can use if you want to:

  • Use to find references to books in the Apocrypha (default false):
BGLinks.apocrypha = true;
  • Use to show the tooltip when clicking the link rather than when hovering over it (default false):
BGLinks.clickTooltip = true;
  • Use to add links to Bible Gateway without any tooltip functionality (default true):
BGLinks.showTooltips = false;
Using configuration options with FANDOM Open Source Library scripts
The instructions on this page describe how to use configuration options with a script. Here on the FANDOM Open Source Library, many scripts provide optional configuration settings as a mean to alter or enhance the default behavior of the script. When installing configuration options in your JavaScript file, please note that they need to go above the import statement in order to work — unless the directions say otherwise. In case MediaWiki:ImportJS is used to load the scripts, it will be executed last.
Configuration options load too late, don't work
Proper placement of configuration options
// 1. AjaxRC import statement
// 2. AjaxRC configuration option
var ajaxRefresh = 30000;
// 1. AjaxRC configuration option
var ajaxRefresh = 30000;
// 2. AjaxRC import statement