• Home
  • Get help
  • Ask a question
Last post 33 min ago
Posts last week 141
Average response time last week 4 hours 42 min
All time posts 67803
All time tickets 10477
All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#5639 – Can't import JoomSEF data

Posted in ‘sh404SEF’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Monday, 04 March 2019 11:14 UTC
jfquestiaux
 Hi Yannick,

I have to import existing JoomSef data into sh404SEF and this is not working: I get a "Error communicating with server, aborting." message.

Reading the doc, I understood that the imported tables have to be on the same server as the target tables, but reading some older tickets, it seems that the site has to be on the same server as the database. Is that correct?

If so, that's why it is not working on my dev site since the site is not on the same server as the database.

But I moved then on localhost (using MAMP PRO on Mac) and I have the same problem so, what should I do?

Joomla!, sh404SEF and JoomSEF (free version) are all at the latest version.

Best regards,
Jean-François
 Better Web - Agence Joomla!
Monday, 04 March 2019 11:25 UTC
wb_weeblr
Hi

Reading the doc, I understood that the imported tables have to be on the same server as the target tables, but reading some older tickets, it seems that the site has to be on the same server as the database. Is that correct?
Yes, the server has to be the same. The original data can be on a separate database but on the same database server as the one Joomla is connecting to. We can only connect to the database through Joomla, so the current site mysql server is the only one we have access to.

However, there can be several databases on that server and the JoomSEF tables can be in another database. The first option in the settings on the JoomSEF import tab is "Source database" and it will list which databases the importer can access. JoomSEF tables must be in one of those databases.

If so, that's why it is not working on my dev site since the site is not on the same server as the database.
Yes.

But I moved then on localhost (using MAMP PRO on Mac) and I have the same problem so, what should I do?
Copy the JoomSEF tables from the original server to the new ones using PHPMyadmin for instance. You do not need JoomSEF at all, just the db tables.

Best regards
 
Monday, 04 March 2019 13:39 UTC
jfquestiaux
Thanks for the response but unfortunately there is still a problem:

The tables ARE on the same server (actually they are even in the same database) but I still get the error. I think I tried every possible combination (local, remote, in the same db or in separate db), nothing works and I can't even find where the error is generated.

It seems however that it's happening just after sh404 is disabled by the plugin.

It's a new install so there are still no data in the sh404 tables. Is it a problem?
 Better Web - Agence Joomla!
Monday, 04 March 2019 13:54 UTC
wb_weeblr
Hi

It should not be there might be many additional reasons for that. I would suggest:

- set Joomla error reporting to maximum
- check your PHP log for any error that could be related to the importer plugin.

Best regards

 
Monday, 04 March 2019 14:06 UTC
jfquestiaux
No PHP error but the console reports an error in "bundle.min.js" (although the message is stille the same: "Error communicating with server, aborting."
 Better Web - Agence Joomla!
Monday, 04 March 2019 15:29 UTC
wb_weeblr
Hi

No PHP error but the console reports an error in "bundle.min.js"
What kind of error? Exactly?

Best regards
 
Monday, 04 March 2019 15:40 UTC
jfquestiaux
As I said, it does not say. only underline script starting at "return console.error(a),u(e,a),void p(e)}d(e,t)}function l(e,t){console.log("Ajax request failure")..." till the end of the file.
 Better Web - Agence Joomla!
Monday, 04 March 2019 18:35 UTC
wb_weeblr
HI

OK, the importer is a little piece of convenience software, it does not have much in terms of error reporting. Could you please provide us with superadmin credentials to your website. You can create a temporary account, and delete it afterward, but it must have superuser level.

Thanks and regards
 
Tuesday, 05 March 2019 06:45 UTC
jfquestiaux
I've created you a Super User account:

User: xxxx
Password: xxxx

URL: https://xxxx.fr/

It's protected by .htaccess (but I've tested without, also locally and still have the error) :
User : xxxx
Password: xxxx

 Better Web - Agence Joomla!
Tuesday, 05 March 2019 10:20 UTC
wb_weeblr
Hi

Like I said, the message is a bit generic as the extension is just a convenience. I found that there's actually no error, simply the plugin does not find any data to import:

{"success":true,"message":null,"messages":null,"data":[{"id":"a802e0f8d74b12cd9c5ba4085418594add2afe06","next_step":"continue","data_type":"","done":{"url":0,"meta":0,"redir":0,"alias":0},"processed":{"url":0,"meta":0,"redir":0,"alias":0},"total":{"url":"6392","meta":"6392","redir":"970","alias":"0"}}]}


