Nevermind. I found it. You have to visit a feed to find it and it only works with topic or category feeds, not the "recent" feed. I can work with this tho. Thanks @PitaJ

@pitaj Thanks for that link. Looks like exactly what I was looking for. I can't seem to find the users RSS tokens though? They aren't in their account info or anywhere else

bump

Has there been any progress on this? If @psychobunny or @julianlam has any insights on how this might be achieved, I'd be open to writing my own plugin or better yet, integrating the authentication of the existing write-api plugin into RSS feeds so we could pass a user token in the get request for the rss feed.

Nevermind I fixed it with the session-sharing plugin. I set it to revalidate instead of trust.

@julian Unfortunately I ended up nuking the repostory and rechecking it out mulitple times trying to fix it.

In the future I know I can't trust the database entirely. I'll have to backup all the files (that I thought were ephemeral).

For some reason my login sessions seem to be messed up somehow. I stay logged into nodebb without issue but when i click the admin link, it redirects me to the login page. If i login again and try to go to admin, i get redirected to login, over and over no matter what i do. If i logout of the forum and then log back in I can access the admin section again for a little while but at some unspecified time in the future that session or cookie seems to expire and im back to only being a normal user.

To be clear, I can still access my account details and I can post on the forum as myself and everything else acts like im logged in, I just can't access the admin panel.

Sorry for the necropost but I'm just now getting back into this. I was so upset I had to take some time to cool off. I was upgrading from 1.1.x to 1.5.1 and I guess that was what the issue was. If i could just go back to the old way it was and forgo upgrading I would. I did backup the database but not the node_modules so I have no idea what was installed and what version.

Is there any way to tell what version of nodebb was installed by looking in the database somewhere? It's a redis DB btw if that matters. I opened the dump file on my workstation and poked around looking for some info but the current nodebb version didn't seem to be included anywhere.

I know I should probably cool off before posting but I am getting really fed up with this project. Every single time I do an upgrade I end up having to wipe everything and start over. Thankfully I get to keep my redis database and the user posts and stuff but half the damn plugins dont work anymore, the templates are broken, things are randomly missing settings... Like why should I even bother. Once I get it working I'm never EVER upgrading again. I'd switch to a different platform if it wasn't too late

To add some specific complaints instead of just ranting:

• Why is there no way to roll back once you upgrade?
• Why is there no way to record what version of plugins you have installed besides copying the entire node_modules directory (that is ignored from source control btw)?
• Why do half the plugins and all my templates break when I upgrade? And to be clear I don't mean half the plugins are disabled because they are incompatible, oh no, i would be fine with that, instead they are enabled and upgraded but just don't work, or they lose their settings, or worst of all they break the rest of the application so I only get half a page to load in the browser or something.
• Why do I get copious javascript errors in the console when I try to view the new version? Clearing cache isn't enough, I have to manually purge the files from the public directory and re-generate them..

This all seems very shoddy. The cynic in me thinks this is an effort to drive people toward the paid version of nodebb but I refuse to believe that. I've interacted with some of the main devs here on the forums and they always seemed very helpful and open. But this application is an absolute minefield to maintain. At this point I need to make a full backup of the entire directory in addition to the database to be safe while upgrading (which is not the recommended process, they recommend you use the nodebb git repo, check out a new tag and run the ./nodebb upgrade script). I'm going to have to treat nodebb like it's nitroglycerin from now on.

If I'm doing something wrong or there's a new accepted way please enlighten me but for now I'm going to return to smashing my face into my keyboard while I figure out a way to recover this disaster.

@pichalite That does work as well but it's not obvious for users not familiar with markdown. They will just paste the code in raw. Having a recognizable code button would help usage.

There used to be a code button plugin. According to google the only one that exists still is a fork of an old plugin that's only supported on 0.7.0. Does no one have a need for a code button? I guess no one posts code syntax on their forums. I need one bigtime. I guess i'll have to create one from scratch.

(I know you can just add 4 spaces before the line to create a code block but adding scripts > 10 lines or so makes this painful)

This is a huge undertaking, especially considering the updates it requires to stay in line with the fast-paced development of nodebb. I'm surprised @psychobunny was able to keep up at all considering they maintain dozens of plugins already.

@julian Hey, I must be missing something. I installed the latest version of the write-api on my 0.7.x stable install and i'm unable to pull any of the authenticated read-only api calls, for example:

curl -H "Authorization: Bearer APIKEY" https://forum.nzb.cat/api/recent

I get the same response regardless if I use a master token or a user token:

{"topics":[],"nextStart":20,"feeds:disableRSS":false,"rssFeedUrl":"/recent.rss","breadcrumbs":[{"text":"[[global:home]]","url":"/"},{"text":"[[recent:title]]"}],"loggedIn":false,"template":{"name":"recent","recent":true}}%

I did test with the write endpoints to make sure the API was working correctly however I did seem to have an issue using master tokens when pulling a GET based endpoint. Adding ?_uid=n to the end of the URL did not work and using --data switched the type to POST instead which also didn't work.

Aaaaaamazing. Thank you very much @julian

ping @psychobunny any ideas? This has come up again. I want to create a script that reads the RSS feed for a category and outputs new posts to various locations (irc, slack, etc) but i can't do this without authentication since it's a private forum.

@Sadtaco said:

Even if the solution is "use OAuth", there should at least be a NodeBB plugin that has those settings to input for those URLs for your OAuth landing.

