Last post 5 hours 23 min ago

Posts last week 94

Average response time last week 34 min

All time posts 67874

All time tickets 10492

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.

#4527 – Error database after update to version 4.13.1

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.

Thursday, 18 January 2018 23:17 UTC

sprspr2

Hi,

On a Joomla 3.7.5 website I just updated sh404sef 4.10.0 to version 4.13.1 (a preparation for updating to Joomla 3.8.3)

The update was successfully, the component seems to work properly, but there was one alarming post update message:

Error while upgrading the database: Unknown column 'metadesc' in '#__sh404sef_metas'

I was thinking this metadesc column might be a remainder from an old sh404sef version (I already used sh404sef in Joomla 1.5, the ancient free version). To check this assumption I did a fresh install of sh404sef 4.13.1 on another website. And I discovered that it's correct to have a column 'metadesc' in '#__sh404sef_metas.

So I don't understand why I did get the error message.
Is it a false alarm?
If not, what went wrong?

Please advise.

Kind regards,
Udo

Friday, 19 January 2018 08:09 UTC

wb_weeblr

HI

Totally a false alarm. This column has been there for many years, since Joomla 1.0 actually. It's still there and is used all the time.

If the column is there, then all is fine. Without it, you would get a large amount of errors all across the board. It's been reported another time, so I think this is due to a very rare combination of circumstances regarding the MYSQL server, Joomla and/or previous sh404SEF versions in use. I will revisit the installation script again to try identify where this could happen.

Certainly nothing to worry about though.

Rgds

Saturday, 03 February 2018 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.