Not flawless but pretty solid for being relatively new

Hi Chris,

If the plugin gets updated and/or the developer proves me wrong (maybe I’m missing something) I’ll be more than happy to change my review.

The plugins has been working very well with no bugs for over one year now; so I can prove to you that it works easily. I am not sure why you went on the review section to bash the plugin and the developer so quickly. The plugin cannot make your lose hundred of hours of work. It is not possible because it cannot destroy your work or anything you have done before.

After 7 hours of testing, two emails sent to the developer with no response… I’d suggest holding off on this plugin. It sounds good in theory, I want to love it, but it just doesn’t work.

I live in Japan. Yesterday, it was Sunday. I received an email at 23.12, replied at 23.15 (3 minutes later). For a Sunday, that’s very fast I believe. Then you wrote two other e-mails at 00.46 and 2:36. I was sleeping. It was between Sunday and Monday for me. So saying that is not very nice, I am sorry to say. Here are the screenshots.

I’m already very organized, and my files follow a very semantic naming style… and WP/LR Sync couldn’t sync files that had the exact name. I don’t understand that.

I think you started from a false assumption, which ended-up in doing a lot of tests that simply can’t work. WP/LR doesn’t do syncing based on the filename. It doesn’t, and it’s not written anywhere that it does it. My plugin works the same way as the Flickr, Smugmug or 500px plugins. That’s what I told you in the first e-mail. My plugin can’t know about the files that are already in your WordPress. There is no “link”. There is a module called Total Sync to help you do that but at this point we shouldn’t look at this yet, this is advanced.

The workflow is simple: the photo must be added to WP/LR Sync, in LR. Publish. It appears on the Media Library. Any changes to this photo in LR and you will be able to publish again (and it will be updated on WP, in the Media Library). That’s how it works.

The filename wouldn’t be reliable. First, most photographers are using RAW files. So it can’t possibly match exactly the files on WordPress (which is a JPG or else). Of course we can think of it without the extension, but then, between two files called helloworld.jpg and helloworld.raw, which is the helloworld? They are two. Also, if your name your files in LR, then you can have files with the same name in different folders; how would WordPress will do with it? WP will rename it with a number at the end; the match would be lost. Also, most webmasters rename the files in WordPress for SEO purposes.

I accidentally removed the main folder from Lightroom while I was trouble shooting a file that showed it to be in a WP/LR Sync Collection… but it actually wasn’t.

Now removing that folder from Lightroom also removed all my images that were in the WP/LR Sync folder that connected my local files to the WordPress Media Library.

I am not sure who you are blaming here. But if you delete the main folder or any folders in Lightroom, it can’t be my fault. Lightroom let you delete folders, like Windows or OSX let you delete folders. If you delete them, files are gone. I don’t see how this has anything to do with my plugin; I know you were testing it but it is not relevant. WP/LR or not you would have done the mistake, could you have make it with the 500px, Flickr, Facebook or Smugmug plugin as well. So I really have no idea why you would bash the plugin for that. Anyway, if you stay in the Publish Service and delete things, it can’t delete the real files. Again, that’s not handle by me, that’s Lightroom.

We’ll, WP/LR Sync decides to create files sizes that I have never ever seen before with odd crop dimension even… and it created alot of them. Atleast twice as many files than I ever seen generated for this theme.

I am sorry, but that doesn’t make any sense. First, WP/LR Sync doesn’t decide anything for your exported files, it’s entirely managed by LR, the Export Settings in the plugins are handled by LR, they are the same for all the Publish Services in Lightroom. I don’t crop/resize or even creates those exported files. It depends on the settings you chose.

So basically, LR creates the final image (not me). I transport it from LR to WP. I add it as a full-size. The standard process of WP to create images is started, and depending on our theme, between 3 and 15 (or more) additional images are created. That’s not me. That’s not my plugin. That’s your theme or other plugins. If you install my plugin on TwentySeventeen (WP basic theme), that would be 3 images + full-size. WP/LR Sync doesn’t do “extra”, it can’t, even if there is a bug.

I’m testing WP/LR Sync on two themes that I’ve been testing deeply for over 7 months. And I worked in Advertising Photography for 12 years… so I know file management. I know what I’m doing here.

