• Resolved aspsa

    (@aspsa)


    Greetings. I have been using Duplicator Lite for some time and have had no issues with it until very recently. Currently, I have version 1.4.0 installed. Also, I use Local Lightning for my WP site development efforts, running under Windows 10.

    In the past, I slightly modified the Duplicator procedure in order for it to work with Local. The Duplicator videos only demonstrate migrating between local development & remote production environments, which does not apply when duplicating a WP site developed locally and then migrating it to another version of the same site under a local development environment. Maybe the problem I am experiencing is only an issue with Local Lightning? I most recently changed over to Local Lightning from Local’s previous incarnation, which ran under a virtual machine.

    Here are the steps I took historically when the duplication & migration process worked with Duplicator Lite running under Local’s previous virtual machine version:

    1. Logged into the WP web site to be duplicated
    2. Created a new Duplicator Lite package
    3. Downloaded the installer and package files
    4. Renamed the lengthy installer file to “installer.php”
    5. Created a new WP web site in Local
    6. Started & logged into the newly created WP web site
    7. Viewed the newly created WP site
    8. Under the new web site’s “public” directory, renamed “wp-config.php” to “wp-config.php_bak
    9. Copied the Duplicator Lite installer files into the “public” directory
    10. For the currently opened view of the newly created WP web site, replaced the URL in the address bar with the following: <WP domain name>/installer.php
    11. After refreshing the page, the Duplicator Lite package files kicked in to migrate the duplicated WP web site to the newly created WP web site
    12. Followed the instructions after the page refreshed, which included entering the proper database name, database user name and database password
    13. Completed the migration process
    14. Selected the installer’s prompt to log into the migrated WP site (doing so would automatically delete the Duplicator Lite installer files)
    15. Opened a new web browser tab to view the newly migrated site

    These series of steps worked flawlessly every single time. Now, after executing the second to last step, instead of being able to log into my newly migrated WP web site as the admin, I am confronted with the following error message:

    “Sorry, you are not allowed to access this page.”

    I did not alter my log in credentials during the migration process, but this error persists, and I am unable to access the migrated WP web site. I compared the “wp-config.php” files across the original and duplicated WP web sites, and, as expected, their contents are identical. Similarly, I examined both the ‘<..>_users’ and ‘<..>_usermeta’ database tables underlying the original and duplicated WP sites. The users tables, in this entailing case a single ‘admin’ record’, matched identically. Similarly, the ‘<..>_capabilities’ meta key values across both ‘<..>_usermeta’ tables matched identically. In other words, this means both the original and duplicated WP web site are credentialed for access identically. The singly defined ‘admin’ user in each case has precisely the same log-in credentials, which is why I am confused as to why the access error message appears at all.

    Your feedback & recommendations are greatly appreciated. Thank you.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter aspsa

    (@aspsa)

    [UPDATE]

    In the interim, I tried a different approach by bypassing the Duplicator Lite WP plugin altogether and, instead, relying upon Local Lightning’s WP web site export capability. Here are the steps I took:

    1. Deleted the migrated version of the original WP web site
    2. Dragged & dropped an exported zip file of the original WP web site into Local Lightning. The exported version was imported into a new location and name of my choosing. However, during the provisioning process, a warning message appeared stating the import process failed to import several SQL files.
    3. After excepting the warning message, I allowed the import process to conclude.
    4. I compared the SQL files in question between the original and newly imported versions of the WP web site. However, contrary the warning message, I confirmed that the SQL files in question actually did import into the WP web site and their file sizes were identical.
    5. I opened the newly imported WP web site and everything seemed to be in order

    I’ll have to examine the newly imported WP web site over time to see if there are any anomalies. However, at first sight, it appears the Local Lightning import & export processes work well enough and that this my be my process of choice when working on multiple versions of a WP web site within the Local Lightning development environment. Still, I need to resolve the Duplicator Lite issues mentioned in this thread, because I require this process to work when moving my WP web sites between development and production environments.

    Hey @aspsa,

    The best recommendations I have for this issue would be found in this FAQ item:

    ? ? – I cannot log in to my WordPress admin dashboard, what can I do?
    ? ? – https://snapcreek.com/duplicator/docs/faqs-tech/#faq-installer-220-q

    Hope this helps~

    Thread Starter aspsa

    (@aspsa)

    I appreciate the link, Cory. Unfortunately, less the redirect recommendation, all the remaining recommendations are predicated upon having a login page appear. As noted in this thread, this does not occur. Rather, when I start my Local server and access my WordPress web site, I simply am confronted with the ““Sorry, you are not allowed to access this page.” error message. This is not a login credentials problem since a comparison between the original and duplicated WP web site’s ‘wp_users’ database tables reveal identical credentials for the one and only ‘admin’ user record in those tables.

    I’m afraid there is something more problematic occurring, and I first need to see if I can replicate this same problem with the previous Local application version, which ran under a virtual machine. It could be some configuration setting that requires tweaking now that Local Lightning runs natively under Windows.

    While I hate to do it, I may need to explore other local (no pun intended) development environment applications.

    • This reply was modified 3 years, 10 months ago by aspsa.

    Hey @aspsa,

    Yeah, I’m not 100% sure, but there are quite a few articles from google, with people getting the same issue. Here is one that might help:

    https://kinsta.com/knowledgebase/sorry-you-are-not-allowed-to-access-this-page-error-in-wordpress/

    Thanks

    Thread Starter aspsa

    (@aspsa)

    Cory, thank you for the follow-up post and, as I may have mentioned in other posts elsewhere, I appreciate your developing this plugin for the WordPress community. I revisited the virtual machine version of Local by Flywheel, known as “Local Classic”. The newest non-VM version is called “Local Lightning”, and Local by Flywheel no longer supports Local Classic.

    After completing the entire Duplicator Lite migration process (see this thread for the steps I took) from my original WP site as hosted in Local Classic to a newly created WP site also hosted in Local Classic, I can report that it performed seamlessly. First, I did not receive the “Sorry, you are not allowed to access this page.” error message. Second, when Duplicator Lite prompted me to log in as administrator, I was able to do so and, as had occurred at all times previously when I ran this process within the Local Classic application, Duplicator Lite automatically deleted the installer files.

    This experience is bittersweet. It works but only within Local Classic and not within Local Lightning, again, where the former is no longer supported by Local by Flywheel. I cannot conclude that Local Lightning somehow does not support the Duplicator Lite plugin, especially since plugin integration occurs at the WordPress framework level and should be independent of the web hosting environment. As previously mentioned, perhaps Local Lightning requires configuration file tweaking. However, I do not feel confident that pursuing this path will resolve this problem nor do I believe it is a trivial ‘fix’, which leads me to ask the following question:

    Can you kindly provide a list of local development platforms and versions under which Duplicator Lite has been tested? Let’s assume we are using WordPress version 5.6.2. Here are some platforms that come to mind:

    Local by Flywheel (Class & Lightning)
    XAMPP
    WAMP
    Laragon
    Laravel Valet (Mac OS only)

    Hey @aspsa

    The current list we have right now is listed in this FAQ, of course, we don’t do a lot of work with Local by flywheel, so it possible the lightning portion could have some issues like the ones you are seeing.

    ? ? – What host providers are recommended for Duplicator?
    ? ? – https://snapcreek.com/duplicator/docs/faqs-tech/#faq-resource-040-q

    Hope this helps~

    Thread Starter aspsa

    (@aspsa)

    Cory, thank you for the link. I assume “Local” under “Personal Computer” section refers to “Local Classic”, the Local by Flywheel virtual machine version of the application.

    Hey @aspsa,

    That would be correct. We don’t run tests on every release of their software, so it’s possible that bugs can pop up from time to time.

    Thanks

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘No Access After WP Site Duplication’ is closed to new replies.