For the Editor permission: I can add an option in settings that Admin can decide if Editors are allowed to use Migro. If the option is unchecked, I would prefer to be checked by default, Migro is not presented to Editors, this can be done fast.
Dry Run Differences: Yes. Dry Run normalizes hostnames before comparing. It applies the same source→destination URL rewrite the migration performs, then compares, so a page differing only because dev.montybees.org.uk becomes montybees.org.uk is reported as unchanged. It also ignores differences that are only which media file each side points at. Page-builder layouts aren’t text-diffed at all, too many differences from one environment to the other but it does check if they are in sync, just don’t show the diff.
I’m working in reviewing more changes for WP 7.1 and will be able to release the 2.6.1 today with the admin checkbox, so you can test. But happy to know that my tool can help you (and thanks for taking care of the bees! I’ve been planting local wild flowers in my house for years to see if I can help the pollinators, it’s been working 🙂 )
Will have the new version soon and let me know if you have any other questions.
Thanks!
thats excellent news..
thanks so far and look forward to administartor only functionality
Ok, 2.6.1 is now live and the option to remove editors is in Settings. 🙂
Lots of bug fixes and improvements done too since I was already there.
Take a look and let me know.
Thanks!
Hey @lfcnutter,
Just catching up! Whenever you get a chance to update both sites to 2.6.1 and try the admin Editor-access setting with an Editor account, I would like to know it behaves the way you expected. If it does what you needed, great. If anything still looks off, tell me the exact step and I will sort it.
Either way, thanks again for the careful testing that shaped these last few releases.
Best,
Al
Hi, just completed testing on newly set up localwp sites.
pairing succeeded without a hitch
tested login to site with:
administartor: all good
Editor: no access to Migro plugin
Author: no access to Migro plugin
All looks good for installation on dev and live sites.
regards
Hey @lfcnutter
Great to hear that everything worked as expected. I appreciate all your insights here, it helped me to improve the tool for people who probably wanted the Editor out of the loop as well.
If you decide to use the tool in prod, let me know if anything looks off once it is on the real servers and I will sort it quickly, same as before.
A small request: if Migro saves you time on real staging-to-production work, a short review on the plugin page would be a real help for a small project like this. 🙂 And let me know if you need anything else!
Thanks again for the careful testing across these last few releases. It made the plugin better!
Best,
Al