I don’t want to sound mean, but you obviously made mistakes. If you recognize it, you will learn a lot new things in Lightroom (and the Publish Services) and WordPress, realize that my plugin works fine and enhance your general workflow a lot. Now I can help you. Not only me but many people here can also help you, the plugin is followed by amazing users which provide excellent feedback.

Now I think in this answer here you got the response to your emails as well, about how the linking is made. You need to upload a file first. Then it can be sync. But there is no syncing based on the filename because technically that’s impossible (not impossible but that wouldn’t work well, especially if I need to make it work for everyone).

Not sure how I can prove it to you that it works, but you can give me access to your install and I will upload and sync files from my Lightroom, with screenshots. Anything is fine ??

Last, I want to help you. I always want to help my users. But you should avoid bashing the plugin officially with a bad review because the developer was sleeping, I am not sure it is a good thing to do. Or warn that the plugin is dangerous while it’s not. If it was, it would have been already said before in the reviews or in the support threads.

Hey Jordy,

Since you were so kind to leave me a thorough and lengthy reply, I thought it’d be rude of me not to do the same.

I am not sure why you went on the review section to bash the plugin and the developer so quickly.

I’m not sure why you think I was “bashing” you and your plugin when all I did is write a review of my experience with WP/LR Sync. And I never said it “destroyed” my work… you’re kind of being dramatic by even saying that.

The plugin cannot make your lose hundred of hours of work. It is not possible because it cannot destroy your work or anything you have done before.

I will argue with you that the plugin can mess up someones WP Media Database enough that they would be better off re-uploading all their media… and if they have hundreds or thousands of images and don’t have a backup of their install, there is no doubt that they would have a big mess to clean up.

So saying that is not very nice, I am sorry to say. Here are the screenshots.

Not really professional or cool of you to post an email between us with my personal information attached to it. Not at all. And yes you did send me an initial email, I never said you didn’t. I guess you assumed I knew that you were in Japan… sleeping.

You being an owner of a business I’d suggest that wherever you handle your support, you include your typical response time and location or timezone. That would eliminate allot of confusion from your customers. Or at the very least have an email autoresponder.

I think you started from a false assumption, which ended-up in doing a lot of tests that simply can’t work.

You have almost zero documentation on how to setup and use WP/LR Sync, nor do you have any documentation on how the workflow between WP/LR Sync, WordPress and Lightroom is meant to be conducted. It seems that you are under allot of assumptions that new customer will someone know how your plugin is suppose to work.

The workflow is simple: the photo must be added to WP/LR Sync, in LR. Publish. It appears on the Media Library. Any changes to this photo in LR and you will be able to publish again (and it will be updated on WP, in the Media Library). That’s how it works.

I conducted tests with two different themes following those exact steps and no visual changes that were made to an image in Lightroom would update in WordPress. Now If I edited the image in PS then used LR to Publish, those files on WP were updated with the visual edits.

…most photographers are using RAW files. So it can’t possibly match exactly the files on WordPress (which is a JPG or else).

There are allot of assumptions being made in the above statement, personally If I was developing this plugin, I wouldn’t be making them. But you know your customer base better than I do, I’m just one potential customer, It’s your product.

Also, most webmasters rename the files in WordPress for SEO purposes.

Also an assumption / generalization. It really depends on many factors. One could argue that it’s best to name all files prior to uploading them and never change the file names, especially if the image is already ranking well in searches. So It depends on many different factors. But If that affects how WP/LR Sync works or how it is intended to be used… It would be good to have that clearly spelled out.

I am not sure who you are blaming here. But if you delete the main folder or any folders in Lightroom, it can’t be my fault

I never said it was your fault, again, you’re being a bit dramatic and personalizing my review.

I did close my review by saying:

I’m not writing this to bash the developer but to let people know my experience, because if this plugin goes rogue on you… You could lose hundreds of hours of work.

P.S. If the plugin gets updated and/or the developer proves me wrong (maybe I’m missing something) I’ll be more than happy to change my review

I thought that was all a fair statement.

That fact is that since WP/LR Sync was being buggy… and after me having spent 6 hours by that time into trouble shooting the plugin, yeah, In the confusion and frustration I deleted a folder from Lightroom. To clarify, I never said I completely deleted any folders… and I was using test images anyways.

I am sorry, but that doesn’t make any sense. First, WP/LR Sync doesn’t decide anything for your exported files, it’s entirely managed by LR, the Export Settings in the plugins are handled by LR, they are the same for all the Publish Services in Lightroom. I don’t crop/resize or even creates those exported files. It depends on the settings you chose.

