Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

imgur image upload fail - nodebb V1.1.2 , redactor V1.4.2 , imgur V1.0.16

General Discussion

2064

C
cryptocentral last edited by

giving internal server error : [[error:no-privileges]]
1 Reply Last reply
Reply Quote 0
JasperNL Gamers last edited by

Is your API key correct?
C 1 Reply Last reply
Reply Quote 0
C
chrismccoy last edited by

also check the new category permissions, they recently added image and file uploads as a permission
1 Reply Last reply
Reply Quote 0
C
cryptocentral @JasperNL last edited by

@JasperNL said in imgur image upload fail - nodebb V1.1.2 , redactor V1.4.2 , imgur V1.0.16:

Is your API key correct?

yes api is correct , default composer upload works.
1 Reply Last reply
Reply Quote 1
C
cryptocentral last edited by

any other solution guys...
1 Reply Last reply
Reply Quote 0
Timothy Fike Community Rep last edited by

Please try the updated version 1.4.3 and let me know if it works for you.
1 Reply Last reply
Reply Quote 1
C
cryptocentral last edited by

thanks @yariplus , it works now...
1 Reply Last reply
Reply Quote 0

Suggested Topics

Custom Theme broken as result of upgrade from 1.5.3 to 1.7.3
General Discussion • • Gus Surarez

1

0
Votes

1
Posts

683
Views

I work on nodebb 1.5.3 and accidentally made the grave mistake of installing a plugin using ACP and ended up losing all my development repos of non 'npm'ed plugins. At that point I decided to upgrade to latest 1.7.3 release since a fix (#6032) for this issue was supposed to be committed into that build. While I checked breaking change lists for 1.6.0 and 1.7.0, apparently I have over looked something since my list/grid topic-list show up all messed up (with no errors in console). I have a bootstrap based listview and gridview of the topics and I use JS code to select between them but now my page layout is gone like one of the libraries is not loading but I am not sure which one since I don't use anything other than jquery and bootstrap.I cannot figure this out but suspect it may be issue (#5980.) Any help would be appreciated and thank you in advance.

Edit:

I get the following error intermittently after several clicks and I am hoping to be related:

Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
Script execution timed out.
at ContextifyScript.Script.runInContext (vm.js:53:29)
at ContextifyScript.Script.runInNewContext (vm.js:59:15)
at Object.runInNewContext (vm.js:112:38)
at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
at tryToString (fs.js:513:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
Script execution timed out.
at ContextifyScript.Script.runInContext (vm.js:53:29)
at ContextifyScript.Script.runInNewContext (vm.js:59:15)
at Object.runInNewContext (vm.js:112:38)
at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
at tryToString (fs.js:513:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
2017-12-31T06:55:43.950Z [1840] - error: /category/14/news
Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
Script execution timed out.
at ContextifyScript.Script.runInContext (vm.js:53:29)
at ContextifyScript.Script.runInNewContext (vm.js:59:15)
at Object.runInNewContext (vm.js:112:38)
at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
at tryToString (fs.js:513:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
Script execution timed out.
at ContextifyScript.Script.runInContext (vm.js:53:29)
at ContextifyScript.Script.runInNewContext (vm.js:59:15)
at Object.runInNewContext (vm.js:112:38)
at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
at tryToString (fs.js:513:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
2017-12-31T06:55:49.005Z [1840] - error: /category/14/news
Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
Script execution timed out.
at ContextifyScript.Script.runInContext (vm.js:53:29)
at ContextifyScript.Script.runInNewContext (vm.js:59:15)
at Object.runInNewContext (vm.js:112:38)
at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
at tryToString (fs.js:513:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
Script execution timed out.
at ContextifyScript.Script.runInContext (vm.js:53:29)
at ContextifyScript.Script.runInNewContext (vm.js:59:15)
at Object.runInNewContext (vm.js:112:38)
at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
at tryToString (fs.js:513:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)

...
some more errors I get after refreshes:

2017-12-31T07:42:50.130Z [13716] - error: /category/5/general
Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\category.js:
Script execution timed out.
at ContextifyScript.Script.runInContext (vm.js:53:29)
at ContextifyScript.Script.runInNewContext (vm.js:59:15)
at Object.runInNewContext (vm.js:112:38)
at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
at tryToString (fs.js:513:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
Error: Parsing failed for template D:\NodeBB-1.7.3\build\public\templates\500.js:
Script execution timed out.
at ContextifyScript.Script.runInContext (vm.js:53:29)
at ContextifyScript.Script.runInNewContext (vm.js:59:15)
at Object.runInNewContext (vm.js:112:38)
at evaluate (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\evaluate.js:17:6)
at fs.readFile (D:\NodeBB-1.7.3\node_modules\benchpressjs\build\lib\express.js:39:53)
at D:\NodeBB-1.7.3\node_modules\graceful-fs\graceful-fs.js:78:16
at tryToString (fs.js:513:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:501:12)
H

Upload Image Times: Server response parsing error
General Discussion • • hahafei

2

0
Votes

2
Posts

50
Views

Can you please share the server-side error? This client-side error is not something we can use, unfortunately.
Upgrading from 0.6 to 0.7
General Discussion • • exodo

4

0
Votes

4
Posts

1127
Views

A

You would have to shut from stable to master. Master isn't advised to be used in production, but for testing is fine.

To change branches you would type

git checkout master
git pull
./NodeBB upgrade
npm up

You may need to disable incompatible plugins if their are any.
UNSOLVED Sounds plugin disabled when upgrade to 1.15.x?
General Discussion • • Normando

1

0
Votes

1
Posts

36
Views

Hello.

I was upgraded nodeBB from 1.14.3 to 1.15.4 and see this when upgrading. Is this for some reason and can I enabled again, or it is incompatible with new nodeBB version?

Thanks!

4faf5501-9715-421f-847f-0162f4bd2cac-image.png
Latest stable v1.4.6
General Discussion • • Mikael Jenkler

9

0
Votes

9
Posts

1873
Views

Ok, so 1.5.x branch is stable to use. Is 1.x.x maintained for bugfixes only or just for history sake?

| |

1 / 1

imgur image upload fail - nodebb V1.1.2 , redactor V1.4.2 , imgur V1.0.16

Suggested Topics

Custom Theme broken as result of upgrade from 1.5.3 to 1.7.3 General Discussion • • Gus Surarez

Upload Image Times: Server response parsing error General Discussion • • hahafei

Upgrading from 0.6 to 0.7 General Discussion • • exodo

UNSOLVED Sounds plugin disabled when upgrade to 1.15.x? General Discussion • • Normando

Latest stable v1.4.6 General Discussion • • Mikael Jenkler

Custom Theme broken as result of upgrade from 1.5.3 to 1.7.3
General Discussion • • Gus Surarez

Upload Image Times: Server response parsing error
General Discussion • • hahafei

Upgrading from 0.6 to 0.7
General Discussion • • exodo

UNSOLVED Sounds plugin disabled when upgrade to 1.15.x?
General Discussion • • Normando

Latest stable v1.4.6
General Discussion • • Mikael Jenkler