[Solved] Avatar's refuse to resize.



  • Whenever I upload an avatar on my forum It zooms it in, depending on how large the image is (I believe)
    I'm trying to upload the avatar I currently have set on here, and this is the outcome

    1

    I have had this avatar set before and it worked fine (was using 0.4.1 at the time), multiple people have been having this problem on my forum, yet I've no idea why it's doing this.


  • Admin

    Can you provide a link to the original image so we can test. I think @julian changed something in the resizing recently maybe that is causing it.


  • Admin

    Yeah, I recently updated the upload code so that the image itself is resized down (or up!) to the requisite 128x128, maintaining aspect ratio, before cropping if necessary.

    In your case, it may just be a matter of updating the core code, and it should be fixed.



  • Image: http://ns3369178.ovh.net/lbp_ezio_face.jpg

    What do you mean by "updating the core code"?
    I'm currently using the direct version, so I assume I'd just upload the files and run nodebb update? hence, how I upgraded from 0.4.1 to 0.4.2.


  • Admin

    @Dazzuh Oh, you use the tarballs located on this page?

    Good news, we just released v0.4.3, so you can just drop in the updated code, and run ./nodebb upgrade :)



  • @julian said:

    @Dazzuh Oh, you use the tarballs located on this page?

    Good news, we just released v0.4.3, so you can just drop in the updated code, and run ./nodebb upgrade :)

    Updated, fixed the avatar problem but multiple new problems have arisen.

    I'm having a similar problem to this (Although, I'm using redis)

    at first I was logged in with the "register / login" text showing at the top right, so I figured I'd try logging out and back in, Logged out now I can't log back in, it stops at "logging in.." which is there the page would usually refresh and I'd logged in, though this time it does nothing.
    So I figured I'd restart nodebb, no luck, ran npm update and tried launching again, still nothing.

    Also the forums show like this when you hard refresh it, clicking the logo at the top left temporarily fixes this, though that's a problem for another time, I've fixed that before.


  • Admin

    @Dazzuh please run the following commands:

    $ npm install nodebb-theme-vanilla@latest
    $ npm install nodebb-theme-lavender@latest
    

    No clue why, but npm seems to be serving stale versions of vanilla and lavender for no reason at all...

    Our package.json shows this: "nodebb-theme-vanilla": "~0.0.19", "nodebb-theme-lavender": "~0.0.25", which is fine...



  • @julian said:

    @Dazzuh please run the following commands:

    $ npm install nodebb-theme-vanilla@latest
    $ npm install nodebb-theme-lavender@latest
    

    No clue why, but npm seems to be serving stale versions of vanilla and lavender for no reason at all...

    Our package.json shows this: "nodebb-theme-vanilla": "~0.0.19", "nodebb-theme-lavender": "~0.0.25", which is fine...

    Doesn't seem to have changed anything at all, even after a restart.

    edit:
    Nevermind, running those commands without @latest fixed the theme issue however login issue is still there.


  • Admin

    Clear cache? Please let me know what errors show up in web inspector/console.



  • @julian said:

    Clear cache? Please let me know what errors show up in web inspector/console.

    node_redis: no callback to send error: Error: ERR unknown command 'pexpire'
    Error: Error: ERR unknown command 'pexpire'
    at HiredisReplyParser.<anonymous> (/var/www/gdt/nbb/nodebb/node_modules/redis/index.js:263:27)
    at HiredisReplyParser.EventEmitter.emit (events.js:95:17)
    at HiredisReplyParser.execute (/var/www/gdt/nbb/nodebb/node_modules/redis/lib/parser/hiredis.js:41:18)
    at RedisClient.on_data (/var/www/gdt/nbb/nodebb/node_modules/redis/index.js:488:27)
    at Socket.<anonymous> (/var/www/gdt/nbb/nodebb/node_modules/redis/index.js:82:14)
    at Socket.EventEmitter.emit (events.js:95:17)
    at Socket.<anonymous> (stream_readable.js:745:14)
    at Socket.EventEmitter.emit (events.js:92:17)
    at emitReadable
    (_stream_readable.js:407:10)
    at emitReadable (_stream_readable.js:403:5)
    info: [app] Shutdown (SIGTERM/SIGINT) Initialised.
    info: [app] Database connection closed.
    info: [app] Shutdown complete.

    Restarts after that.


  • Admin

    You need to update redis to 2.6.0 at least.



  • @baris said:

    You need to update redis to 2.6.0 at least.

    Sorry, but I have no idea when it comes to redis.
    I've downloaded redis from redis.io, buut using that loads a different database for nodebb (I assume? all categories and users are gone when I use it)
    Any idea how I can update and use the same database? orr, transfer it, at least. I'm probably asking a bit much now but as I said I am pretty new to using redis.
    using linux, ubuntu 12.04, using apt-get install redis and it's supposedly on the latest version, though I know how allot of stuff can be outdated on ubuntu's default sources.


  • Admin

    Redis files are usualy in /var/lib/redis you can backup those *.rdb files and then install a recent version on redis.


  • Admin

    @Dazzuh If you're running a flavour of Linux, best bet is to install using their package manager... Ubuntu? CentOS?



  • @julian said:

    @Dazzuh If you're running a flavour of Linux, best bet is to install using their package manager... Ubuntu? CentOS?

    oh I tried, according to ubuntu package manager I was already up to date.
    Already figured it out though. Thanks for your help.


Log in to reply
 


Looks like your connection to NodeBB was lost, please wait while we try to reconnect.