Images pasted to Wiki cannot be enlarged

[Tarek Faham]

When pasting an image into Wiki, it works, but if the image is a screenshot, there is no way to see the image clearly since it is scaled down. I hope you can add a way to zoom into the Wiki or enlarge the pasted images.

Tarek

[#2]

I have just pasted a screenshot in a Wiki in Teams and I can resize it with no problems

[#3]

How did you resize? What is the exact version you are using?

Tarek

[#4]

I have this same issue. Were you ever able to resolve?

[#5]

I just tried now, and I noticed that a handle will appear on the image when you click on it. This allows you to expand the image. Also, you can zoom in/out by pressing ctrl and use the mouse wheel to control zoom level.

Tarek,

[#6]

The image resizer does not work for me either. Windows 10 desktop or Chrome browser

[#7]

Here is my version (Windows Desktop):

You have Microsoft Teams Version 1.1.00.25457 (64-bit). It was last updated on 9/26/18.

Check your version from Your Account (Picture) -> About -> Version.

[#8]

I'm having the same issue at the latest Team version here (Version 1.1.00.25457, 64 bits, 26/09/2018.). New images I paste into the wiki can't be resized, but older ones (pasted a few weeks ago) can be. Really strange and no clue on how to solve it.

[#9]

Unfortunately although I see the little handle, it doesn't seem to do anything. I'm on Mac OS 10.13.6 on and have tried it both in chrome Version 69.0.3497.100 and in the Mac desktop application Version 1.1.00.26352.

[#10]

Same thing here. I'm facing the issue on Edge and on the Windows app.

[#11]

Actually, you guys are right !!! When I paste new image, there is no way to change its size. The size handle will show, but it will not work.

The old images can be resized.

I will try to paste new image, and check in few days to see if it will work. Maybe it takes time to be ready for resizing.

Tarek

[#12]

I've waited more than one hour and still nothing. If I look at the Wiki folder in SharePoint, all the pasted images are there with original resolution, so it's certainly something in the interface, as they are being uploaded fine. 

[#13]

I am having the same issue with the Wiki images. It is completely worthless to put tutorials in my Wiki if the images are tiny and a user can't read them. How do we get this fixed asap.

[#14]

Another issue appeared as I was fiddling with this matter, is that the WiKi item will get locked, and then you have to force unlock. The strange thing is that there is no way you can lock WiKi item manually.... it gets locked as part of a bug or issue.

[#15]

Is this discussion enough to inform Microsoft about the potential bug? I continue working with a few wikis here assuming it'll be fixed someday, but if not... I need to change strategy. Anyone from Microsoft here?

Regards. 

[#16]

I'm seeing this issue too. One of the sections on a page I created is locked...by me... and I cannot access or unlock it despite the fact that it says I'm the one working on it.

[#17]

In case they want to fix, better provide desired behaviour.

As a WiKi user/author, when pasting an image, allow the image to show as a thumbnail, then when you click on the image, it will expand/zoom to show in full resolution. Also, allow zooming in/out.

If you anyone has feedback, please suggest modification.

Tarek

[#18]

Being able to click and see the actual size of the image is great, but the functionality that's broken here is more basic than that. The wiki is auto-resizing images on its own and will not allow the manual resizing of that displayed image or thumbnail even if there is available space within the wiki page. I would like to be able to manually resize those images to use all available width before there's a need to click and enlarge.

[#19]

I agree with you Danielle. Writing it down as an user story or something would be great had we been talking about a new feature, but this is a bug. I can confirm that three or four weeks ago we could resize pictures in Teams wiki. Indeed, images pasted before the bug can still be resized. So, unless this is a feature change (which I doubt), we should consider it a bug. Regards. 

[#20]

I suggest to specify the requirements, and let them implement accordingly. Weather it's a bug or missing feature, the bottom line is that it's not meeting our needs.

[#21]

Sure mate. I've got your point. I would just avoid ADDING requirements because a bug would (should) probably be corrected first. So my user story would be: "as a wiki user in Teams, I would like to be able to resize pasted images (again)". :) Sheers.

[#22]

I'm experiencing the same behavior, absolutely kills the Wiki for us.

[#23]

Teams app just updated and the issue remains.

Currently Microsoft Teams Version 1.1.00.29068 (64 bit). It was last updated on 06/11/2018.

Regards. 

[#24]

Copy an old picture that can be resized and paste as a new image and it can NO LONGER be resized. Microsoft Teams 1.1.00.28562 and Teams Online O356

[#25]

Same issues :( Although glad its not just me, while doing a google search I found a few hints and tips which didn't work, assuming that's because of the update and not me. Although this really does raise an issue for my Team as we are creating a PowerBi team and were going to use wiki's for publishing schema's and database architecture which have some large images that cant be seen very clearly :(

[#26]

I seem to have the same issue, new content cannot be added until the image resize issue is fixed. It is pointless not able to see full sized images. Hope this issue can be fixed soon, using Teams both in chrome and as an app on windows 10.

Workaround until this is fixed: Right click on the image and open in new tab in chrome, this seems to show the full size image in a new tab, atleast I can see the image for now.

[#27]

Same issue here. When I first started using Teams, I could resize the image. 

But now I can not resize.

I've tried both copy/pasting the image into WIKI and also inserting the image using the "image" icon.

Help!

[#28]

Same here...

I convinced my organization move to teams and now we begin transferring instructions, handbooks and other documentation to Teams WiKi pages. With small images, schemas and etc. it totally worthless... Now I don't know what to say to my users. Any plans to fix this issue?

[#29]

I just got to this thread searching on how to resize images. As it seems that no-one at Microsoft is paying attention to this thread, you should vote here, if you haven't already done so (they at least seems to check UserVoice from time to time):

https://microsoftteams.uservoice.com/forums/555103-public/suggestions/18666934-change-picture-size-i...

[#30]

Looks like it's fixed! My desktop version is 1.1.00.31860 updated 12/6/2018 and my wiki images can be resized again. Yay!

[#31]

Still can't :(

1.1.00.31860 updated 12/7/2018

Hope it will begin to work...

(Or I can't figure out how it works. Just click and drag low right image corner? Or double click?)

[#32]

That should work how odd. When I hover over the image there’s a blue outline with a blue corner bottom righ. Click that corner to drag. This is the desktop app Win10 for me, not a browser

[#33]

Ok, finally I can confirm that's it is working!
Needed to remove and add images once again and now it can be resized.

[#34]

I am curious, why to use Wiki-functionality for this? I usually use& recommend using OneNote and building a wiki with that. 

OneNote: syncs to different devices (available offline), you have a working version history, there is a file to move around if needed, excellent and free form canvas to use, desktop & online apps, included in the search.

Wiki: fast to use inside Teams. No working version history. No recovery option (if you delete wiki from Team you don't get it back), not available offline, files accessable only via Teams, no way to move Wiki to another team for example. So far the only + side (fast use) did not make the cut for me.

[#35]

@Vesa Nopanen We have some old Teams that use Onenote and most new ones that use the Wiki functionality. We basically used them to store quick notes and instructions, related to the Team, that are rarely edited but frequently accessed.

It is true that Wikis are currently quite limited (you have revision history through the Sharepoint they are stored in, though) but, for frequently accessed info, the speed is (at least for us) a huge difference, specially if you only use them within teams, where you cannot "pin" a tab open, and sometimes you might have to keep jumping between the Wiki tab and a different channel tab.

[#36]

In my experience Wiki's SharePoint history has some issues (it was easily overwritten if somebody has the wiki open while previous version was restored).

I was curious about the use cases, since I am very willing to give Wikis a good chance and choose the best tool depending on scenario.

You can "pin" a specific Onenote page to tab (use page url) but the speed is not the best if you keep on jumping between tabs (yeah, slow). Usually I try to use alternative myself: keep OneNote open in the OneNote app and access it's information from there. Not a "one UI" approach but using tools what Office 365 provides in a best way for me. This always depends on scenarios and people.

[#37]

Hi Vesa Nopanen, thanks for tips and insights!

Looking for a knowledge base (handbooks, instructions and etc.) solution for our organization. And just playing around with WiKi Teams / WiKi SharePoint / OneNote. Previous experience was with Jira Confluence pages.

Hope to handle to get the best of 365 possibilities for that.

[#38]

Create a proof of concepts / pilot solutions with each of possibilities (OneNote, Teams Wiki, Modern SharePoint Pages) and see what suits your needs the best. List scenarios/use cases how and where you would use wiki and trial these out.

I would not rule out Modern SharePoint Pages either, since they are really versatile and can be added as tabs (online use only of course).