lfcnutter
Forum Replies Created
-
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
thats excellent news..
thanks so far and look forward to administartor only functionality
OK updated and ran some tests. looks like this could really suit our environment.
Permissions: v2.6.0 successfully removes the configuration controls from Editors, but Editors can apparently still perform migrations. For MBKA we’d prefer an option to make migration/Push/Pull to/from Production Administrator-only.
Dry Run differences: will Migro normalise source/production hostnames when deciding whether content differs. Otherwise pages containing absolute URLs may appear changed solely because for instance
dev.montybees.org.ukbecomesmontybees.org.uk.OK. no need to fast track on my account. Still evaluating so am quite prepared to wait and see things once they are properly tested.
Further testing results
all test up to this point have been made using a WordPress Administrator account
I’ve now tested Migro while logged in as an Editor alongside our custom editorial workflow.The migration itself behaves very well and preserves the workflow statuses correctly.
However, an Editor can also access Migro Settings. From that screen the Editor appears able to change the environment from Production to Staging and can access Update Connection/Delete Connection controls.
For our use case, Editors should be able to work through the editorial workflow, but Migro configuration/pairing and production deployment should be Administrator-only.
Is there currently a capability setting for this, or could the Settings/pairing controls be restricted to administrators (
manage_options)?new version looks good.
2 localwp sites set up from scratch and migro installed on both.
pairing was automaticuploaded 3 images on dev to media library
added those 3 images to existing page and selected for migrationmigration of page and media library images successful
live progress bar now completes correctlyMigro Health still shows ToDo Configuration source (in blue)
does migro think this is still to be completed?Query on possible future development:
Would it be possible on the Batch Content Migration to have a button against a selected item that could check the current status of that item on staging and live.
An indication of just exact match or different may be extremely useful.No problem. looks like an ideal plugin for my use and thanks for the quick responses.
let me know when the fix is vailable and I’ll run another testOK pairing now successful using localhost:10011 and localhost:10017
have pushed a test page to production it has worked but the Live Progress bar still shows 99% even though below it shows success.
is this expected?Thank you. I checked the LocalWP Database tab and the Local Site Shell.
My current LocalWP installation on Windows does not display a Database Socket. It only provides:
Source site:
Host: localhost
Port: 10011Destination site:
Host: localhost
Port: 10017I also checked the Local Site Shell. There is no
DB_SOCKETenvironment variable or any other database socket value available.It therefore appears that this LocalWP version is using TCP connections through localhost and the individual port numbers.
Could you please confirm how Migro should be configured for this current LocalWP setup?