Forum Replies Created

Viewing 15 replies - 1 through 15 (of 5,036 total)
  • Plugin Author Yani

    (@yaniiliev)

    Hi there,

    Thanks for the detailed breakdown of your setup. Since you’re using the Unlimited Extension (a premium product), our dedicated support team will be best equipped to help you troubleshoot this. Per the forum guidelines, premium products are supported through our direct support channel rather than the community forums.

    Please reach out here: https://servmask.com/contact-support

    That said, given the symptoms you’re describing (stalling at 42% during media archiving on a large 8.2 GB site, while smaller sites complete fine), the support team will likely want to look at your server’s memory_limit, max_execution_time, disk space availability, and disk I/O worker configuration. Something in the latest server or PHP environment update may have tightened one of these limits just enough to affect your largest site.

    The team will be able to dig into the specifics with you and get this sorted out.

    Yani

    (@yaniiliev)

    Hi @nic,

    Thanks for reaching out! By default, the Query Loop stacks to a single column on screens below 782px to keep the content readable on smaller devices.

    If you’d like to show two columns on mobile, you can add this custom CSS snippet via Appearance > Editor > Styles > Additional CSS (or a child theme):

    @media only screen and (max-width: 781px) {
      .wp-block-post-template {
        grid-template-columns: repeat(2, minmax(0, 1fr));
      }
    }

    If you only want this on a specific page, you can add a custom CSS class to the Query Loop block (under Advanced > Additional CSS class(es)), for example mobile-two-cols, and then target it like this:

    @media only screen and (max-width: 781px) {
      .mobile-two-cols {
        grid-template-columns: repeat(2, minmax(0, 1fr));
      }
    }

    Let me know if that helps!

    Plugin Author Yani

    (@yaniiliev)

    Hi there,

    When a backup was created years ago, it contains the plugins and themes from that time. Since then, WordPress, PHP, and many plugins/themes have received major updates, which can cause compatibility issues during import.

    Here is what I would recommend:

    Set up a temporary site running an older version of WordPress and PHP that matches the era when the backup was originally created. Import the archive there. Once the import completes successfully, update your plugins and active theme first, then update WordPress itself, then update PHP. After everything is confirmed working on the latest versions, create a fresh export. That new archive will import cleanly on any current site.

    If you need help identifying which WordPress/PHP versions to start with, let us know roughly when the original backup was made and we can point you in the right direction.

    Alternatively, you can extract package.json from the backup using traktor: https://traktor.wp-migration.com/
    It contains the WordPress version, PHP version, MySQL/MariaDB version of the site that the backed up.

    You can easily create a website in your browser using WordPress Playground: https://ww.wp.xz.cn/plugins/all-in-one-wp-migration/?preview=1
    Click the gear icon in the top right corner and select the WordPress version and PHP version that you got from package.json

    Plugin Author Yani

    (@yaniiliev)

    Great question! We actually have a dedicated checklist for exactly this: https://blog.servmask.com/post-migration-verification-checklist

    It covers 50+ verification steps across 10 categories: content, forms, email, URLs, SSL, performance, cron jobs, SEO, e-commerce, and third-party integrations. You can work through it top to bottom to make sure nothing was missed.

    Plugin Author Yani

    (@yaniiliev)

    Hi nikkiemond,

    I hope you are well. Does the plugin stop halfway of the upload or halfway of the import?

    Plugin Author Yani

    (@yaniiliev)

    Hi @16ww, thank you for reaching out! Just a quick note, the reviews section isn’t the best place to get technical support, and it’s also best to start your own topic rather than posting on someone else’s review. Our support team won’t be able to follow up with you here.

    Could you please open a new support topic in the plugin’s support forum?

    Thanks for understanding, and we look forward to helping you there!

    Plugin Author Yani

    (@yaniiliev)

    Hi Andrew,

    Thanks for the feedback. I want to clarify something because the review is based on a misunderstanding of where the upload limit comes from.

    The plugin does not set a file size limit. The number you see is your hosting provider’s PHP configuration (upload_max_filesize and post_max_size). The plugin reads and displays it so you know what your server allows before you try to upload.

    You can verify this yourself: go to Tools > Site Health > Info > Server in your WordPress dashboard and check upload_max_filesize. It will match what the plugin shows. You can also try the plugin on the ww.wp.xz.cn live preview (https://ww.wp.xz.cn/plugins/all-in-one-wp-migration/?preview=1) where the server allows imports up to 2GB. Same plugin, different server, different limit.

    In many cases, you can increase the limit yourself by editing .htaccess, .user.ini, or asking your host to raise it. We have a guide here: https://blog.servmask.com/wordpress-upload-limit/

    The Unlimited Extension exists for cases where your hosting provider locks those PHP settings or where server-level restrictions (Nginx limits, firewall rules, Cloudflare caps) block large uploads regardless of your PHP config. It works by transferring data in small chunks that stay under every limit. If adjusting your PHP settings works, you do not need it.

    As for “All-in-One”, the name refers to migrating your entire site (database, media, themes, plugins, content) in a single file. Not a claim that every feature is free.

    Happy to help you get your import working in the support forum.

    • This reply was modified 2 weeks, 1 day ago by Yani.
    Plugin Author Yani

    (@yaniiliev)

    Hello Kotaro,

    I hope you are well.
    I have logged your request and passed it to the team.
    I am sure we can ship it in the upcoming new versions.

    Plugin Author Yani

    (@yaniiliev)

    Hola,

    Gracias por compartir la captura de pantalla. El error indica que el plugin no puede escribir en su carpeta de almacenamiento:

    /home/opinand1/public_html/wp-content/plugins/all-in-one-wp-migration/storage/

    Esto es un problema de permisos de archivo en tu servidor. Para solucionarlo:

    1. Accede a tu hosting mediante el Administrador de Archivos en cPanel (o por FTP)
    2. Navega a wp-content/plugins/all-in-one-wp-migration/storage/
    3. Cambia los permisos de la carpeta storage a 755 (haz clic derecho > Cambiar permisos)
    4. Intenta la exportacion de nuevo

    Si el problema continua despues de cambiar los permisos, es posible que tu servidor tenga poco espacio en disco. Puedes comprobarlo desde cPanel > Uso de disco, o pidiendo a tu proveedor de hosting que lo verifique.

    Saludos

    Plugin Author Yani

    (@yaniiliev)

    Hi!

    I hope you are well. The easiest way to do all this is to create a new WordPress website locally, onto your computer. Import the wpress backup, delete the sites that you do not need and then export again with the lean file. If you want to extract or browser wpress files you can do it with Traktor

    Plugin Author Yani

    (@yaniiliev)

    Hi there,

    Thanks for reporting this. The WPML Advanced Translation Editor relies on its own internal configuration and service connections that are separate from your site’s content. After a migration, WPML sometimes needs to be re-initialized to restore these connections.

    Here are the steps we’d recommend:

    1. Go to WPML > Settings and re-register your WPML site key (even if it shows as active)
    2. Navigate to WPML > Translation Management > Translation Editor and confirm the Advanced Translation Editor is selected
    3. Clear any object caches or transients (using WP-CLI: wp transient delete –all, or via a caching plugin)
    4. If the issue persists, deactivate and reactivate WPML and its add-ons, then re-enter your site key

    This is a known WPML behavior when the site URL or domain changes during migration – WPML’s translation service needs to re-authenticate with the new domain.

    That said, since this is a WPML configuration issue rather than a migration issue, the WPML support team would be best positioned to help if the steps above don’t resolve it. You can reach them at https://wpml.org/forums/

    If you have any questions about the migration itself, we’re happy to help here.

    Plugin Author Yani

    (@yaniiliev)

    Hi there,

    Thanks for reaching out! It sounds like you want to restore a backup of ae.prcnstore.com onto ag.prcnstore.com within your multisite network, so they become identical.

    This scenario, importing a single site backup into an existing subsite on a multisite network, requires our Multisite Extension, which handles all five multisite migration scenarios including this one. Since this is a premium product, we’re unable to provide setup assistance here on the ww.wp.xz.cn forums as per the forum guidelines.

    You can find the extension and full details here: https://servmask.com/products/multisite-extension

    We also have a step-by-step guide that covers exactly your use case: https://blog.servmask.com/wordpress-multisite-migration-guide/

    For any questions about the Multisite Extension, please reach out to our support team https://servmask.com/contact-support and we’ll be happy to walk you through it.

    • This reply was modified 2 weeks, 4 days ago by Yani.
    Plugin Author Yani

    (@yaniiliev)

    Thank you for the follow-up. We appreciate the effort to look into this, but we need to correct the record here.

    The Wayback Machine link you shared is from 2016. However, our records show your purchase was made in 2021. These are not the same product page.

    The 2016 page you linked lists a price of $79 and says “Use on any number of websites.” The product page at the time of your actual purchase in 2021 was priced at $99 and clearly states “Use on any number of websites that you own.” The distinction was explicitly communicated at the point of sale.

    We understand that licensing terms can feel like fine print, but “websites that you own” versus client websites is a meaningful and clearly worded distinction. It is the same distinction that separated the Personal plan from the Business plan.

    We are not questioning whether you found the plugin useful. Clearly you did, and we are glad it served your work well for years. But presenting a product page from five years before your purchase to suggest the terms were unclear is not an accurate representation of what happened.

    Our offer still stands. If you believe your situation was handled unfairly, our support team is ready to review your case individually. They will look at the actual license terms from your purchase date, the usage data, and any context you provide.

    Thank you.

    Plugin Author Yani

    (@yaniiliev)

    Hi @remakewarsaw,

    Thank you for taking the time to share your experience. We genuinely appreciate that you found All-in-One WP Migration useful enough to rely on it across development, staging, and client projects for what sounds like many years. That speaks to the value the plugin delivered for you and your clients.

    We do want to clarify a few things for the benefit of anyone reading this.

    Our FTP Extension (now part of All-in-One WP Migration Pro) was offered under two plans: a Personal plan (lifetime license) for use on your own websites, and a Business plan (monthly or yearly subscription) for use on client websites. These terms were clearly presented at the time of purchase. Using a Personal license across client projects is a violation of the license terms, and that distinction exists for a reason.

    We understand that after years of use, having a license revoked is frustrating. But consider the other side: if the plugin was purchased around 2019, that comes out to less than $10 per year. If your hourly rate is even $20, the plugin only needed to save you an hour or two each year to pay for itself many times over. The value you received over those years is real, and it was delivered in full.

    To be clear, we are not revoking lifetime licenses as a policy. A small number of licenses have been cancelled where our system identified a pattern consistent with misuse. Our detection uses multiple data points, including download frequency, geographic distribution, and the number of distinct sites a license has been activated on. When these signals, taken together, point to systematic abuse, we act on it.

    You are right that the Personal license does not include a dashboard to track individual site activations. That is a feature of the Business plan, which includes the tooling to manage use across client sites, precisely because it is designed for that use case.

    We take every case seriously. Our support team reviews each situation individually, including the license terms that were in effect at the time of purchase, the usage data, and any context the license holder provides. If you believe your case was handled in error, we encourage you to reach out to our support team directly so we can review it together.

    Thank you again for your years of using the plugin. We hope we can resolve this.

    • This reply was modified 3 weeks, 1 day ago by Yani. Reason: add link to contact customer support
    Plugin Author Yani

    (@yaniiliev)

    All-in-One WP Migration does not impose any upload size limit. The message you are seeing comes entirely from your web server/hosting provider’s PHP configuration, not from the plugin.

    You can verify this by trying the plugin directly here: https://ww.wp.xz.cn/plugins/all-in-one-wp-migration/?preview=1

    On this example, you can import a file as large as 2GB. The 300MB limit you are seeing is what your hosting allows, not what the plugin allows.

    If you need help increasing your server’s upload limit: https://help.servmask.com/knowledgebase/how-to-increase-maximum-upload-file-size-in-wordpress/

Viewing 15 replies - 1 through 15 (of 5,036 total)