This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Other than cropping, I was able to use edit wrap points to edit pictures to get just a portion of the object. How does this work in Publisher 2013?
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Unless the freehand shape is an option, the function has not evolved well. **In previous versions, the portion of the image outside of the wrap points was not visible.**This is a function I use daily and will have to find an alternative now.
In addition to JimenezOlga's answer the cropping function in Pub 2013 has evolved.
Reference: Crop a picture to a shape: http://office.microsoft.com/en-us/publisher-help/crop-a-picture-to-a-shape-HA102919810.aspx?CTT=1
DavidF
My case has resulted in the problem being dropped into the MS developers' work queue, and they triage. Because of this, I can't stress enough to EVERYONE having this problem with Publisher 2013 the importance of calling in and going on record to report the problem as a bug. Even if your Publisher 2013 is out of warrantee for free support, you still won't be charged for reporting it as a bug. The important thing is to try and get a Case Number for your report and don't let them close the Case Number (leave it open until the issue is resolved). Also when I called, I had to try and get level 2 support b/c level 1 simply told me it doesn't work anymore and tried to get me off the phone. I called back and then spoke with level 2 tech who spent a great deal of time working with level 3 support testing the hotfix and determining it doesn't work for MS either. At this point, they reported it to the developers in a meeting they had that day and also sent background details and videos to them. But, as I said, it's in the developers' queue and they triage.
The support number for reporting the Edit Wrap Points and Edit Points malfunction in Publisher 2013 is 800-642-7676. Ask for a supervisor if you need to. Thanks everyone!
After having tech support today (June 5, 2013) flatly tell me the function was discontinued, I did some more sleuthing and discovered this MS "HotFix" for edit wrap problem on the microsoft.com site. It was released by MS on February 12, 2013.
I haven't downloaded or tested it yet. It can be found at http://support.microsoft.com/kb/2760285
Hoping it works -- like so many others, it's critical that I have this function.
If the hotfix doesn't work, fortunately, I did a custom install for 2013 so it wouldn't overwrite my 2010 version of publisher so have both available. If I need to, I'll edit wrap points in 2010 and transfer them over to 2013 and hope that it transfers over correctly.
As above, it's important to report bug, however, to make sure this problem is fully addressed.
I thankfully only installed 2013 on one of our machines (mine); we still have 2007 on the others. Our organization was on the verge of a major print job, the formatting of which was completely destroyed by this bug. I spent a day panicked, thinking I'd messed something up...glad to see it's not just me.
We are having the same issue with Publisher 2013 and the edit warp points for pictures. This is also a feature we use all of the time. I down loaded the hot fix which did nothing to correct the issue, which is also frustrating. Also find that publisher moves extremely slow compared to 2003, starting to regret upgrading. Miss the old way of puzzling pieces together too. Please keep me in the loop as to when this issue is corrected.