-
I believe that Roman numerals will not be picked up automatically. However, reftagger.com describes how to use bibleref markup, which can be applied to provide hints to RefTagger for cases that it cannot resolve automatically. This is also useful for text that uses partial references when the book/chapter is clear from the surrounding context.
-
The space is gone, but the slashes are still being escaped. This is likely being caused by the text editor that you're using.
-
Note, in particular, that the original text has a space after the quotation mark, whereas the corrected version does not.
-
No special code is needed for getting Bible references to be recognized. Opening up the web page in the inspector revealed this warning: This led me to an additional error: The text ' ∕∕api.reftagger.com/v2/RefTagger.js' should instead be '//api.reftagger.com/v2/RefTagger.js'.
-
It appears that you're missing a comma after the closing quotation mark of "KJV".
-
The value is saved as soon as you leave the field or press enter. There used to be some visual indication of this, which seems to have vanished at some point. I'll file a case for the team to fix this.
-
You can see which groups you share with a person by hovering over their name. Clicking on the "down arrow" in the upper-right corner of a post reveals options for prioritizing or muting content from various sources.
-
Thanks for the report. If this happens again, could you also post a link to your group so that we can investigate the bug?
-
Biblia is now a completely different website under different ownership than it was in 2005. However, it appears that you can still find the old version cached by the Wayback Machine: https://web.archive.org/web/20051218171126/http://www.biblia.com:80/islam/history.htm
-
It looks like you've got the RefTagger code at the end of your head element, rather than at the end of your body element. This will cause errors when running in some browsers, such as Firefox and IE, because they run the script before loading the rest of the document.
-
I visited your page and opened the Chrome inspector, and this is what I saw: in your copy of the script, you have "smart quotes" in several places (“”) instead of "straight quotes" ("). This can happen if you use a text editor that tries overly hard to be helpful. If you change these back to straight quotes, the script should work again
-
[quote user="Bob Pickle"]Inge, if you haven't already, why don't you try using the full URL, https://reftagger.com/ ? I wonder if your browser is taking Reftagger.com and turning that into de.reftagger.com. If the de subdomain is in your browser history, that could be where it's coming from.[/quote] When a web browser makes a request to a server, it
-
[quote user="Inge Anderson"]But now that I have your attention, how do we change the colors on the Tool Tip if the css file is referenced from the js script.[/quote] The latest version of RefTagger has several customization options related to appearance. If those options are insufficient, you can apply further customization by creating your own stylesheet
-
[quote user="David Mitchell"]However, the initial implementation of Web App Notes is built on top of the old system, so that we can (basically) flip a switch and make Web App Notes appear in Desktop/Mobile notes if we have to abandon the current strategy for any reason. (customers hate the new UI, unforeseen technical challenges, whatever)[/quote] I
-
[quote user="alabama24"] As long as this means that the notes & highlights WILL (eventually) be integrated into the rest of the system, I fully agree with you. If this is not what is intended, but rather they mean "the note system now WILL NOT be plugged in, but eventually we will create a system WHICH WILL," then you are wrong and harm indeed will
-
[quote user="Mark Miller"]Why do I ask, it seems that Firefox version 52 no longer supports Java as of about a week or so ago.[/quote] Despite the similar name, JavaScript and Java are completely separate technologies, and Firefox discontinuing support for Java has no impact on their support for Javascript. (which remains)
-
RefTagger supports linking to Apocrypha references, but not all Bibles (including ESV, which is selected for your site) contain the Apocrypha. To enable these references, you can either change the Bible version across your site (in the RefTagger settings) or including a version abbreviation after your reference. For example: 1 Macc. 10:19 (NRSV)
-
It appears that your jQuery plugin uses a `transform: translate3d()` rule to accomplish its element position. If you have a way to find the current value of the transform rule and also apply it to all elements with the class `.rtTooltip`, your tooltips will appear in the correct position. (note that I am unfamiliar with this jQuery plugin and can't
-
It appears that teachable does not have any obvious hooks to disable AJAX page loading. Some knowledge of JavaScript would be required to work around this issue.
-
I've deployed a fix for this. (you may need to disable your cache when refreshing your website to see the change)