warning in log x from '\' is deprecated

[teh_g]

@PitaJ said in warning in log x from '\' is deprecated:

@teh_g can you inspect the response headers to see if X-Powered-By: NodeBB is there? If you made the changes to nginx, then those warnings should not be showing, unless the issue is that your theme uses the old paths.

I see the X-Powered-By: NodeBB. Here is the response I get when going to my site (gamingexodus.com

access-control-allow-origin:null
cf-ray:344ade7fed9c7c28-LAX
content-encoding:gzip
content-security-policy:default-src 'self'; connect-src 'self' wss: https://api.github.com https://packages.nodebb.org https://bootswatch.com; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://iframely.gamingexodus.com https://storage.googleapis.com https://checkout.stripe.com https://s.imgur.com https://www.google.com https://www.gstatic.com; img-src 'self' data: https:; style-src 'self' 'unsafe-inline' https://maxcdn.bootstrapcdn.com https://fonts.googleapis.com; font-src 'self' https://maxcdn.bootstrapcdn.com https://fonts.gstatic.com; child-src https:; object-src 'none'
content-type:text/html; charset=utf-8
date:Fri, 24 Mar 2017 16:04:57 GMT
server:cloudflare-nginx
status:200
strict-transport-security:max-age=15552000; includeSubDomains; preload
vary:Accept-Encoding
x-content-type-options:nosniff
x-frame-options:SAMEORIGIN
x-powered-by:NodeBB
x-xss-protection:1; mode=block

I am using the Persona theme, so I'd imagine it is using the right paths

Here is my location blocks from my nginx config

        location @nodebb {
                proxy_pass http://127.0.0.1:4567;
        }
        location ~ ^/assets/(.*) {
                root /var/www/nodebb/forums/;
                try_files /build/public/$1 /public/$1 @nodebb;
        }
        location /plugins/ {
                root /var/www/nodebb/forums/build/public/;
                try_files $uri @nodebb;
        }
        location / {
                proxy_pass http://127.0.0.1:4567;
        }

[julian]

Is it Persona or a fork of Persona? Maybe you need to pull latest Persona in

[teh_g]

@julian said in warning in log x from '\' is deprecated:

Is it Persona or a fork of Persona? Maybe you need to pull latest Persona in

It is just regular old Persona.

nodebb-theme-persona
Persona theme for NodeBB

Installed 4.2.6 | Latest 4.2.6

[teh_g]

Has anyone else seen this error?

Any other info I can provide @julian to narrow this down?

[PitaJ]

@teh_g is that log for a single request? If not, can you run ./nodebb dev and make a single request? Can you reproduce anywhere else? Is this in a public facing website I can look at? Have you tried ./nodebb build?

[teh_g]

@PitaJ said in warning in log x from '\' is deprecated:

@teh_g is that log for a single request? If not, can you run ./nodebb dev and make a single request? Can you reproduce anywhere else? Is this in a public facing website I can look at? Have you tried ./nodebb build?

Unfortunately the log is just from my production instance at https://gamingexodus.com. I haven't narrowed down a specific request that causes the warnings.

I did a ./nodebb build and am running in dev mode now. I did some basic clicking around, and I do not see anything coming up in the log yet. The warnings did not happen too often though, so I kind of expect it to not be on every click.

[teh_g]

@PitaJ

I can't tell if my clicking did this, or if it was someone else on my site. I noticed this warning right after I clicked the https://gamingexodus.com/groups link:
27/3 12:33:03 [6371] - warn: [deprecated] Accessing `images/cover-default.png` from `/` is deprecated. Use `/assets/images/cover-default.png` to access this file.

[rod]

With the Lavender theme I get these on my console:

27/3 06:04:01 [26017] - warn: [deprecated] Accessing `stylesheet.css` from `/` is deprecated. Use `/assets/stylesheet.css` to access this file.
27/3 06:04:02 [26017] - warn: [deprecated] Accessing `nodebb.min.js` from `/` is deprecated. Use `/assets/nodebb.min.js` to access this file.
27/3 06:04:06 [26017] - warn: [deprecated] Accessing `src/client/chats/recent.js` from `/` is deprecated. Use `/assets/src/client/chats/recent.js` to access this file.
27/3 06:04:07 [26017] - warn: [deprecated] Accessing `src/client/chats/search.js` from `/` is deprecated. Use `/assets/src/client/chats/search.js` to access this file.
27/3 06:04:08 [26017] - warn: [deprecated] Accessing `src/client/chats/messages.js` from `/` is deprecated. Use `/assets/src/client/chats/messages.js` to access this file.
27/3 06:04:08 [26017] - warn: [deprecated] Accessing `src/modules/scrollStop.js` from `/` is deprecated. Use `/assets/src/modules/scrollStop.js` to access this file.

[PitaJ]

@rod what version lavender? Latest is 4.0.0.

[PitaJ]

@teh_g ok, can you check user profile pages as well? And upgrade script should have updated that.

Regardless, these deprecation warnings are for developers, and can be safely ignored until NodeBB v2.0.0, which is still far out.

[rod]

@PitaJ My Lavender is 3.0.15 yet my ACP does not show an update for it:

[PitaJ]

@rod what version of NodeBB are you on? [email protected] is compatible with NodeBB 1.4.4+

[rod]

@PitaJ v1.4.4