By Elizabeth Deakin on Monday, 20 June 2016
Posted in Technical Issues
Replies 19
Likes 0
Views 450
Votes 0
Hello
a few weeks ago I purchased Easyblog and with your help we imported all the posts.

It's all been looking great, but I just finally switched off the old url, redirecting all traffic to the new site to find that all the photos have gone!

I suspect that the photos were all still pulling from the old website.

How do we resolve this please? At the moment I have 104 blog posts with no photos......

L
I've checked on your site, it seems like your blog content already stored your old site domain name, it quite hard to revert back to your current domain.

By the way, what my ideas is move all of your photo file into your current Joomla root folder e.g. JoomlaFolder/wp-content/uploads/2016/04/website-March-2016.jpg <- move all of your file into this wp-content folder.

Then override the http://www.karibunyumbani.org to use your current site domain name.
·
Monday, 20 June 2016 23:45
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Alex - it sounds like that would work - can you do this for me?

Your team did the import for me as it didn't work when I did it - that's why it wasn't spotted earlier.
·
Monday, 20 June 2016 23:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Will you be able to do this today please?
·
Tuesday, 21 June 2016 03:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Elizabeth,

I am sorry for the delay of this reply is because what I last reply already at midnight 12am last night, hope you understand.

Hi Alex - it sounds like that would work - can you do this for me?

Your team did the import for me as it didn't work when I did it - that's why it wasn't spotted earlier.

Regarding this you have to do it manually by yourself is because the blog content already stored your old domain name into blog post every single image.

1. Move all of your photo file from your old site .../wp-content/uploads/2016/04/website-March-2016.jpg (under wp-content folder) to your current Joomla site (Joomla root folder).

2. You have to manually edit all the existing post `old domain name` inside the image content to use your current domain site http://whmtuk.com, because you already changed your domain.
·
Tuesday, 21 June 2016 10:46
·
0 Likes
·
0 Votes
·
0 Comments
·
So, your team did the import for me, didn't do it correctly, and now I have to do hours of work to correct your mistake?
·
Tuesday, 21 June 2016 16:15
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Elizabeth,

So, your team did the import for me, didn't do it correctly, and now I have to do hours of work to correct your mistake?

I am deeply saddened by this statement. However, the migrator did migrated all the content correctly as what you provide us with your wordpress.xml file in previous post, you can refer on my attached screenshot below.

The reason why it didn't get correctly the photo path is because your old site is use this domain name http://www.karibunyumbani.org instead of whmtuk.com , so all of your blog content image path get affected.

By the way, may i know can I have permission to re-migrate all the blog post in your site? Because I would like to modify this xml file postsKN.wordpress.xml inside all the http://www.karibunyumbani.org domain to use your current domain name whmtuk.com before I run the migrator from backend.

