Terry Arthur

answered here: https://www.ads-software.com/support/topic/gallery-images-problem-2/

This works for me. Substitute my sizes for yours and remove true and the last comma if you don’t want the images cropped to fit.

add_theme_support( ‘post-thumbnails’ );
add_image_size( ‘post-thumbnail size’, 870, 420, true );
add_image_size( ‘post-thumbnail size’, 250, 130, true );

then regenerate your thumbnails via wpcli or a plugin

This works for me. Substitute my sizes for yours and remove true and the last comma if you don’t want the images cropped to fit.

add_theme_support( ‘post-thumbnails’ );
add_image_size( ‘post-thumbnail size’, 870, 420, true );
add_image_size( ‘post-thumbnail size’, 250, 130, true );

then regenerate your thumbnails via wpcli or a plugin

I think I remember having this same issue at first. For some reason pages are imported with a faulty post type, article, I think if I remember correctly.

It has been a while but I am pretty sure all I had to go into PHPMyAdmin and change the post type to post for the imports to show up.

Something like this should work, as long as I have remembered the errant post type correctly, just change the db prefix if needed:

UPDATE wp_posts SET post_type = ‘post’ WHERE post_type = ‘article’;

Hope this helps.

It’s the same error, you still don’t have enough memory allocated. Unless you do what I, or anyone for that matter, ask there isn’t much I can do to help. Here’s the ask again:

“Have you tried importing just one page? Are you using a Windows server? Once you have a meeting with your developer if you can provide more detailed information about the resources available to the server, the site and plugin config, plugins installed and activated during the import, screen errors, error logs, steps to reproduce the error etc. we will get to the bottom of this much sooner.”

Just because it is a dedicated server doesn’t mean it has the available resources you need to accomplish the import or that it is configured correctly to utilize them even if they are available.

Have you tried importing just one page? Are you using a Windows server? Once you have a meeting with your developer if you can provide more detailed information about the resources available to the server, the site and plugin config, plugins installed and activated during the import, screen errors, error logs, steps to reproduce the error etc. we will get to the bottom of this much sooner.

I will have to politely decline the call but I am happy to help for free via these forums as my schedule permits so that anyone that comes along later with a similar issue can benefit from this thread.

Let me know how I can help,

Terry Arthur

see my answer in your dupe post https://www.ads-software.com/support/topic/html-conversion/

Hello fellow Floridian!

First I want to say I really understand your frustration and I am going to try and help you because this is a community and I have been helped here many times and I want to pay that back through helping you. However, let’s be honest attempts to shame the developer of a fantastic FREE!!! plugin or run down the community here for not responding on your schedule will usually get the same results as you have had up to this point. Everything has constraints and free technical support has the constraint of being delivered when someone finds some free time and out of the goodness of their heart decides to help someone else. If you need help on your schedule hire a developer(like the author of the plugin) to fix things for you. I apologize for the lecture but I was really put off by the tone of your last post.

Second, don’t lose hope! The hard thing about hard things is just that. I have used this plugin to import over 10,000 pages and it worked fine with some tweaks to my server(PHP) and site(wp-config) configuration. It took me what felt like a hundred thousand tries to get it right though. So what you are trying to accomplish can most likely be done.

How much memory is allotted to PHP? It appears from the error message to be ~512MB. Have you tried setting the limit to say 1024MB? That is the value that worked for me. I also needed to add a couple of defines to my WordPress config file:

define( ‘WP_MEMORY_LIMIT’, ‘1024M’ );
define( ‘WP_MAX_MEMORY_LIMIT’, ‘1024M’ );

I ran WordPress with no plugins, other than the importer, activated so that reduced the memory load too.

I also had to increase the execution timeout and a couple of other setting that do not come to mind right now but let’s start with the memory issue and work from there.

If increasing resources doesn’t help then enable verbose PHP error reporting and turn on debug in WordPress and report back with the errors and maybe we can get you moving forward. The whois that told me you were in Florida also tells me you are using InMotion Hosting and that probably means you are on a shared server which may not allow you to utilize so much of the server’s resources without choking and timing you out so if that is the case you will probably need to change your hosting plan.

I just noticed another post about this so I am going to link to this answer in that post.

Let me know how I can help,

Terry Arthur

First, Check your .htaccess file. You may have uploaded the one from your local directory which might not(probably won’t) work on your live server.

Also, check your permissions and ensure folders are 755 and most files are 644. I say most since you may want more restrictive permissions, like 444, on sensitive files like .htaccess or wp-config.php. You may have bad permissions on some of the uploaded files.

If that doesn’t work you can always use the WordPress export tool to export all the content and media from your old site and then use the import tool on the new site to import the .xml file you generated with the export.

Forgot to mark this solved.

So I figured this out. Turns out there is some disambiguation by PHP I wasn’t aware of.

STRTOTIME Note:
Dates in the m/d/y or d-m-y formats are disambiguated by looking at the separator between the various components: if the separator is a slash (/), then the American m/d/y is assumed; whereas if the separator is a dash (-) or a dot (.), then the European d-m-y format is assumed. If, however, the year is given in a two digit format and the separator is a dash (-, the date string is parsed as y-m-d.
To avoid potential ambiguity, it’s best to use ISO 8601 (YYYY-MM-DD) dates or DateTime::createFromFormat() when possible.

The site I was importing from was displaying the dates using dashes and not slashes and STRTOTIME was assuming they were European but the site is in the US so it was necessary to change the site I was importing from to use / instead of – and then reimport all the pages. After that everything went great for 1,398 posts, images, attachments, tags everything.

This is a fantastic plugin and the only issue was with something I didn’t know about PHP.