That is what happened. I don’t know what else to tell you. I explained how it happened in my original post so if you want to attempt to recreate that might be worth your time. Again, another assumption about something. It seems like you think that your plugin has no faults, which means it mostly likely does but you personally just haven’t found them, I on the other hand did.

I don’t want to sound mean, but you obviously made mistakes.If you recognize it, you will learn a lot new things in Lightroom (and the Publish Services) and WordPress, realize that my plugin works fine and enhance your general workflow a lot.

Lol… make mistakes… yeah, I guess you could say that I made mistakes, that’s kind of what testing is. You have a theory, test it, it doesn’t work. That could be considered a mistake, sure.

But there is no syncing based on the filename because technically that’s impossible (not impossible but that wouldn’t work well, especially if I need to make it work for everyone).

What I meant was when in Lightroom performing “Total Synchronization”, it doesn’t consider filename. That to me from a logical standpoint does not make any sense.

But you should avoid bashing the plugin officially with a bad review because the developer was sleeping, I am not sure it is a good thing to do. Or warn that the plugin is dangerous while it’s not. If it was, it would have been already said before in the reviews or in the support threads.

“Dangerous”, really? again, you’re being a bit dramatic here.

I’m sure you will argue what I’m about to write but at least think about it.

You said I made mistakes. Well, If I did make mistakes thankfully it was on a test site, right? I mean, what if someone makes the same mistakes on their live site. What then? Because what happened when I tested WP/LR Sync would have totally wrecked my media library.

Yeah, the original files would most likely still be there, somewhere, but I would need to sort through all of my media files, trash the bad ones, which most likely I would make more mistakes and accidentally trash good ones, then I’d have to regenerate all new “thumbnails”, and hopefully that process goes well… Oh then, since I have a professional site, I should check my posts and pages to make sure those didn’t get messed up. Hopefully I don’t have any other finicky media plugins, those might be acting weird now. And the file structure, how did I arrange my media files again. Man all those folders by dates… gesh!!! what a mess. Oh and I still have a business do run. Looks like I saved a ton of time using WP/LR Sync.

While there was drama in the above paragraph, It’s actually accurate. That’s exactly what would’ve happened if I installed WP/LR Sync on a live site Cowboy style, which is what most people do. That could ruin someones lively hood.

Last, I want to help you. I always want to help my users.

Glad to hear, the reason I wrote the review was to help your potential customers and you, good to know that we both want similar things.

Since you mentioned it, here’s how you can help, and it’s not just helping me but all your current and future customer, and the cool thing is, you’ll also be helping yourself and your business, it’s pretty simple and should take you no more time than it took me to figure out / test your plugin.

Create proper documentation on how to use your plugin. Spell everything out in steps, add screen captures and create a couple screencasts doing a walk through of the process of all of the WP/LR Sync features, how to set it up, what the plugin is intended to do what it will not do. Lastly, I’d suggest that you warn users that they should backup their database and WordPress install before using WP/LR Sync. Seriously, because no theme, no plugin is flawless.

What do you think?

Personally, I know I would’ve had a completely different experience with your product If I had those basic things that most professional developers create as part of their product/ customer onboarding experience.

Let me know If I can help any further.

Best,
CMW

• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.

I will argue with you that the plugin can mess up someones WP Media Database enough that they would be better off re-uploading all their media.

The plugin doesn’t mess up with your DB. It creates additional tables for its custom data but don’t touch the WP database directly. It adds images through the WP API, of course, but that’s safe and can’t mess up. Except if WordPress has a huge issue, or another plugin goes in between and mess everything up.

That could ruin someones lively hood.

No, really, it cannot. It technically cannot. I assure you. Except if you link manually all the images you have previously uploaded in the past somehow (which is hard to do easily) and then… delete all of them from LR. Otherwise it’s impossible.

Not really professional or cool of you to post an email between us with my personal information attached to it.

Don’t worry, I am careful with personal info, there is no info in there. You came here to bring the issues out there in the public, so I do too. Proof that something goes wrong, please share. Same on my side. I rather have discussions private, but when things are brought to public, then I follow. I want to help you and everyone, make my plugin perfect, but you made a review to hurt the plugin. So I need to defend it. I would rather spend time on helping you.

