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
DavidF2 et al,
Update on MS's Publisher 2013 Edit Wrap Points Hotfix:
6/7/13: After testing the MS Publisher 2013 Edit Wrap Points Hotfix (http://support.microsoft.com/kb/2760285) myself and finding it didn't work, I called Microsoft and received level 2 tech support who also received instruction from level 3 tech support to work on the problem. The techs found the published hotfix didn't work for them either and reported their findings to the developers/programmers. I was assured that it will be addressed and that I would receive word at some point (no estimated time) about resolution. (Although I frequently use Photoshop to doctor images, it's very inconvenient to lose this function in Publisher 2013. Creates more work not to have it functioning.)
I believe it would help tremendously if more users would call in about it and go on record as reporting the Edit Wrap Points and Edit Points malfunction to level 2 support or speak with a supervisor (800-642-7676). I don't recommend raising the issue to level 1 support who simply advised me that function has been discontinued. Also reporting it as a MS Product Bug, as DavidF2 recommends, would help as well.
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.
Thanks so much for posting this information. Please post again after you have tested it and share your results.
DavidF
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.