AdmiralRob

Alright, I solved it. The issue was that some of the images were greater than 512kb which was the php limit on the server. So although my list was well below that, SOME of the images were too high and therefore I had to remove those ones before reimporting. Than it all worked.

Alright, More info on it now:

It’s the images somehow. the images in my import are listed as simple url. When I tell it not to import that column, it comes through just fine. But if I tell it to use the images, that’s when it stalls out. I’ve got the images in a folder on the same server. like this:

https://new.alaskabooksandcalendars.com/import/1607894945.jpg

Any ideas on this?

Hey Brian,

What a happy accident! it looks like you’re plugin will probably work for me better than my crazy edits ??

Thanks!

Ok, so I unchecked that and reposted the post. Now it moved over the media file to this url:
https://bowheadsupport.uicalaska.com/wp-content/uploads/sites/3/2018/05/6700ArcticSpur.jpg

but linked it with this link:
https://bowheadsupport.uicalaska.com/wp-content/uploads/sites/3/2018/05/6700ArcticSpur-600×311.jpg

should I just post a link to the broadcast debug dump here? or send it to you another way? (is that not a security issue?)

Wow, you replied much faster than I was expecting ??

So, when the parent sends the blog off to the child site, it updates the image url to:

https://bowheadsupport.uicalaska.com/wp-content/uploads/sites/3/2018/05/6700ArcticSpur-600×311.jpg

but the image exists here:
https://bowheadsupport.uicalaska.com/wp-content/uploads/sites/3/2018/05/6700ArcticSpur_7674686.jpg

It’s just that random number at the end that’s off. Is that a setting problem?

Looks like it’s not updating the image file name itself properly.

The image it moves over to the child site library looks like this:

https://bowheadsupport.uicalaska.com/wp-content/uploads/sites/3/2018/05/6700ArcticSpur_7674686.jpg

if you open up user-meta-manager.php and go down to line 2841, you’ll see that he does an add_action into the admin footer. This adds in javascript to generate the user fields with an ajax request. I’m not great with javascript so I can’t find the specific problem in there, but I was able to comment the add_action line out and it works fine. I don’t get the custom meta on the new user form, but I didn’t care about it being there anyway.

Hopefully the author can et this fixed soon.

I have the same problem here.

This makes the plugin entirely unusable for me. And I’m sure we’re not alone in this.

On Chrome Version 43.0.2357.81 (64-bit) It doesn’t even show the meta fields generating, it just sits there and spins until it crashes and I have to kill the page.

on Firefox 39.0a2 it actually shows the fields populating endlessly, so at least I can stop that and use the page.

Safari does the same as chrome.

WordPress: 4.2.2
UMM: 3.4.6

Wow! Not a soul knows anything about this issue?

Has no one ever tried to do it before?

Same issue here!

Turns out that error was actually from setting the admin counter option (where it adds one to the counter for admins).

The widgets page is actually a standard screen you should have in any wordpress installation. If you don’t have it, I doubt it has anything to do with this plugin.

Thanks for posting this… so I found the code, and in the url it says code=###… etc…

Does it just need that code? because that doesn’t seem to be working for me either.

Alright, so we do have the latest version. But it’s still using the wrong email receipt.

Thank you for your quick response!

I have 1.01, and it’s Pro, on WordPress 3.6.

What’s the latest version?