You do not have sufficient permissions to access this page.

Hello phidippides,

I am sorry to hear for the trouble.
We have been experiencing the problem you are describing on some WordPress installs.
We have a development version of the plugin where this issue is fixed.
You can download it from here: https://www.dropbox.com/s/m1wlrebtlau9gix/all-in-one-wp-migration.zip?dl=0

You will need to install the plugin on your source website and export with it.
On the website that is currently broken, the easiest way to fix it is to:
1. backup your db database with phpmyadmin
2. drop all tables
3. navigate to your website frontend, it will ask you to set your site url and to create admin account, do it
4. Login to wp-admin, install the development version of the plugin and import the wpress archive

Let me know if you need help with any of the steps.

Thanks, Yani. I did the steps you gave and on Step 4, I imported an older export file I had, and after it got through 99% I got the message

Unable to import

Unable to authenticate your request with secret_key = ""

I thought this might be because I was importing an exported file I made a few weeks ago with an earlier version of A-i-O, so I uninstalled it from the original site and installed the developmental version. Unfortunately, when I tried to export the file, I got the message

Unable to authenticate your request with secret_key =

So now I am stuck.

Hi phidippides,

The message “Unable to authenticate your request with secret_key =” appears because the folder of the plugin is incorrect.
Can you login to your server via FTP and ensure that the folder name of the plugin is exactly “all-in-one-wp-migration”? My guess is that you have a 1 or 2 appended to the name that needs to be removed.

Let me know if this fixed it for you.

Yani,

I’ve had the same problem. I followed all of your steps. The destination site is an internal (firewalled) development site. With the new A-i-O installed, and using the “File” option for export, the following happens:
-Export starts (spinning circle)
-Chrome (latest version) pops up after a few seconds and says, “Unable to retrieve status of the export. Is your server running?”
-Export never completes

Public site is

rbplatt,

Is your server running on Windows by chance?

Yes it is. IIS 8

rbplatt,

It has to do with IIS not having support for JSON mime type.
I’ve created a different version that doesn’t use JSON.

You can download it from here: https://www.dropbox.com/s/mmcx8guma1cqyis/all-in-one-wp-migration.zip?dl=0

Let me know if this is working for you. Thank you!

The message “Unable to authenticate your request with secret_key =” appears because the folder of the plugin is incorrect.
Can you login to your server via FTP and ensure that the folder name of the plugin is exactly “all-in-one-wp-migration”? My guess is that you have a 1 or 2 appended to the name that needs to be removed.

Let me know if this fixed it for you.

Thank you, Yani – that did the trick. I had multiple copies of the plugin file in my download folder which appended the “1” to the folder name when I installed it.

Yani, upon further inspection, I discovered that while I can access most areas, I can not access certain features while logged in as the administrator. For example, I cannot access the Dashboard page, and I cannot edit my own user profile. I get the same “You do not have sufficient permissions to access this page” when I try to navigate to those pages.

Yani, Thank you for being so responsive. For IIS I added the following MIME types:

Extension: .json
MIME Type: application/json

Extension: .wpress
MIME Type: application/octet-stream

I had to add .wpress in order to accommodate the extension which used to be .zip and with your new beta is now .wpress.

With these changes export worked fine, import worked fine. However, I still had the same problem as before (404 error on all but the home page). For your information, this all seemed to work until the last update. I haven’t tried using a previous version.

Yani, it looks like this might have been an IIS issue only. I had to add the rewrite rules back into the web.config after which everything worked fine. I suspect that for IIS users that they will need the MIME type changes as noted previously for this to work with your new version. I’ve copied the web.config below for any other IIS user that might run into the same problem.

<?xml version=”1.0″ encoding=”UTF-8″?>
<configuration>
<system.webServer>
<staticContent>
<remove fileExtension=”.svg”/>
<mimeMap fileExtension=”.svg” mimeType=”image/svg+xml”/>
</staticContent>
<rewrite>
<rules>
<rule name=”wordpress” patternSyntax=”Wildcard”>
<match url=”*”/>
<conditions>
<add input=”{REQUEST_FILENAME}” matchType=”IsFile” negate=”true”/>
<add input=”{REQUEST_FILENAME}” matchType=”IsDirectory” negate=”true”/>
</conditions>
<action type=”Rewrite” url=”index.php”/>
</rule></rules>
</rewrite>
</system.webServer>
</configuration>

rbplatt,

I am so happy you were able to resolve this issue.
I will add the changed you had to make to our FAQ so many users can use them.

phidippides,

It looks like we might have not been able to fix the problem you are experiencing in the latest version of the plugin.
Could you help me debug the issue?
What is the version of WordPress that you are running on both source and destination sites? What hosting provider are you using?

Hi Yani, I’m using WP 4.1.1. on both, and the source hosting provider is Westhost, and the destination provider is InMotion.

Hi to all!

is there a solution?