[nodebb-plugin-glossary] Glossary Plugin for NodeBB
-
@baris From what I see, the plugin is actually firing on whole words
In this case, it's matching on
bits
as well asbit
(which it should)And also matching on
dev
insidedevil
EDIT: Sorry - this was due to the CSV import I have... Ignore that
-
@baris another suggestion would be to empty the table storing the glossary items. When you import 1000 plus from a CSV it's very clunky to have to delete them all one by one if you need to.
Allow option to empty glossary content 路 Issue #5 路 NodeBB/nodebb-plugin-glossary
A suggestion would be to empty the table storing the glossary items. When you import 1000 plus from a CSV it's very clunky to have to delete them all one by one 馃檪 if you need to.
GitHub (github.com)
-
@baris Thanks. I spotted a bug in 0.6 when performing a large import. The mapping being returned should be (for example
SNMP
Simple Network Management Protocol
comes back withSNMP
something completely wrong
)Examples
and
Not sure if my data is incorrect (I'll check), but wanted to report this in case it is actually an issue. Reverting back to 0.5 the issue is not present
and
So, I think there is a bug somewhere
-
add csvtojson support 路 Issue #7 路 NodeBB/nodebb-plugin-glossary
use https://www.npmjs.com/package/csvtojson instead of custom code
GitHub (github.com)
-
I updated the plugin to use https://www.npmjs.com/package/csvtojson so it is using the csv spec from https://www.loc.gov/preservation/digital/formats/fdd/fdd000323.shtml
-
@baris This doesn't seem to work for me at all using the latest version sadly. It doesn't matter which format I use, the import always seems to work, but exhibits the same issues as I highlighted earlier. Version
0.5
does not have these issues from what I can tell. -
It is necessary to disable the use of keywords in URLs. Plugin must not affect URL