Last post 14 hours 41 min ago

Posts last week 94

Average response time last week 34 min

All time posts 67911

All time tickets 10496

All time avg. posts per day 20

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.

#1432 – error in "sef urls" after update

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, 23 November 2015 17:40 UTC

itaym

after issue "#1377: Title problem after update" I update to the latest version "com_sh404sef_4.7.1.3144_full".
Now I get this error when I go to "sef urls"
PLEASE HELP

Incorrect key file for table './xxxx_jasdh213la2agxe3/ujz5v_sh404sef_urls.MYI'; try to repair it SQL=select u.*, pg.pageid as pageid, pg.id as pageidid, pg.type as pageidtype, pg.hits as pageidhits, count(a.alias) as aliases from ( select distinct u1.*, count(d.`id`)-1 as duplicates, count(m.`id`) as metas from ujz5v_sh404sef_urls as d, ujz5v_sh404sef_urls as u1 left join `ujz5v_sh404sef_metas` as m on m.newurl=u1.newurl WHERE u1.newurl <> "" AND d.oldurl=u1.oldurl AND u1.rank = 0 group by u1.`id`) as u left join `ujz5v_sh404sef_aliases` as a on a.newurl = u.newurl left join `ujz5v_sh404sef_pageids` as pg on pg.newurl = u.newurl group by u.newurl order by `oldurl` ASC

Monday, 23 November 2015 17:50 UTC

wb_weeblr

Hi

This is not an sh404SEF error. It's coming from your MYSQL server and seem to indicate that your database is corrupted or damaged.
As per the error message:

Incorrect key file for table './xxxx_jasdh213la2agxe3/ujz5v_sh404sef_urls.MYI'; try to repair it

you can surely repair it, for instance using phpmyadmin.

Rgds

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.