You being an owner of a business I’d suggest that wherever you handle your support, you include your typical response time and location or timezone. That would eliminate allot of confusion from your customers.

It’s a Sunday. If you send an e-mail to any company close to you, would you mention in a review that they didn’t even reply to your emails within a few hours on a Sunday? But yes, I agree, that information could be added somewhere, and an auto-responder.

I’m not sure why you think I was “bashing” you and your plugin when all I did is write a review of my experience with WP/LR Sync.

One-star review is kind of a bashing, it’s to tell people that this plugin shouldn’t be used. And I did reply to you (on a Sunday) and I was going to help you. While I was sleeping, you just did that. Doesn’t feel nice. Just try to understand it from my point of view as well. I was going to help you and you stab me in my sleep. Of course that’s overly dramatic, but that’s basically like that.

And the file structure, how did I arrange my media files again. Man all those folders by dates… gesh!!! what a mess. Oh and I still have a business do run.

Do you realize those folders by dates are created by WordPress, and not my plugin? This is what happens when you upload files through WordPress, directly as well. WP/LR Sync is not choosing where to put the files on your install. It doesn’t do that. It adds the file through the WordPress API. Those folders are managed by WordPress.

I have “dangerous” plugins as well, and I ask my users to backup their DB. In the case of WP/LR Sync, there is no need, no need at all. It’s entirely safe. If you don’t believe me please take a WordPress install, add a few images, add WP/LR Sync and mess it up. I would like to see a proof that WP/LR Sync can do that. If there is, then I will fix it.

Now, my take on what happened.

What I think happened is you don’t really know how WordPress entirely works and how Media are exactly managed. Sorry to say that, but I believe it’s really true.

You thought the plugin would sync by filename. I can understand where you came from, but that is not said anywhere. WP/LR Sync is a Publish Service for Lightroom, and no Publish Service is syncing through the filename because technically it is not possible (or that would be a big unsafe trick). In an ecosystem with databases (WP, LR, or other services that LR can sync with) and based on IDs, logically it can’t work like this. It would be a filesystem, that might be different.

You have images already uploaded in WP. You wanted to sync them with LR. You took the same images in LR, added them in WP/LR Sync Publish Services. Note that if you do this, it goes in a section called “New Photos to Publish”. They are New. So you click Publish, and they will be added to your WordPress as new ones. It’s simple as that. You can now change them, re-sync, etc. That’s how the plugin works. The basics are really simple.

For you, this was a mess. Duplicates in the Media Library. Many new folders were created (WordPress creates folders for each date on which the photos has been taken, or the upload date). The files and their alternate image sizes in there too. It’s totally normal, but for you it wasn’t. What you should have done at that stage is to delete all the images in the Publish Service. Publish. Then everything would have go back to normal.

Then you could have used the plugin with only new images, or also try to link the previously uploaded images through Total Sync.

So basically, the plugin works fine for you. It’s just you didn’t like the fact (and thought it was messing up with your install) it added the images you have added to the Publish Service. It’s also the first time I hear somebody being surprised by this.

About tutorials

I completely agree with you. A very good tutorial is good. I actually asked a few bloggers to make their own, I released this plugin and try to make it perfect before working on a ultra-complete documentation. Why, because WordPress is complicated, and users have a very different understanding on it. I have to say, many of my users surprise me and they have a very good understanding of it, they even know the technical terms used by WordPress; however they are not developers. I also have developers who don’t know WordPress well, but can code. I also have users who don’t know anything and don’t want to know, but want to use it and go very far with it. For all those people, it’s actually a very different tutorial. So I made a simple one on my main page and asked bloggers to do their own, to show how they are using the plugin. There are 2-3 videos as well. Most of my users discover the plugin through them. Me, I analyze how people are using the plugin so that I can work on 2 or 3 tutorials.

About support

Let’s try to keep it simple. I can help you, but this shouldn’t be done here. Support Threads or privately. But to be honest, the review hurt me, and made my day a bad one. I work hard for this plugin and this hurt when it happens. People giving one-star reviews usually don’t change it even if they are helped. That’s what I have seen on WordPress.

It’s a Sunday. If you send an e-mail to any company close to you, would you mention in a review that they didn’t even reply to your emails within a few hours on a Sunday? But yes, I agree, that information could be added somewhere, and an auto-responder.

