For those following this thread.
I just did an import recently, and the latest import seems to be working great.
There is even a new import interface. Do check it out!
For those following this thread.
I just did an import recently, and the latest import seems to be working great.
There is even a new import interface. Do check it out!
Was playing around with this plugin, its working great with posts and all, yet i felt something was missing.
-URL Source (URL of the Original Content)
@julian I can probably do that. where can i find the full stack trace?
what ever that is shown on the ./nodebb dev console window?
I am also looking to transfer my db from redis to mongoDB.
For private groups, how to set the "owner" of that group?
I have created a test user, and "applied" for access to a private group.
I see the "Invtation Pending" button for that test user.
But, with my main account (admin), i did not see any notifications nor places to approve the user. Where is the information supposed to be?
@charles said:
@trevor said:
@Tanner said:
I had to remove the plugin because of the duplicate post issue.
Just thought of a good idea for core integration; Duplicate post checking.
+1 for duplicate check
+2 for duplicate checks
@julian not working yet.. haha.. let me play around it further. its a good step forward that i managed to associate the account already.
@Ted most of the time?!
@julian
From pushbullet:
From my forums:
@Ted @julian managed to get associated, but i am not receiving any notifications via pushbullet. Are there any conditions that needs to be fulfilled?
@julian swapped and restarted
the oauth test url from pushbullet. not too sure if you can access it here.
https://www.pushbullet.com/authorize?client_id=Wyna2jTkLbp5mOmcvxDPtMiFzfMkxrtV&redirect_uri=https%3A%2F%2Fwww.gameredge.org%2Fpushbullet%2Fauth&response_type=token&scope=everything
Running the latest 0.5.3 and pushbullet plugin, still encountering
`2014-10-31T08:52:58.126Z - warn: Route requested but not found: /api/pushbullet/auth
Glad to hear that. Its a very minor issue, with no functional impact to the usability of nodebb. Just wanted to flag it out to you guys in case it is missed on version 1.0 release