Title: Plugin improvement
Last modified: November 4, 2021

---

# Plugin improvement

 *  Resolved [Ilari Arovuo](https://wordpress.org/support/users/iarovuo/)
 * (@iarovuo)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/plugin-improvement-3/)
 * Hi [@stoyangeorgiev](https://wordpress.org/support/users/stoyangeorgiev/),
 * I love the plugin, when it works!
 * Through number of migrations conducted, I have found two issues, where migration
   fails miserably.
 * 1) The origin server does not have PHP memory settings at all. Thus, resulting
   to a plugin crash without any visible trace of the reason in the admin UI.
    –
   This is plugin is not very informative about these details, or what it is actually
   doing, so it’s near impossible to troubleshoot what might be the issue. – After
   increasing user and admin PHP memory to 256M the plugin worked. – This check 
   should be fairly simple with `ini_get('memory_limit');` or similar and even fix
   on the fly with `@ini_set('memory_limit', '256M');` or similar.
 * 2) One of the migrated website had apparently gone through several iterations
   through it’s lifecycle, and had TWO options tables in DB. The tables were with
   different prefix, but got the migrator failing miserably. and again, without 
   a single clue in admin UI or debug logs what the heck went wrong.
    – Took me 
   literally days to find this out! – After removing the obsolete, wrong prefixed
   options table, the migrator worked perfectly. – I have not taken a look at the
   code, but would assume the plugin uses ‘too simple’ method to find details in
   the options table, and does not consider the exactly right table, and the table
   prefix actually in use with the current installation. – This should be fairly
   easy fix to use something like `$table_name = $wpdb->prefix . "options";` to 
   workout the details with correct table, always.
 * 3) The logging and information provided in the admin UI is way too little.
    –
   We want to know what is the source IP, destination IP, protocol/port, and what
   files it is trying to write, etc preferably in the admin UI – These details would
   be super helpful when something goes wrong.
 * Do note that, when ever these migrations are being done, there are always some
   DNS updates and propagation topics – and it can get extremely confusing when 
   something isn’t working, and there is absolutely no clue what went wrong.

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Author [Elena Chavdarova](https://wordpress.org/support/users/elenachavdarova/)
 * (@elenachavdarova)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/plugin-improvement-3/#post-15040149)
 * Hello [@iarovuo](https://wordpress.org/support/users/iarovuo/),
 * Thank you for the feedback!
 * We will consider improvements on all topics you have listed here.
 * Best Regards,
    Elena
 *  Thread Starter [Ilari Arovuo](https://wordpress.org/support/users/iarovuo/)
 * (@iarovuo)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/plugin-improvement-3/#post-15041088)
 * Thank you [@elenachavdarova](https://wordpress.org/support/users/elenachavdarova/).
   
   You may close this thread.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Plugin improvement’ is closed to new replies.

 * ![](https://ps.w.org/siteground-migrator/assets/icon.svg?rev=3447692)
 * [SiteGround Migrator](https://wordpress.org/plugins/siteground-migrator/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/siteground-migrator/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/siteground-migrator/)
 * [Active Topics](https://wordpress.org/support/plugin/siteground-migrator/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/siteground-migrator/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/siteground-migrator/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Ilari Arovuo](https://wordpress.org/support/users/iarovuo/)
 * Last activity: [4 years, 6 months ago](https://wordpress.org/support/topic/plugin-improvement-3/#post-15041088)
 * Status: resolved