Select which photos are sent to the difference channels and our own website.

Status: Requested 18 Votes
Dean D
Apr 12, 2024 2:53 PM
Joined Feb, 2023 2 posts

Hello,

VRBO is complaining about some of our photos because they have QR codes embedded in them. Can you add a feature that allows us to omit some photos from certain channels so we don't have to remove them from everywhere?

Scott J
Apr 13, 2024 9:21 PM
Joined Mar, 2019 185 posts

Vrbo is being utterly overly paranoid and protective. They are flagging a photo of mine that says that everyone of all races, genders, orientation, etc are welcome. Totally insane.

Ken T
Apr 13, 2024 10:38 PM
Joined Aug, 2019 1707 posts

Yes, they don't allow any text in any photos, because someone had the bright idea to post the text of their direct-book website in a photo.

Scott J
Apr 13, 2024 10:51 PM
Joined Mar, 2019 185 posts

With the corporate buyout of Vrbo, the revenue model went to commission-only, thus the paranoia and protectionism.

Ken T
Apr 13, 2024 10:54 PM
Joined Aug, 2019 1707 posts

I cannot speak to that, except to say that attempting to evade Vrbo's commissions by inducing guests to find and book directly has been against their TOS for as long as they've been charging commissions, which is many years now.  So it's nothing at all new.

Dean D
Apr 14, 2024 6:26 AM
Joined Feb, 2023 2 posts

I cannot speak to that, except to say that attempting to evade Vrbo's commissions by inducing guests to find and book directly has been against their TOS for as long as they've been charging commissions, which is many years now.  So it's nothing at all new.

by Ken T – Apr 14, 2024 2:54 AM (UTC)

Hi Ken, 

One picture is a QR link to a store where guests can enhance their stay by purchasing products and/or services. That is not related to evading commissions. 

 

Ken T
Apr 15, 2024 10:10 AM
Joined Aug, 2019 1707 posts

Yes, and neither is the "Welcome to Las Vegas" sign.  Vrbo doesn't make any attempt to actually read the text or follow any links and suss out if they're a TOS violation or not - it simply disallows text entirely.

Scott J
Apr 15, 2024 1:44 PM
Joined Mar, 2019 185 posts

Hey thanks, Ken, for explaining all this to us. We understand that OwnerRez has nothing to do with it. I think you're just hearing our respective frustrations with Vrbo/Expedia about it.

Ken T
Apr 17, 2024 11:33 AM
Joined Aug, 2019 1707 posts
Ken T
May 13, 2024 9:38 AM
Joined Aug, 2019 1707 posts

[Another topic was closed as a duplicate of this topic (Separate photo albums for Airbnb and VRBO)]

Ken T
May 13, 2024 9:38 AM
Joined Aug, 2019 1707 posts

[Another topic was closed as a duplicate of this topic (Property Photo Storage)]

Ken T
May 13, 2024 9:38 AM
Joined Aug, 2019 1707 posts

[Another topic was closed as a duplicate of this topic (Photo - Active/Hide)]

Ken T
May 13, 2024 9:39 AM
Joined Aug, 2019 1707 posts

[Another topic was closed as a duplicate of this topic (Disable Property Photos)]

Robert P
May 13, 2024 10:23 AM
Joined Aug, 2023 40 posts

This is NOT the same feature request.

Being able to send different photos to different channels (this thread) is a different facility than being able to upload additional photos and have the extra ones stored on OwnerRez, with some being active, and others not, and the ability to swap the stored ones in and out of the active set. As already explained, some photos may be seasonal, and used only at certain times (Christmas or WinterTime for example) of the year. They may go back up each year, and should not need to be resubmitted (along with the ones they replace).

It shouldn't be necessary to delete a photo to replace it with another one that has to be re-submitted, and vice versa to change it back, as seasons come and go during the year.

Deleting that feature request because this one exists makes no sense.

Or have I missed something?

Ken T
May 13, 2024 10:29 AM
Joined Aug, 2019 1707 posts

There are currently two related, but separate, feature requests active.

One is this one, which relates to assigning different photos to different channels.  To me, logically, this would also include the ability to assign a photo to no channels at all.

Then, there's this other one:

https://www.ownerrez.com/forums/requests/display-hide-gallery-photos-by-datemonthseason

Which relates specifically to a scheduling capability, allowing photos to be swapped in and out with the seasons.  I agree with you, that is a separate feature, and I've left it so.

For your purposes, you would want to vote up both of them.

Robert P
May 13, 2024 10:37 AM
Joined Aug, 2023 40 posts

I realize we're on the wrong thread for this part of the discussion, but the ability to swap photos in and out of the active set is ALSO a different feature than being able to have it done automatically on a schedule.

Swapping stored photos in and out of the active set (which I would only need to do manually) is one feature.

Having it done automatically according to a preset schedule is an additional feature that only becomes relevant once the swap feature is available.

I wouldn't want the scheduling facility to hold up introducing the ability to simply just swap photos in and out of the active set, hence my mentioning the distinction.

Ken T
May 13, 2024 10:43 AM
Joined Aug, 2019 1707 posts

the ability to swap photos in and out of the active set is ALSO a different feature than being able to have it done automatically on a schedule.

Well, yes, those are indeed two separate features.

The ability to swap photos in and out of the active set, for each channel as well as for the website, is inherently part of this feature request, as I mentioned.

To have that done automatically on a schedule, is NOT part of this specific feature request - it's the other one I linked to.

Robert P
May 13, 2024 12:03 PM
Joined Aug, 2023 40 posts

Sorry Ken, but I disagree with your contention about photos being swapped in and out of the active set being inherent to which ones get sent to a channel. In a global perspective it may be, and I understand why you say this, but that isn't the point.

1st Feature: Store and swap photos in and out of the active set, which appears on own site and gets sent to all channels.

2nd Feature: Have photos added to and removed from active set on a schedule.

3rd Feature: Have photos tagged by channel to control which 'set' or subset of the main currently active set gets sent to a particular channel.

The first is inherent within the second, and the third feature would inherently cover the first. BUT... combining them together, makes them (I suspect) a bigger project, and more difficult to do. And this being the case, the likelihood of the first feature NOT being introduced (being delayed or simply taking longer) because its been linked to also only being able to provide the 2nd or 3rd feature, becomes much more likely.

Personally, and I suspect for many other users as well, I would prefer to see the first feature introduced as soon as possible, without the second feature (and/or the third) holding it up because doing so has made it a much larger developmental chore. (This also means combining features which I also suspect are of less value to most users.)

I also think that as far as the forum and feature votes go, most users would't be looking to control which photos get sent to each channel (and thus wouldn't search for that) nearly as much as would simply want to be able to store and swap photos in and out of the main set. That being the case, you'll likely find yourself with additional feature request threads being started all over again.

The other requests are not all duplicates of this one... Baby steps.

"The more they over-tink the plumbing, the easier it is to stop up the drain." Scotty, Star Trek III

 

Ken T
May 13, 2024 12:13 PM
Joined Aug, 2019 1707 posts

I would prefer to see the first feature introduced as soon as possible

Realistically, that won't happen, because that alone is not in demand by enough people, nor is it likely to be.  By combining what you define as the first two features (which I still view programmatically as being simply different aspects of the same feature, much more efficiently coded together), the feature request becomes more popular and therefore more likely to get on the schedule.  Even as it is, I don't anticipate that happening in the near term.

In my personal opinion, this functionality overall is a valuable and useful idea, so I'd like to see it available sooner than later.  It's just in competition with a great many other feature requests, internally and externally, that are also valuable and in-demand.