Also can you provide us with your following details?
1. Joomla backend Superadmin access
2. FTP access for your new site (whmtuk.com)
3. PHPMYADMIN access
4. Old site FTP access (http://www.karibunyumbani.org) because I would like to move all of your existing photo data from your old site to new site.
·
Tuesday, 21 June 2016 20:43
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Arlex

Hmm, the site was always whmtuk.com - the karibunyumbani.org was the legacy site.

I can give you back end access to the Joomla site, but the old KN site was written and controlled by a 3rd party and we don't have access to that. It doesn't even have its domain anymore as it's been transferred to us. It's when the domain name moved across that the problem presented itself

I'm going to try something else first: my plan is to use Akeeba to spin up a new instance of the site on the karibunyumbani.org domain - with any luck we can then put the photos in folders which roughly correspond to those which existed in the old set-up.

I cannot go in manually and change every single photo url - there are probably 500 photos and I'll be here all night

Do you want me to try that first and then get you to help me with the clean up? Possibly quicker than trying to manipulate what we have right now?

L
·
Tuesday, 21 June 2016 21:51
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Elizabeth,

Yes, hopefully you can get back your photo file data from your karibunyumbani.org domain, and transfer it to your current Joomla site.

And these every single photo URL we will try our best run some script to update your existing blog image URL to use your current domain site URL.

If that is not possible, then we have to help you re-migrate again.

I will replace all the karibunyumbani.org domain to use whmtuk.com before we re-migrate again.

By the way, keep us update then.
·
Tuesday, 21 June 2016 23:53
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Arlex

OK, so I have the new site up and running - same problem at the moment.

I used your migrator to grab all the existing posts from the old wordpress site - am I given to understand that this migrator file doesn't have any of the photos in it?

L
·
Wednesday, 22 June 2016 04:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Elizabeth,

I am sorry for the delay of this reply,

Currently the migrator only migrate all of your blog content based on your xml file instead of automatically move all of your photo file from your old wordpress file directory .../wp-content/uploads/xxxx to your Joomla root folder.

Can I have your old wordpress site FTP directory access which still contain this folder photo file .../wp-content/uploads/xxxx? So that I can help you manually move all these photo file into your Joomla root directory folder?
·
Wednesday, 22 June 2016 10:40
·
0 Likes
·
0 Votes
·
0 Comments
·
Arlex

I keep telling you: I don't have access to the old site!

Your migrator promised to "move all the content" it says nothing about NOT moving the photos - there's no warnings to advise this, the guy on your team who did the move didn't check where the photos were.

Do you know how much trouble this has caused?

L
·
Wednesday, 22 June 2016 16:16
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Elizabeth,

I am sorry for the delay of this reply and I thought you have trying to get the access from your old KN site,

May i know is it don't have other way to contact with your 3rd party provider and see is it can get the access download this old wordpress file directory .../wp-content/uploads/xxxx ?
·
Thursday, 23 June 2016 10:56
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello
I now have back-end access for the OLD account.
I'll look and see
L
·
Thursday, 30 June 2016 05:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Elizabeth,

That was great !

May i know there still exist these folder file? .../wp-content/uploads/xxxx
·
Thursday, 30 June 2016 10:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Arlex
Sorry for the delayed response - I have the photos now and have uploaded them into the folders - this seems to be working, but on every post I have a large placeholder at the very beginning - not something that should be there as far as I can see.

Is there a way to remove this please?

e.g. the newest post is called "Newcomers", the post itself is fine, and the image for it is showing, but before all of that is a large placeholder which I don't understand. It is present on every post. Obviously, we need to remove this.

You can get access to the site now on the karibunyumbani.org address (I remade the site using this domain name)

So for access to the admin area please go to karibubyumbani.org/administrator - your username is blogguru and the password is applepie216. Please remove these details from the public thread as soon as you can

Many thanks

L
·
Monday, 04 July 2016 06:18
·
0 Likes
·
0 Votes
·
0 Comments
·
Oh wait, I found the setting which was causing that. All fixed now. I've disabled your superuser access as I didn't like it being published on a public forum.

Please could you do one final thing for me and update my licence to serve the domain karibunyumbani.org rather than whmtuk.com?

Many thanks

L
·
Monday, 04 July 2016 07:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Elizabeth,

I am sorry for the delay of this reply,

Glad to heard your issue resolved.

By the way, your current license support domain already updated to karibunyumbani.org

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry.
·
Monday, 04 July 2016 10:27
·
0 Likes
·
0 Votes
·
0 Comments
·
erm, it's OK giving me a few gentle reminders, but maybe I can give you some of my own:

1. I was absolutely clear at the outset that I was creating a new website under a different URL - your team said that they could migrate everything and signed off the migration as complete - at no point did you mention that photos would need to be moved separately, or that there were any complications at all in doing this.

2. this could have caused a catastrophic failure of my project and I'm appalled.

Your documentation/instructions need to be updated to reflect this. As it is, I've had to fix it myself rather than getting help from you.

I've now just come across another issue, not mentioned in your documentation, which is that apparently, Facebook autoposting will not work without ssl. you've let me do more work before mentioning this, far, far into the work.
Why can't you put some prerequisites on your documentation at the beginning?

Working with easyblog repeatedly feels like I'm doing a jigsaw with only half the pieces - it's awful.

Yes, before you say it. I will post a new thread about Facebook. Mailchimp to come as well. Not looking forward to that. My client has been delayed by a month by issues caused by you. It's not good.
·
Tuesday, 05 July 2016 01:28
·
0 Likes
·
0 Votes
·
0 Comments
·
I am sorry for any inconvenience caused.

By the way, thanks for your feedback, we will update our documentation regarding this.
·
Tuesday, 05 July 2016 15:52
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post