Yea, there is, it's called nodebb-plugin-sso-oauth. It's what I finally ended up using to integrate my site. It works pretty well actually.

@psychobunny Sure, here ya go:

<head>
	<title>NodeBB Admin Control Panel</title>
	<meta name="viewport" content="width=device-width, initial-scale=1.0">

	<link rel="stylesheet" href="/vendor/jquery/css/smoothness/jquery-ui-1.10.4.custom.min.css?v=v0.5.0-2-3305-g62a2e9f">
	<link rel="stylesheet" type="text/css" href="/vendor/nanoscroller/nanoscroller.css?v=v0.5.0-2-3305-g62a2e9f">
	<link rel="stylesheet" type="text/css" href="/admin.css?v=v0.5.0-2-3305-g62a2e9f" />

	<script>
		var RELATIVE_PATH = "";
		var config = JSON.parse('{"relative_path":"","socketioTransports":["polling","websocket"],"websocketAddress":"","version":"0.7.0-dev","siteTitle":"NZBCat Forums","showSiteTitle":true,"postDelay":"10","minimumTitleLength":"3","maximumTitleLength":"255","minimumPostLength":"8","maximumPostLength":"32767","hasImageUploadPlugin":true,"maximumProfileImageSize":"256","minimumUsernameLength":"2","maximumUsernameLength":"16","minimumPasswordLength":"6","maximumSignatureLength":"255","maximumAboutMeLength":"500","useOutgoingLinksPage":false,"allowGuestSearching":false,"allowGuestHandles":false,"allowFileUploads":false,"allowProfileImageUploads":true,"allowTopicsThumbnail":false,"allowAccountDelete":false,"privateUserInfo":true,"privateTagListing":false,"usePagination":false,"disableSocialButtons":false,"disableChat":false,"maxReconnectionAttempts":5,"reconnectionDelay":1500,"tagsPerTopic":5,"minimumTagLength":3,"maximumTagLength":15,"topicsPerPage":20,"postsPerPage":10,"maximumFileSize":"2048","theme:id":"nodebb-theme-persona","defaultLang":"en_US","userLang":"en_US","loggedIn":true,"cache-buster":"v0.5.0-2-3305-g62a2e9f","script-buster":"7c252825","css-buster":"9d2983c6","requireEmailConfirmation":false,"topicPostSort":"oldest_to_newest","categoryTopicSort":"newest_to_oldest","csrf_token":"v6xPIZMH-i2zZSdlzssZA8HFfa9udNvgugus","searchEnabled":true,"notificationSounds":false,"openOutgoingLinksInNewTab":false,"topicSearchEnabled":false}');
		var app = {
			template: "admin/general/dashboard",
			user: JSON.parse('{"username":"KingCat","userslug":"kingcat","email":"[email protected]","picture":"/uploads/profile/5-profileimg.png","email:confirmed":false,"uid":5}')
		};
	</script>

	<!--[if lt IE 9]>
		<script src="//cdnjs.cloudflare.com/ajax/libs/es5-shim/2.3.0/es5-shim.min.js"></script>
		<script src="//cdnjs.cloudflare.com/ajax/libs/html5shiv/3.7/html5shiv.js"></script>
		<script src="//cdnjs.cloudflare.com/ajax/libs/respond.js/1.4.2/respond.js"></script>
		<script>__lt_ie_9__ = 1;</script>
	<![endif]-->

		<script type="text/javascript" src="/vendor/chart.js/chart.min.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/vendor/hammer/hammer.min.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/nodebb.min.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script>
			require.config({
				baseUrl: "/src/modules",
				waitSeconds: 3,
				urlArgs: "v=v0.5.0-2-3305-g62a2e9f",
				paths: {
					'admin': '../admin',
					'vendor': '../../vendor',
					'buzz': '../../vendor/buzz/buzz.min'
				}
			});

			app.inAdmin = true;
		</script>
		<script type="text/javascript" src="/vendor/colorpicker/colorpicker.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/src/admin/admin.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/vendor/ace/ace.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/vendor/nanoscroller/nanoscroller.min.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/vendor/jquery/event/jquery.event.drag.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/vendor/jquery/event/jquery.event.drop.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/vendor/semver/semver.browser.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/vendor/jquery/serializeObject/jquery.ba-serializeobject.min.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/vendor/jquery/deserialize/jquery.deserialize.min.js?v=v0.5.0-2-3305-g62a2e9f"></script>
		<script type="text/javascript" src="/vendor/mousetrap/mousetrap.js?v=v0.5.0-2-3305-g62a2e9f"></script>


	</head>

BTW, I've re-enabled all the plugins as they didn't seem to affect this issue.

@julian Ok so I booted up a new freshly installed windows VM and loaded up firefox. Visiting my forum I don't see any of these errors. I don't know what's going on with my chrome/firefox/opera/safari on my other systems but they seem to be holding onto the cache even though i've cleared it many times completely and rebooted. For some reason they continue to have the errors...

@julian Did that. I even nuked the entire public directory and re-pulled it down from git just to make sure. Restarted nginx and cleared all cache in the browsers.

@julian Nope, vanilla everything. I do have some custom CSS in the custom CSS section of the ACP to fix some skinning problems of Persona but no javascript or anything.

@psychobunny

[email protected] /data/nodebb2
└── [email protected]