Le problème est résolu, merci
The problem is solved, thank you
Guys, any solution.. this is major bug,
cannot manage categories
cant manage user
cant upload logo / branding
cant add group
Please, my development halted due to this bug.
Please update to the latest code -- this should be resolved.
I already on latest i think - v.0.6.1-dev
any other recent than this? cant found any after run ./nodebb upgrade
Did you run
git pull first to get the latest code?
./nodebb upgrade only updates dependencies and database migration
i run this by step,
ls -d node_modules/nodebb* | xargs -n1 basename | xargs npm update
node app --upgrade
however im still on version v.0.6.1-dev
is my installation corrupt?
Guys, the version not change,
however after step above,
i press ctrl+f5 on chrome, no more black layer,
thanks guys, real help.
@Fuad-Othman CTRL-F5 causes the browser to refresh the external resource files (CSS and JS files, usually) and clearing the cache would have done the same thing for you.
I have had several weird post-upgrade issues with things like this and a force refresh or cache dump usually fixes it.
@julian I understand that being pre-release means the release schedule is accelerated and that's the major cause of these things, so this is surely a low priority, but at some point it might be prudent to add version numbers to the CSS/JS files to prevent these browser cache issues.
@Shaun Production mode should manage cache busters, but they're not present in devlopment mode... perhaps we're missing headers that instruct the browser to not cache assets...
Regarding the workaround on chrome developer tools, can you explain its step by step?
For the purposes of posterity ... if you press F12 in most browsers, you can inspect and manipulate the elements of a page. In this case, if you hit F12 and found the DIV tag with the modal-backdrop CSS class, it has a CSS property called z-index, which controls the layer position of the element. The basic problem here is that both the backdrop and the modal window have z-index values of 1040, which leaves it up to your browser to decide which one is actually in front of the other (I would think in this circumstance, the later element on the page should be treated as "in front" but that's not what's happening), so you can manually manipulate the z-index value to make the page function in your browser. And after confirming that that's the problem, obviously, you can make the changes permanent in the CSS files or whatever.
I did try your custom css workaround, but this bug still persist.
The custom CSS I posted in that other thread would fix the issue on the main forum, but I don't think that the admin panel loads that CSS, so I didn't expect it would fix your problem directly (but you could modify the CSS file for the admin panel).
@julian I don't think I'm running in development mode. You have to start it in development mode specifically, right? I'm just running
nodebb start as advised by the Ubuntu docs. I recall using a different command to put it in development mode to troubleshoot something once. I tell my users to hit CTRL-F5 every time I do an upgrade, because there are usually some oddities if they don't.
Bug on administration panel now clear already, however it keep happening on thread management,
its also happen in this thread when i try(test) to delete it too.
still got black layer blocking mouse input.
Opening the modal popup for the emoji or polling on this thread does it as well. The extended emoji is grayed out, but you can escape out of it, unlike the emoji/polling modals.
I am having this happen on things like uploading avatars and deleting or moving threads. I tried posting this in the custom cc and it didn't work:
Thanks. @pichalite Just curious what does it mean when its closed but not fixed?
@pichalite Thanks for the answer. Is there any temp get around for this? Kinda of immobilizes my forum.
I changed the z index to 0, seems to temp fix the problem, at least temporally. Pasted the following in the custom CSS;