I’ve had issues with publish via sftp and now it seems that I have an image that is corrupt. Is there a way to get Elements to just republish a single page, or better yet a single component, rather than republish the whole site?
Yes, Right Click on the page in the pages panel and click publish page. 
Nope. That doesn’t force it to republish the content. It thinks the image (which it broke) has already been published so it’s not pushing it again. All I get is newer index pages.
Maybe try a different image, publish that and then change the image back and publish that?
In this case I can remove the image from the page and put it back along with its caption but that’s not really the solution to this problem if the component is more complex.
I was just suggesting the workaround for you.
@dan I think this is a bug or feature that needs correcting? Maybe there needs to be the equivalent of Re-Publish All Files for a single page?
1 Like
That isn’t guaranteed to only publish one page in my experience but in anycase it still might not update the image that OP had an issue with?
That doesn’t fix my problem. Elements thinks it has successfully published an image on the page and there appears to be no way to force it to publish that image again (without removing it from the page and putting it back again). Re-Publish All Files would do the job except the project is image heavy and I don’t want it uploading all of the images again, especially when it stuffed up the image in question and could just do it again. Really I want a way to mark an element or resource as changed even though it hasn’t been to make Elements publish it again.
1 Like
Also there are a lot of index files, and the like, that publish wants to publish each time you hit the publish button and that is rather tedious.
1 Like
Did you try to connect to the server and replace the image directly inside /resources ?
No because I’m using a gallery and there are two broken images (one @400) so it’s not as simple as just grabbing the original image file and dropping it on the web server. Yes I could publish to a local directory and grab them from there but that’s not a real fix either for a system that should be more user friendly than that.
Point taken…and I can only agree !
Hi @mrp
you can go to your section with the faulty image, select it in the node browser and then right click and “Mark it as Changed”. Then it should re-publish the faulty one.
That doesn’t help as the problem is a resource (image in a gallery) and marking the page as changed only makes Elements republish the framework of the page and not the resources used by it.
Ok, thought this forces Elements to re-publish the whole page. Then you need a “harder” workaround 
Mark all the pages you do not want to re-publish to “not publish” like so
Then press “Re-Publish All Files”. That should force Elements to publish only the one not marked page to a complete renewal-
1 Like
I am concerned that that might republish all the images in resources and not just the ones associated with the page with the broken image.
Would that be a disaster? It would take time of course, but otherwise?
Maybe doing a backup with an FTP-Client first can be a good idea, if anything happens you are on the save side 
1 Like
Given how image heavy the web site is I doubt it is much different to a simple republish all files. The simple “solution” in this case is to just remove the image and put it back but the real generic solution is a mechanism to force a republish of a component.
I’m unclear here as to how the image got corrupted in the first place. That’s what I’d be worried most about.
If you fully understand the structure of your site and have a utility such as Transmit, it’s easy enough to replace a single resource file. But again, how it got corrupted is the worry here.