Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted March 14Mar 14 In version 4.7 I had a limit to video width and picture width and it respected my settings. On desktop it seems to go full width even with smaller resolution settings on v5. I'm guessing I'm missing a setting somewhere else. I'd love to be able to restrict the size so they aren't so giant in desktop mode.
March 14Mar 14 Author I am also having an issue where a user also has a picture in their signature even though I believe I have it set so that no one can use images in their signature.
March 16Mar 16 Community Expert You're pointing at the wrong setting there. Its the "Maximum embeded content width" item below it you would be looking at
March 16Mar 16 Author @Marc Thanks for the reply. I believe I had the right area shown in the first screenshot? Or am I missing another area entirely. Basically all embdeded content or images are rendering at full browser width no matter what settings I'm trying. Previous version 4.7 I didn't have this problem. I'm gonna try going through apps that I have installed and disabling and see if anything is conflicting with these settings. Same apps I used in 4.7, but maybe an update on one of them causes this. I'll report back IF one of the apps was the problem. Otherwise, I'll still be looking for the fix.
March 16Mar 16 Author Alright, I've just reduced the image sizes even more and I got it to not render huge. However I'm still have a problem with youtube videos. As shown below, I'd like this video to not be full width of the post.
March 16Mar 16 Community Expert you resize the video by pulling the corner up to the size you want in the post.
March 17Mar 17 Author Thank you for that, I had a way to auto resize these on 4.7 Not sure if it was an app doing it, I can't rely on forum goers to resize stuff, if anything someone would probably make it bigger lol.
March 17Mar 17 Community Expert Solution Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.