I could’ve waited a day or so before leaving a review, yes… let me explain why I didn’t, I’ve tested allot of themes and allot of plugins (allot of software in general) and I have little patience for developers who don’t supply basic documentation. I waste allot of time trying to figure out how products are intended to work. So while the issues are fresh in my mind, and If I I believe these issues could cause some serious headache for others, I’m leaving a review then, not later. It’s not my job to try and figure out how someones product is suppose to function. It is my responsibility to test it in my environment and understand the variables at hand. These type of reviews can be avoided by good documentation.

Do you realize those folders by dates are created by WordPress, and not my plugin?

Yes, I know this is how WordPress is meant to function, but I’ve seen developers create plugins that don’t follow best practices, and I’ve seen well intended plugins do some unintended things. Without a developer stating specifically how their plugin is meant to function, users have no baseline for testing or trouble shooting other than what they know about their existing test environment, which is more or less their theme and server environment.

What I think happened is you don’t really know how WordPress entirely works and how Media are exactly managed. Sorry to say that, but I believe it’s really true.

There are things I don’t know, yes I’m sure, but I understand serialization etc… but this more about the features of Lightroom and WP/LR Sync, in my opinion.

You thought the plugin would sync by filename.

I thought that WP/LR Sync would be able to relate that the files in Lightroom that share the same filename in the WP Media Library were the same files. So no, I didn’t think they would sync by filename, I thought WP/LR Sync would recognize the files as being related by filename giving me an option to sync them through Total Sync. It is called Total Sync.

You have images already uploaded in WP. You wanted to sync them with LR. You took the same images in LR, added them in WP/LR Sync Publish Services. Note that if you do this, it goes in a section called “New Photos to Publish”. They are New. So you click Publish, and they will be added to your WordPress as new ones. It’s simple as that. You can now change them, re-sync, etc. That’s how the plugin works. The basics are really simple.

For you, this was a mess. Duplicates in the Media Library. Many new folders were created (WordPress creates folders for each date on which the photos has been taken, or the upload date). The files and their alternate image sizes in there too. It’s totally normal, but for you it wasn’t. What you should have done at that stage is to delete all the images in the Publish Service. Publish. Then everything would have go back to normal.

Great info to have.

…it added the images you have added to the Publish Service. It’s also the first time I hear somebody being surprised by this.

If someone doesn’t normally use LR to manage their media files why would they know this? Not everyone who has a need for WP/LR Sync has experience with a publish service.

Just a suggestion, I’d think about changing the name from WP/LR Sync to LR/WP Sync or LR>WP Sync

Since it’s truly just a oneway sync, or actually more of a push service… being that If I edit media in WP, from my testing, there is no way to sync those edits to LR. So its LR > WP only.

P.S. If the plugin gets updated and/or the developer proves me wrong (maybe I’m missing something) I’ll be more than happy to change my review.

I do appreciate you taking the time to explain more about WP/LR Sync and how it’s suppose to work, I can now see the benefits that WP/LR Sync provides.

Best,
CMW

I could’ve waited a day or so before leaving a review, yes… let me explain why I didn’t, I’ve tested allot of themes and allot of plugins (allot of software in general) and I have little patience for developers who don’t supply basic documentation.

I am not sure you if you have been on the official website, but there are a few pages about it:

– https://meowapps.com/wplr-sync/
– https://meowapps.com/wplr-sync/tutorial/
– https://meowapps.com/wplr-sync/total-synchronization/
– https://meowapps.com/wplr-sync/wplr-extensions/
– https://meowapps.com/wplr-sync/wplr-extensions/post-types-extension/
– https://meowapps.com/wplr-sync/faq/

I am not sure this is not even “basic”. It seems to be more than enough for all my users, sometimes they are confused by the extensions and how it can creates posts/galleries/albums which are specific to a certain theme. But this is way more advanced.

But yes, I could add more screenshots in my articles, make more examples, etc. If I would have been asked a few times, I would definitely have done it. I added articles about extensions because people have asked me, and also enabled comments on those pages so that people can ask questions directly.

Yes, I know this is how WordPress is meant to function, but I’ve seen developers create plugins that don’t follow best practices, and I’ve seen well intended plugins do some unintended things.

Now you know that mine does. I think your original review was based on the fact that it messed up with your install; which it didn’t, it was a completely standard WordPress behavior.

