Manual Code vs. Plugin in WP.org
I've installed Reftagger both with the plugin and with manual code on my wordpress.org site (at separate times, not together). I have two lists http://biblesymbol.com/parables-list/ , http://biblesymbol.com/symbols/symbols-list/ (with "Inline Google Spreadsheet Viewer" plugin) that have references in them, one is a list of parables, the other is a list of Symbols, that both have the references in them.
The plugin works just fine and the way I want it to, except that I can't customize the colors etc. for my site. It tags all the references in the list if I list by 10 per page or by 100 per page. I can go to the next set of 10 and the references are all tagged. But them I decided that in order to customize reftagger I would install regtagger manually. Reftagger then worked only for the first displayed set of references that show up as in the first 10 items, if I switched to 100 items per page then only the first 10 were tagged and not the rest, until the page was refreshed, which reset the viewer back to the default 10 items per page. After installing the code manually my site had a warning message above the plugins page after deactivating the plugin and installing the code that said something like "the code was not loaded on the back end but on the front end (or vise versa) but it would still work.
It seems like I have a choice to either have customized colors and fonts, or not have all the references tagged.
Any Ideas or workarounds?
Comments
-
The site is currently working as expected, which I guess means you have the plugin installed. It will only be possible to see what's wrong with a manual installation, if we can see that manual installation. Perhaps you can switch back to that and let us know.
For future reference, I'm copying the code inserted by the plugin, which is in the footer. That will allow me to see the differences with the manual code.
<script>
var refTagger = {
settings: {
bibleVersion: "KJV",
libronixBibleVersion: "KJV",
addLogosLink: true,
appendIconToLibLinks: false,
libronixLinkIcon: "dark",
noSearchClassNames: [],
useTooltip: true,
noSearchTagNames: ["h1", "h2"],
linksOpenNewWindow: false,
convertHyperlinks: false,
caseInsensitive: true,
tagChapters: true
}
};(function(d, t) {
var g = d.createElement(t), s = d.getElementsByTagName(t)[0];
g.src = '//api.reftagger.com/v2/reftagger.js';
s.parentNode.insertBefore(g, s);
}(document, 'script'));
</script>This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
The Site is using Custom code now. I saw the error message again and this is what it says:
Reftagger is not activated, the correct Bibleref semantic markup will still be generated on the frontend, but without a link. | Hide Notice
You can see that the pop up box now matches my site, but the references on the second page are not tagged.
Thanks for looking.
0 -
Fred Littlefield said:
You can see that the pop up box now matches my site, but the references on the second page are not tagged.
When you paste the code in manually, Wordpress is putting it lower down the page than the plugin does.
I think the reason that matters is because your page works by displaying the entire table, then hiding rows on subsequent pages. When the plugin is installed, RefTagger runs before these rows are hidden, and therefore tags them. When you install the code manually it runs after the rows are hidden, and therefore they're not tagged.
The solution should be to move the manual code higher up the page. That's easier said than done, but if you have an option for putting it in the header, then that might work (although it might also be slightly slower).
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Thanks Mark. I'll try that, and report the results.
0
