Reftagger stopped working on our HTML site about 2 weeks ago

We have gratefully used your script on our Bible Study site for years, but it suddenly stopped working about 2 weeks or so ago - on pages where it had worked flawlessly for years. 2016 example, current example.

Note that Reftagger comes up, but is unreadable, because the background is totally transparent. It looks like a CSS error. This is what we found:

Our page tries to load http://bible.logos.com/jsapi/referencetagging.js, which doesn't exist any more. Logos redirects that URL to https://api.reftagger.com/jsapi/referencetagging.js, which successfully loads. That files calls bible.logos.com/Content/ReferenceTagging.css, which likewise doesn't exist anymore, and Logos doesn't redirect that one.

So, if Logos is willing to help just a little, it's a relatively easy fix: Please restore the css file that used to reside at bible.logos.com/Content/ReferenceTagging.css.

We will change our code to reference https://api.reftagger.com/jsapi/referencetagging.js, and everything should work fine.

So, would you please restore bible.logos.com/Content/ReferenceTagging.css,?

Thank you!

[Edit:] I also note that https://reftagger.com/ no longer exists. Instead it redirects to the German site, https://de.reftagger.com/.

Find more posts tagged with

Comments

Jan Krohn

Probably caused by adblocking... use the forum search to dig out previous threads with details.

Bob Pickle

https://community.logos.com/discussion/comment/901829#Comment_901829

No, it's not caused by adblocking. The problem is that the JavaScript file is trying to use a CSS file that no longer resides at bible.logos.com.

Maybe Logos is phasing out the bible subdomain. But if that's the case, how can we edit the JavaScript file at https://api.reftagger.com/jsapi/referencetagging.js so that it points to the correct, current location of the CSS file?

Inge Anderson

https://community.logos.com/discussion/comment/901829#Comment_901829

Yes, I searched the forum an saw the references to ad blocking. But if there's a missing file to which the Reftagger script points, it can't work with or without ad blocking. We used the script for years, and it worked perfectly -- until just recently, with no change on our part.

Jan Krohn

https://community.logos.com/discussion/comment/901846#Comment_901846

Okay, so we can safely assume then that you have made sure that the file in question has indeed been removed, and not merely been filtered out by your adblocker, right?

Inge Anderson

https://community.logos.com/discussion/comment/901848#Comment_901848

Reftagger actually runs on the site, as you can tell by clicking the links I originally supplied:

2016 example, current example.

So it is not being blocked. The issue is that it is not readable, because the Reftagger Tool Tip does has only a transparent background, so is unreadable. Additionally, the text and text area is larger than the correct Reftagger script. It is fairly evident that there's a missing CSS file, and if you click on the file, you can see that it is missing, not "filtered." See bible.logos.com/Content/ReferenceTagging.css

I tried referencing a css file on our site, but it doesn't work either because the https://api.reftagger.com/jsapi/referencetagging.js script has an embedded reference to a css file that does not exist.

The solution seems fairly simple. If someone will only restore bible.logos.com/Content/ReferenceTagging.css, the JS script will work again.

This is the css text file that needs to be restored to its original URL/original name (or the JS file edited):

.lbsTooltip
{
background:#fffade;
border: 1px solid gray;
z-index: 99;
text-align: left;
text-indent: 0;
}

.lbsTooltipHeader
{
background:#fff4b8;
color: black;
font-weight:bold;
font-size:15px;
line-height: 18px;
font-family:Arial,Helvetica,serif;
margin: 0;
padding:4px;
position:relative;
border: 0;
}

.lbsTooltipBody 
{
padding: 4px 8px 0 8px;
margin:0;
position:relative;
z-index: 2;
border: 0;
line-height:16px;
}

.lbsTooltipBody p, .lbsTooltipBody span
{
display: inline;
color: black;
font-family:Arial,Helvetica,serif;
font-size: 14px;
line-height:16px;
}

.lbsTooltipFooter
{
font-size:11px;
font-family:Helvetica,Arial,serif;
bottom:4px;
margin-top: 4px;
position:absolute;
text-align:right;
border: 0;
}

.lbsTooltipFooter a:link, .lbsTooltipFooter a:visited, .lbsTooltipFooter a:hover 
{
color: blue;
text-decoration: underline;
font-weight: normal;
font-size:11px;
font-family:Helvetica,Arial,serif;
}

.lbsTooltipBody .ch-ref, .lbsTooltipBody .verse-ref
{
font-size: 85%;
top: -1px;
position: relative;
}

.lbsTooltipBody .ch-ref
{
font-weight: bold;
}

.lbsTooltipBody .verse-ref
{
color: dimgray;
}

