Skip to main content
Adobe Photoshop Family

2 Messages

 • 

212 Points

Tue, Jun 20, 2017 1:37 AM

8

Lightroom: Why isn't there a publish service for Adobe Portfolio?

I currently publish my photography on SmugMug because Adobe Portfolio does not have a Publish Service from Lightroom.  I can't understand why this is the case.  Nor can I understand how the response from Adobe is that Portfolio is synced to LR Mobile/online.  It only syncs the first time you share.  When I make edit changes to images published to Smugmug, they are re-publishable... not so via LR mobile/update... its a delete/share process which is not acceptable.  Please add at least a LR Adobe Portfolio Publish Service, as well as Adobe Behance... sorely missing!

Responses

Accepted Solution

Adobe Administrator

 • 

14.9K Messages

 • 

286.1K Points

3 years ago

Sr. Product Manager, Adobe Digital Imaging

17 Messages

 • 

506 Points

I think Gary already knew about the Lightroom mobile integration, he was very specific about his needs and the inconvenience of the current implementation.

"If you’re not aware of Adobe Portfolio – here is a short overview:  If you are a member of Creative Cloud or the Creative Cloud for Photography Program, Adobe Portfolio is included in your membership. Portfolio is a simple way to create a beautiful, personalized, website with galleries of images, specialty pages (such as About, Contact, Awards etc.), social media links, and more."

So why can't you publish pictures from Lightroom directly into Portfolio? What is the strategy here?

10 Messages

 • 

226 Points

Exactly... the answer was stock and not to my question... I know the LR Mobile "sync" process, and can invent others as the blog covers...

10 Messages

 • 

226 Points

Your answer is stock and not to my question... I know the LR Mobile "sync" process, and can invent others as the blog covers...  why in the world would you offer the power of Publish Services, and then not offer it to your CC Portfolio customers... some hidden agenda likely, and assumed until a real answer is offered...

1.3K Messages

 • 

22.5K Points

Publish Services is a rather old mechanism of providing a generic publishing platform. The "generic"  is important, because all types of third party services are able to write publish plugins that allow Lightroom to interact with their systems.

Portfolio comes from a different direction. It is a web-originated service and doesn't need anything from inside Lightroom. It could be used to display photos that have never been near LR Desktop - eg from people who only use LrMobile - or from non LR users who are Adobe CC customers. Portfolio just needs to connect to Adobe's server. So Publish Services are pretty irrelevant to it.

Yes, it is indeed  tedious that when an image changes in Lr or LrM, you need to go into Portfolio and replace it. That's fine for some users, not for others who continue to improve their pictures.

So your question should be recast as follows. Why can't Portfolio call the latest "live" versions of images from the Mobile server?

10 Messages

 • 

226 Points

I currently publish my photography on SmugMug, which is a web service that allows me to add and delete photos from LR, my computer, smartphone... where-ever.  I use the SmugMug LR Publishing Service plugin as my primary photo source for my SmugMug website, and it is a workflow thing of beauty.  It allows me to have the exact same file organization within LR and on SmugMug, and if I see something I want to change in an image once published, an edit to the photo in LR and a push of a Publish button in the SmugMug LR plugin and poof, its updated on my website.  Call it an old mechanism, but compared to whats available for Portfolio and its light years ahead.  You might say, stick with SmugMug then, and I will answer, until this is fixed, sure, I will! 

178 Messages

 • 

3.7K Points

3 years ago

I'm every once and a while trying to update my Adobe Portfolio page but it's a pain as the interface for LR Web is so slow.

To be able have some hierarchy for photos inside Projects I find Grids useful but to add photos to a Grid makes the LR Web interface load separately every time and waiting for the photos to show up takes just too long.

It makes the whole workflow a pain.

So, I wouldn't mind Publish to Adobe Portfolio as some kind of middle man to have those photos somehow more quickly and conveniently available. I realise Publish to a Grid inside a Adobe Portfolio Project so I understand Publish may not be the flexible way going forward, but something has to change. Opening the LR Web interface, choosing a Collection and getting photos to show up takes too much time (as in minutes), and when you do it several times it gets frustrating.

Keeping Adobe Portfolio site up to date is a pain.

EDIT, ADDITION: Even if you quickly select a Collection that has only a few photos in it, it takes too much time to load those few photos.

1 Message

 • 

80 Points

3 years ago

The point trying to be made is that in order to "update" a gallery in Portfolio, one must delete the gallery first, then resync the newer version of it to LRM THEN re-import into Portfolio. The galleries are not kept up to date by any synchronization; the sync is happening between LR and LRM, but not between AP and LRM. Hence the breakdown in workflow effeciency.

Whereas, if Portfolio was fed by a publish service that tracks/creates galleries, etc, and tracks changes to images, thereby prompting to republish only the changed images, the entire process becomes more streamlined.

1.3K Messages

 • 

22.5K Points

I'd be amazed if Adobe implemented a publish service for this (as explained above).

But are you aware of recent changes to this aspect of Portfolio? Collections are now linked, and within Portfolio's edit view you can now  update the contents quite easily - it's much less manual. See this post Introducing Portfolio’s New Integration With Adobe Lightroom.

1 Message

 • 

62 Points

I did see this new feature in Portfolio, and it's one step closer, which means they are on the right path.  Ran into a bug though trying to use it, so not committing yet.