It says there are 6392 URLs and 970 redirections in total ("total":{"url":"6392","meta":"6392","redir":"970","alias":"0"}), but it did not process any of them ("processed":{"url":0,"meta":0,"redir":0,"alias":0})

I would need to dig further but I can't do that on a remote site. Can you export the content of the JoomSEF DB tables to a .sql file (with PHPMyadmin or similar), zip them and upload them to that [private online folder].

I can them load them on a local machine and see why no URL qualifies for import more easily.

Best regards
 
Tuesday, 05 March 2019 10:56 UTC
jfquestiaux
There are indeed all these URLs to import. I uploaded them in the indicated folder.
Thank you for looking into this issue.

Best regards,
Jean-François
 Better Web - Agence Joomla!
Wednesday, 06 March 2019 08:36 UTC
wb_weeblr
Hi,

The data import fines for me:



Next step is that I take an akeeba backup of the site and run the import on the actual site. You do not run many plugins that could interfere (and I tried disabling some of them) but we are now left with only 2 options:

- some extension on the site
- the server (ie php setup)

OK?

Best regards


 
Wednesday, 06 March 2019 09:06 UTC
jfquestiaux
It's OK by me.

I can disable the protected folder .htaccess if you think that may cause an issue.
 Better Web - Agence Joomla!
Wednesday, 06 March 2019 09:08 UTC
wb_weeblr
Hi

It should not have any effect although it's always worth a try. I'll do the backup anyway.

Best regards
 
Wednesday, 06 March 2019 09:10 UTC
jfquestiaux
I deactivated it while you are working.
 Better Web - Agence Joomla!
Wednesday, 06 March 2019 09:35 UTC
wb_weeblr
Hi,

So it's something on the server: the restored akeeba backup imports fine! I'm not sure what's happening to be honest, all of this is pretty simple code, there's nothing special to it.

The only difference with my local setup are:

- MariaDB version is 5.5.5 on your server while I'm using MySQL 5.6 (and on my way to upgrade to 5.7). However the version number is strange it says "5.5.5-10.0.35". So not sure exactly which version you're running. I've never used MariaDb but as far as I know, it's fully compatible with MYSQL.
WOuld be worth checking the MYSQL error log if you can access.

- PHP is the same
- If you have any firewall, security extension on the server, maybe try disabling that or at least checking the logs.

Maybe a workaround at this stage would be to copy the site onto another server and import the sh404SEF tables back. As I have done just that, I have uploaded a zipped SQL dump of those tables into the same online folder. You can download the file there and import into your database, that should do the trick for now.

Best regards

 
Wednesday, 06 March 2019 09:53 UTC
jfquestiaux
Well, thank you for the tests.
The strange thing is that I tried the import also locally and had the same issue. And on the local server (MAMP PRO), it's MySQL 5.6.38 and different settings for PHP and Apache.
So I think it's more something coming from the site, even though I started this migration (coming from J! 2.5) on a fresh J! 3.9.3 install.
I guess what I could do is test on a bare J! install and see what's happening.

However, in the meantime, to save me some time, I'd appreciate if you have a successful import in sh404SEF tables that you could send me. I will do the tests later and let you know.

Best regards,
Jean-François
 Better Web - Agence Joomla!
Wednesday, 06 March 2019 14:53 UTC
wb_weeblr
Hi

I'd appreciate if you have a successful import in sh404SEF tables that you could send me. I will do the tests later and let you know.
See my previous message:

As I have done just that, I have uploaded a zipped SQL dump of those tables into the same online folder. You can download the file there and import into your database, that should do the trick for now.


Best regards
 
Wednesday, 06 March 2019 14:55 UTC
jfquestiaux
Sorry, I read the message too fast. I just downloaded the files.

Thanks again for your assistance.
 Better Web - Agence Joomla!
Wednesday, 06 March 2019 14:59 UTC
wb_weeblr
i

You're welceom. Very strange that you have the same issue locally. I'm on windows so no MAMP for me but if ALMP settings made a difference, you would see an error in PHP logs and/or MYSQL logs. I'll try again on an online server, ie linux.

Best regards
 
Monday, 11 March 2019 09:51 UTC
wb_weeblr
Hi,

Tried on a linux server but did not have any issue. I will leave this ticket open in case you need to add something. It will automatically close in 2 weeks if no further comment is made.

Best regards
 
Tuesday, 26 March 2019 05:34 UTC
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.