.lbsTooltip, .lbsTooltipBody span, .lbsTooltip a, .lbsTooltipBody p
{
margin:

Bob Pickle

https://community.logos.com/discussion/comment/901848#Comment_901848

I don't have an adblocker. And I don't see any way that an adblocker would cause the web server to return a 404 error when attempting to reach directly the URL bible.logos.com/Content/ReferenceTagging.css.

Mitch (Faithlife)

Sorry about the troubles Inge!

This was indeed an oversight on our part as we were doing server maintenance.

Things should be up and working correctly now.

Bob Pickle

https://community.logos.com/discussion/comment/901890#Comment_901890

Thanks so much, Mitch. That takes care of most of the problem. RefTaggerControlPanelWide.css is being redirected to https://api.reftagger.com/Content/RefTaggerControlPanelWide.css which is still missing. Could you fix that as well?

Inge Anderson

https://community.logos.com/discussion/comment/901890#Comment_901890

Whew! Thank you so much! Reftagger is, indeed, working perfectly, just as it used to.

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.

It's easy enough to change the references to the css file in the header to point to one on our server, but it is ineffective as long as the css file reference is embedded in the js file. Is it necessary to have it embedded? (I thought that, originally, there were instructions in how to change the appearance by referencing our own css file.)

And, yes, as @Bob Pickle says, restoring the bible.logos.com/Content/ReferenceTagging.css file would ensure that our pages going back to the beginning of Reftagger will continue to work correctly.

Thanks so much.

David Mitchell

https://community.logos.com/discussion/comment/901918#Comment_901918

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.

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 that references the class names used by RefTagger.

Inge Anderson

https://community.logos.com/discussion/comment/901921#Comment_901921

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.

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 that references the class names used by RefTagger.

Thanks, David, but I see you provided an URL that used to exist but exists no more. Reftagger.com (try it!) and anything that used to be there redirects to https://de.reftagger.com/. And the only customization there is the style of the header bar on the Tool Tip - dark or light gray. And it's in German only. There are more choices at https://de.reftagger.com/customize/ - also in German. Though that's not a problem for me, it might be for others.
Since the subdomain https://de.reftagger.com/ is functioning, it seems to me it shouldn't take much to get the files back on the main domain and stop it from redirection to https://de.reftagger.com/.

A lot of people would be grateful. (It's a shame you hear from us only when something goes wrong. We have over 80,000 individual visitors a month to our plain HTML pages, but we also only seem to hear from them when something goes wrong - such as Reftagger not working. )

Graham Criddle

https://community.logos.com/discussion/comment/901941#Comment_901941

Hi Inge

Thought it worth mentioning that reftagger.com still,works correctly for me

Bob Pickle

https://community.logos.com/discussion/comment/901941#Comment_901941

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.

As with Graham, I'm not having trouble reaching https://reftagger.com/

David Mitchell

https://community.logos.com/discussion/comment/901955#Comment_901955

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.

When a web browser makes a request to a server, it includes several pieces of information, like what language the user prefers. The RefTagger website appears to have a (somewhat aggressive) bit of code that automatically redirects visitors to the version of RefTagger for their preferred language, if it exists.

Inge likely has his browser set to prefer German.

Inge Anderson

https://community.logos.com/discussion/comment/901956#Comment_901956

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.

When a web browser makes a request to a server, it includes several pieces of information, like what language the user prefers. The RefTagger website appears to have a (somewhat aggressive) bit of code that automatically redirects visitors to the version of RefTagger for their preferred language, if it exists.

Inge likely has his browser set to prefer German.

Interesting. No I don't have my browser set to prefer German, but I do have 3 "Keyboards" in my Windows setting, including German. Canadian English was active when my browser redirected me to the German version of Reftagger. (Microsoft did it.)

As for "History," I tried another browser (Microsoft Edge) which I had not used for accessing Reftagger.com and was still directed to the German site.

I cleared my Chrome browser history, as Bob Pickle suggested, and I typed in https://reftagger.com/, and I was *still* redirected to https://de.reftagger.com

So I removed Deutsch completely from my language options, opened Firefox which I hadn't used for many months, and *finally* I was able to access https://reftagger.com/ <Whew!>

Cleared by Chrome browser history again and typed in https://reftagger.com/, and still got redirected to https://de.reftagger.com!!

I'd say there is something a little too aggressive about the Reftagger code! There may be other settings on my computer that include German, but I have no idea where they are. American English is my preferred setting, although Microsoft sometimes drops me back to Canadian English just like Google forces me to search with Google.ca

Now I know that I can only access Reftagger on Firefox! Is it necessary for the code to be so domineering?!