Ahh dang, would definitely be a nice feature! I've resorted to making a quick and dirty plugin that will add new fields in the composer.tpl file.
Would be nice to one day have this plugin up and running to make my forms much more flexible!
Ahh dang, would definitely be a nice feature! I've resorted to making a quick and dirty plugin that will add new fields in the composer.tpl file.
Would be nice to one day have this plugin up and running to make my forms much more flexible!
I recently upgraded my forum to v1.5.1 and my "Recent Cards" plugin to v0.4.0 (https://github.com/NodeBB-Community/nodebb-plugin-recent-cards#readme).
However, after enabling the plugin, the recent cards carousel no longer appears. The admin panel shows that it's activated and this is what inspecting the page shows-
Any others experiencing this?
I recently upgraded my forum to v1.5.1 and my "Recent Cards" plugin to v0.4.0 (https://github.com/NodeBB-Community/nodebb-plugin-recent-cards#readme).
However, after enabling the plugin, the recent cards carousel no longer appears. The admin panel shows that it's activated and this is what inspecting the page shows-
Any others experiencing this?
So I finally got around to upgrading my forum for v1.4.5 to v1.5.1. I followed the steps in the documentation for upgrading (https://docs.nodebb.org/configuring/upgrade/) but when I started my forum back up, it wouldn't let me log in!
Instead, I'm taken to a page that simply says "Forbidden" while my console log says "error: /login invalid csrf token". Anyone ever experienced this? I know others had seen similar issues with an older version but was never able to find if there was a definitive solution.
Any help or suggestions is greatly appreciated!
@Master would love to know how you did this!
I added text into the "Forum Terms of Use" section on the ACP ("Settings -> User -> User Registration") but when users register for a new account, they're never prompted or shown this text.
Has anyone else experienced this problem? I need users to "Agree" to my ToU before registering. Is there some type of plugin or fix for this?
Ahh dang, would definitely be a nice feature! I've resorted to making a quick and dirty plugin that will add new fields in the composer.tpl file.
Would be nice to one day have this plugin up and running to make my forms much more flexible!
Similar to something like <!-- IF !isTopicOrMain --> or <!-- IF !isEditing -->, is there some variable I can check in my .tpl file to see which category or subcategory I'm in?
I'm building out a custom composer that changes based on where the topic is being posted. For instance, it would know that I'm currently in the "NodeBB Plugins" category and display a particular part of my .tpl file, otherwise it wouldn't.
@yariplus Would this plugin allow forms to submit content as new topics in certain categories?
I'm currently looking for the best method to create custom forms so that when users create new topics, their posts are uniform and contain certain fields of information.
I put in a request for a plugin but honestly not sure what the best route would be -https://community.nodebb.org/topic/10326/custom-forms-for-new-topics-in-certain-categories
I'm looking to include custom forms on my site so that users can post uniform data for certain categories.
What would be the best way to tackle this? Would I need to create an entire plugin for a new composer, just make a custom .tpl file, etc.?
Looking for any suggestions or help! Attached are a few mockups of the form from an older website-
I'm looking to include custom forms on my site so that users can post uniform data for certain categories.
What would be the best way to tackle this? Would I need to create an entire plugin for a new composer, just make a custom .tpl file, etc.?
Looking for any suggestions or help! Attached are a few mockups of the form from an older website-
Interesting, thanks! I had my forum set up on a subdomain; decided to try changing my config.json file back to it's original version and the error seems to be cleared up.
I'll be sure to monitor this error if I want to change back to the subdomain.