Ahhh, the humanity!
lulzdev
Posts
-
0.9.0 Breaking Changes -
[nodebb-plugin-custom-pages] "You seem to have stumbled upon a page that does not exist."tried that command: did not revert. restarted; same. Uninstalled and tried that command; did not install. Restarted and still not.
Have been getting this error recently when installing plugins:
Not at the time that i tried to revert custom pages, but it may be a factor in troubleshooting. Using Persona, as well. Not sure that error reads vanilla.I am unsure what i can place into the custom pages field to make it work. It has not worked at all.
-
[nodebb-plugin-custom-pages] "You seem to have stumbled upon a page that does not exist."After creating a test page, i cannot find a combination of settings that produce any result other than the error, "You seem to have stumbled upon a page that does not exist."
What is a working example of code that produces a working custom page; code structure of each field, header, body, footer.
Or
Where exactly are the files to be changed; a click path or full folder location.I tried copy pasting the global code and using an existing widget and even tried touch test.tpl in the theme folder with the other .tpl files... only the error.
-
Offcanvas sidebar with categories?Awesome. I chose Nodebb for flexibility; become the forum/CMS that I need. Nodebb never ceases to surpass expectations.
-
Offcanvas sidebar with categories?I am planning on having several plugins coded by freelancers, Is there anything in the core, or otherwise, that would prevent me from removing the categories from the home page and placing them into an offcanvas sidebar?
-
Plugins in coffeescript?Thanks for the answer
-
Plugins in coffeescript?There's a coder that coded a program in coffeescript that i would like ported to nodebb. Are there any issues with coding nodebb plugins in coffeescript?
-
plugin-custom-homepage wont loadIs there a list of confirmed compatible plugins?
-
plugin-custom-homepage wont loadTried to install Carousel and it too does not show in the list as if it did not install. then i tried searching for a plugin listed inside the forum and install extended-header plugin and it did work.
-
plugin-custom-homepage wont loadThe plugin does not show up in the built in search and when loaded from the command line the plugin does not show up in the list of installed plugins.
tried:
npm i nodebb-plugin-custom-homepage
npm install nodebb-plugin-custom-homepage
sudo npm i nodebb-plugin-custom-homepage
sudo npm install nodebb-plugin-custom-homepageNo joy.
Is it broken or I am doing something incorrectly?
-
NginX configuration assistance with NodeBB, Redis and Ubuntu 12.04.5 32bit on Digital Ocean dropletHey thx for the update. its never too late.
-
How to use plugin-custom-homepage??installing from the command line does not place this plugin into the list of installed plugins. Is this plugin still functional after the last update?
-
Adding a button to each post+1
would also like to be able to add a configurable button to posts.
-
NginX configuration assistance with NodeBB, Redis and Ubuntu 12.04.5 32bit on Digital Ocean dropletThe three options in the docs were not clear as options rather than mandatory. Nginx.conf moved from the first option to the second option and it then worked.
-
NginX configuration assistance with NodeBB, Redis and Ubuntu 12.04.5 32bit on Digital Ocean droplet@Fastidious said:
Check nodebb is running fine by going to the fully qualified domain name, port 4567.
Configuration
NGINX-served sites are contained in a server block. This block of options goes in a specific place based on how nginx was installed and configured:/path/to/nginx/sites-available/* – files here must be aliased to ../sites-enabled
/path/to/nginx/conf.d/*.conf – filenames must end in .conf
/path/to/nginx/httpd.conf – if all else fails
Below is the basic nginx configuration for a NodeBB build running on port 4567:What is the *.conf; the nginx config file listed just below that?
-
NginX configuration assistance with NodeBB, Redis and Ubuntu 12.04.5 32bit on Digital Ocean dropletAfter following the many imperfect tutorials online, Our forum is up and running, but only on port:4567.
NginX has been installed, and configured (although not properly)
Now when navigating to http://sitedomain.com we are welcomed by the NginX "default" html, and not our forum.Some information that might be helpful:
Location of forum : /var/www/sitedomain
No special permissions have been applied to the folder.Nodebb configuration
When node app --setup asks for a url, the Virtual droplets IP address was inserted
everything else was set as default.The current overall configuration has two issues.
The first issue is that the sites-available/sitedomain (which is linked to the sites-enabled/sitedomain) is not configured at all (removed all previous configuration as nothing has worked yet) I have tried every configuration online, including the virtual server configuration notated in the "default" file.
The second issue is that something by default is still pointing NginX to load the Default file rather than the file, sitedomain.
Attempting to bypass the latter issue, I replaced the root path in the default configuration with the root path /var/www/sitedomain.
This result is NginX providing a 403 Forbidden error when navigating to http://sitedomain.com.
Unsure of what I am doing in the sites-available configuration, I am going off the knowledge of the many flawed tutorials, that I also need an "index" line pointing to the file that is actually loading the forum. Unfortuately, I have tried multiple files, with multiple attributes, most of which result in the downloading of ,for example, the nodebb.bat file straight to my computer, which makes me believe that it is not a permissions issue.If anybody could provide me with what they believe is the best <sitedomain> configuratin (located in sites-available) based on what I have described, along with where I need to configure nginx to look to my sitedomain file, rather than default, I would be very greatful.
After following the many imperfect tutorials online, Our forum is up and running, but only on port:4567.
NginX has been installed, and configured (although not properly)
Now when navigating to http://sitedomain.com we are welcomed by the NginX "default" html, and not our forum.Some information that might be helpful:
Location of forum : /var/www/sitedomain
No special permissions have been applied to the folder.Nodebb configuration
When node app --setup asks for a url, the Virtual droplets IP address was inserted
everything else was set as default.The current overall configuration has two issues.
The first issue is that the sites-available/sitedomain (which is linked to the sites-enabled/sitedomain) is likely not configured properly as I have tried every configuration online, including the virtual server configuration notated in the "default" file.
The second issue is that something by default is still pointing NginX to load the Default file rather than the file, sitedomain.
Attempting to bypass the latter issue, I replaced the root path in the default configuration with the root path /var/www/sitedomain.
This result is NginX providing a 403 Forbidden error when navigating to http://sitedomain.com.
Unsure of what I am doing in the sites-available configuration, I am going off the knowledge of the many flawed tutorials, that I also need an "index" line pointing to the file that is actually loading the forum. Unfortuately, I have tried multiple files, with multiple attributes, most of which result in the downloading of ,for example, the nodebb.bat file straight to my computer, which makes me believe that it is not a permissions issue.Some configuraions I have tried using before:
How To Install nginx on Ubuntu 12.04 LTS (Precise Pangolin) | DigitalOcean
This tutorial explains how to install nginx, how to start nginx, and how to confirm that nginx is running on your server. nginx is a high performance web se…
(www.digitalocean.com)
How to Install NodeBB on Ubuntu 18.04 - RoseHosting
How to Install NodeBB on Ubuntu 18.04 - RoseHosting
RoseHosting (www.rosehosting.com)
If anybody could provide me with what they believe is the best sitedomain configuratin (located in sites-available) based on what I have described, along with where I need to configure nginx to look to my sitedomain file, rather than default, my team would be very appreciative.