Profile picture cropping modal issue

Readerly

Hey @PitaJ,

I think I found another absolute symlink:

readlink /build/public/plugins/nodebb-plugin-markdown/styles

gives:

/Users/seanmiller/Documents/nodebb/NodeBB/node_modules/nodebb-plugin-markdown/public/styles

In that same directory, readlink js yields:

/Users/seanmiller/Documents/nodebb/NodeBB/node_modules/nodebb-plugin-markdown/public/js

It may be that all the symlinks are absolute in this build.

Missing a railscasts.css causes this:

404 Not Found
Route Count
/plugins/nodebb-plugin-markdown/styles/railscasts.css 59

PitaJ

Yep those should be fixed as well

Readerly

Hi @PitaJ

I replaced those absolute folder symlinks in the plugins directories with the actual folders and their contents. I'm still getting these errors in my console logs when I load pages, though:

404 Not Found
Route Count
/plugins/nodebb-plugin-markdown/styles/railscasts.css 96
/assets/uploads/profile/1-profileavatar.png 9

The odd thing is that it's only happening in Chrome, not Firefox:

forum.driversbydesign.com/:35 GET http://forum.driversbydesign.com/plugins/nodebb-plugin-markdown/styles/railscasts.css net::ERR_ABORTED
(index):322 GET http://forum.driversbydesign.com/assets/uploads/profile/1-profileavatar.png 404 (Not Found)

PitaJ

Try clearing your cache.

Readerly

Do you mean the browser cache?

Did that. Now both Firefox and Chrome are spitting out the following errors in the console log:

Firefox:
GET http://forum.driversbydesign.com/plugins/nodebb-plugin-markdown/styles/railscasts.css [HTTP/1.1 404 Not Found 92ms]

Chrome:
Failed to load resource: the server responded /plugins/nodebb-plugin-markdown/styles/railscasts.css
1-profileavatar.png Failed to load resource: the server responded with a status of 404 (Not Found)
railscasts.css Failed to load resource: the server responded with a status of 404 (Not Found)

Readerly

Hi @PitaJ,

I'm still having an issue with NodeBB not being about to find a profile picture I set up on my (admin) profile. It happens on Firefox or Chrome. It's hard to discern a pattern--why some actions cause the browser not to be able to load the image, while the other still can.

Any other suggestions?

Sean