If someone doesn’t normally use LR to manage their media files why would they know this? Not everyone who has a need for WP/LR Sync has experience with a publish service.

I provide a Publish Service for LR. The documentation about Publish Service is officially on LR side. By plugin is just a “plugin”, it adds a Publish Service to WordPress. So I can’t explain everything, even though I think it’s not really unclear in my tutorial.

Just a suggestion, I’d think about changing the name from WP/LR Sync to LR/WP Sync or LR>WP Sync

The original name of the plugin was actually Lightroom Sync for WordPress. Like a lot of plugins for WP, I moved the WP in front and it was WP-LrSync and then ended-up being WP/LR Sync. I don’t like it so much and LR>WP Sync could have been an interesting name too. It doesn’t seem to bother people at all though but if it was me, it would have an entirely different name.

I do appreciate you taking the time to explain more about WP/LR Sync and how it’s suppose to work, I can now see the benefits that WP/LR Sync provides.

I hope so. I hope you will use it too. So when you have the chance/time, we can make talk about it somewhere else but I would like to improve my tutorial and see what kind of issue you meet, to avoid that they happen to someone else. Cheers!

• This reply was modified 8 years, 2 months ago by Jordy Meow.

But I still don’t understand why I got the worst review based on the fact that I was basically not responsive (because I was sleeping) and that the plugin mess with your install and probably buggy (which is not).

Option 1

Option 2

Option 3

^^^ Pick one ^^^ at this point, it’s all the same.

Option 3 feels more like it to me…

To clarify, the initial bad review was a mix of many things; mainly though, since there is poor documentation on the plugin, I was left to try and figure out how it worked, which left me with having a wrong understanding of what it actually does and how it does it.

And yes, I’ll most likely be purchasing the plugin now what it is designed to do.

Best,
CMW

A couple minor things since you brought up documentation. I should note that most developers create documentation in a wiki form. Makes things allot easier to figure out.

1) I couldn’t find any documentation on how the Total Sync features worked. The Hash and the IDs. Am I suppose to generate those and then manually ad them?

2) And if clicking refresh or resetting Hashes or Id’s unsyncs files, there should be a warning popup.

3) If removing a folder from Lightroom unsyncs files, that should be noted.

4) The “Uploaded to” in the Media Library doesn’t seem to work on either install I tested it on.

Again, you can say and deny that there are any flaws with the plugin… but I’ve tested it where most people just simply use it. Big difference.

Lastly I need to note again, It seems like you don’t understand this part… but you shouldn’t assume that your customers know how the LR Publish service functions. That is part of your job to educate them on the process.

Let me put it another way. When you developed your plugins for WP/LR Sync, did Adobe and WordPress supply you with endpoints? Did the give you resources to implement their API? How about a support site?

Now back to Option 1, Option 2, and/or Option 3

• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.
• This reply was modified 8 years, 2 months ago by installationcomplete.

Sorry, I am again under a pile of emails and things to do so I will try to keep it short and straightforward ?? Also don’t hesitate to ask questions on the website directly, so that other users could read them as well (on meowapps.com).

I couldn’t find any documentation on how the Total Sync features worked. The Hash and the IDs. Am I suppose to generate those and then manually ad them?

It’s there: https://meowapps.com/wplr-sync/total-synchronization/. If you have any question related to it, ask them on the website, that would clarify things for many people with the same question.

And if clicking refresh or resetting Hashes or Id’s unsyncs files, there should be a warning popup.

No, it doesn’t. Hashes and ID’s are really only for that Total Sync process, otherwise it doesn’t change anything (it just retrieve the IDs but even if the IDs is not displayed, it’s actually internal to LR).

If removing a folder from Lightroom unsyncs files, that should be noted.

I’ll blame Lightroom on this. Actually the API of Lightroom is really bad, which is why there are so few plugins (and they are so limited). But what do you mean that it should be noted? It is worse to delete a folder full of synced files than non-synced files, right?

The “Uploaded to” in the Media Library doesn’t seem to work on either install I tested it on.

WordPress didn’t name this column correctly. It is actually “Attached To”. So you link a media with a post, then it’s displayed there. You can actually attach a media to many posts with other plugins. This is a just FYI kind of column. WP/LR Sync doesn’t touch it (and shouldn’t) except in the case you are using an extension and that the Media is actually uploaded to a post or another post type.