How to upload Yosemite Photo to Blogger

[iubhounds]

I changed to the Yosemite 10.10.3 beta a couple of weeks ago. My 25Gb of iPhoto transferred to Photo with no issues. I am still having major problems with Apple Mail verifying with my 5 different Gmail accounts ... mail is a daily problem (frustration)

My question today is ... what is the process now of uploading photographs from the new PHOTO to my blog on blogger.com

Normally I could highlight "pictures" and then all of my different folders would show up for me to choose with photo I wanted to upload ... no problem.

Today was the first time I needed to upload a photo for my blog post. I did the same process I've always down but the only folder option I had to use was the PHOTO LIBRARY folder.

So, can anyone tell me what I need to do just to upload a photo from Yosemite Photos to a website?

Yes, I tried so search first on this forum but didn't find anything.

Can I go back in my Time Machine to the date before I updated to Beta and restore back to the NON beta version?

I still have iPhoto to use, so I am assuming I can delete PHOTO ?

 

[AllergyDoc]

Right now you'll have to export the image from Photos then upload it. It's a hassle but at least it runs quickly. I've been using Flickr Uploadr to back all my photos up, but it won't recognize Photos albums yet.

 

[iubhounds]

Right now you'll have to export the image from Photos then upload it. It's a hassle but at least it runs quickly. I've been using Flickr Uploadr to back all my photos up, but it won't recognize Photos albums yet.

Thanks for the answer about exporting the photo first. I also use Flickr for backing up my images and after trying that, it didn't work. I was just about to try to export from Photo to desktop and then try to upload the photo to my blog ... when I received the email notice there was a reply to my question.

I wonder if it is safe to assume this process will not change? Seems backwards.

 

[AllergyDoc]

I wonder if it is safe to assume this process will not change? Seems backwards.

I would be very surprised if it's not fixed by the time 10.3 is released to the general public. Leaving it like this would be a huge step back in functionality. Very backward.