library.js is server-side java script, not jQuery. jQuery functionallity can be simulated with eg cheerio
main.js is included in HTML (client-side), here u can use jQuery.

what's the value of the "last logged in" option? How do I query that in the settings?

https://github.com/NodeBB/nodebb-widget-essentials/issues/38

Content inside widgets can not be translatet, because the plugin will only get the transaltion for the default language as set in acp. It ignores the user profiles language.

can anyone confirm this?

AlexGalax created this issue in NodeBB/nodebb-widget-essentials

closed Translation ignores user settings #38

got it! had to add the folter/files for the default language en-GB as set in apc, even though my user account language is de.

so it's not possible, using translation in widgets?
But it's weird, that nodebb is recognizing it as a translation.

@pitaj said in [nodebb-plugin-calendar] Fully featured calendar plugin for NodeBB - Testers needed:

@alex-galax the best way to override templates is probably to create a new plugin with a templates directory and a plugin.json set to {}. You can override the templates that way if you copy the calendar templates over.

I created the plugin with the following structure.

nodebb-plugin-ns-theme/
├── templates/
│   └── calendar.tpl
├── package.json
└── plugin.json

plugin.json is an empty object and calendar.tpl has only some text for testing. I activated the plugin, set its position below calendar in the apc sorting settings and build everything. But its still the old calendar

it's working now. did it with a regular plugin setup.

library.js is server-side java script, not jQuery. jQuery functionallity can be simulated with eg cheerio
main.js is included in HTML (client-side), here u can use jQuery.

In my languagefile, I have all the transaltions { "greeting": "Oh, Hi." ... }.

When I include [[mytheme:greeting]] in template files, the correct text will be displayed.
But in widgets as title or html content, I get the log Missing translation "mytheme:greeting".
Why so?

@pitaj yeah I can imagine its not that easy. I'd probably extend data.postData.event = {...} and go from there. For now I found a css only solution.

@pitaj that's true. I will try how far I come with pure css.
I mean, I'd like to have it as a <li component="post" element. Why isn't that html code parsed as a tpl anyways?

@pitaj want to change the panel layout. shure, could be done in css but its not neat
best thing for my layout would be the event as a seperate post component. and for that I need to change the plugin anyways. but i still have no idea, why the fork won't install correctly