no login after updated to 1.5.1

Having trouble installing serendipity?
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Re: no login after updated to 1.5.1

Post by garvinhicking »

Hi!

Check your Transmit FTP tool, maybe this one is involved? Maybe you can use FileZilla instead?

When you edit the file in your texteditor, it looks normal?!

What's your URL again, if you open that file from your webpage inside the browser, what do you get?

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
3nd3r
Regular
Posts: 71
Joined: Tue Aug 19, 2008 12:58 pm
Location: NeoMadrid, Spain
Contact:

Re: no login after updated to 1.5.1

Post by 3nd3r »

Ok, I've started from the beginning on this process, so I've used Opera instead of Chrome and downloaded Serendipity 1.5.1 tar.gz.

Then I've downloaded and installed FileZilla for FTP. Uploaded and overwrite serendipity.

Then, I've downloaded db_update_1.5-alpha1_1.5-alpha2_sqlite.sql.zip archive you attached before, and unzipped and overwrite the one in my server.

Then I run fixperm and modified serendipity_config_local.inc.php

Then I went to my weblog (http://www.pajareo.com), I need to update. The next screen shows:

Code: Select all

Verify Installation Integrity
sql/db_update_1.5-alpha1_1.5-alpha2_sqlite.sql corrupt or modified: failed verification
and a little down:

Code: Select all

He encontrado los siguientes ficheros .sql que se necesitan ejecutar antes de que puedas continuar usando normalmente Serendipity:
._db_update_1.5-alpha1_1.5-alpha2_mysql.sql
that means that the script needs to use that file before continue using Serendipity...
So I click on the button "Yes, please" and...

that message appears again! :shock:

Code: Select all

- 
Mac OS X           2��ATTR;
/ You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 1
�����Y�Ycom.apple.quarantine0000;
/ You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '���' at line 1
4b31e5ab;
/ You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '4b31e5ab' at line 1
Google\x20Chrome.app;
/ You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'Google\x20Chrome.app' at line 1
The .sql file looks like this:

Code: Select all

create table {PREFIX}tempauthors (
  realname varchar(255) NOT NULL default '',
  username varchar(32) default null,
  password varchar(64) default null,
  authorid {AUTOINCREMENT} {PRIMARY},
  mail_comments int(1) default '1',
  mail_trackbacks int(1) default '1',
  email varchar(128) not null default '',
  userlevel int(4) {UNSIGNED} not null default '0',
  right_publish int(1) default '1',
  hashtype int(1) default '0'
) {UTF_8};

INSERT INTO {PREFIX}tempauthors 
(realname,username,password,authorid,mail_comments,mail_trackbacks,email,userlevel,right_publish) SELECT 
realname,username,password,authorid,mail_comments,mail_trackbacks,email,userlevel,right_publish FROM {PREFIX}authors;
DROP TABLE {PREFIX}authors;

create table {PREFIX}authors (
  realname varchar(255) NOT NULL default '',
  username varchar(32) default null,
  password varchar(64) default null,
  authorid {AUTOINCREMENT} {PRIMARY},
  mail_comments int(1) default '1',
  mail_trackbacks int(1) default '1',
  email varchar(128) not null default '',
  userlevel int(4) {UNSIGNED} not null default '0',
  right_publish int(1) default '1',
  hashtype int(1) default '0'
) {UTF_8};


INSERT INTO {PREFIX}authors 
(realname,username,password,authorid,mail_comments,mail_trackbacks,email,userlevel,right_publish,hashtype) SELECT 
realname,username,password,authorid,mail_comments,mail_trackbacks,email,userlevel,right_publish,hashtype FROM {PREFIX}tempauthors;
DROP TABLE {PREFIX}tempauthors;
When I try to open this file in my browser I get

Code: Select all

Forbidden

You don't have permission to access /sql/db_update_1.5-alpha1_1.5-alpha2_sqlite.sql on this server.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.7a mod_bwlimited/1.4 PHP/5.2.11 Server at www.pajareo.com Port 80
Please, what can I do?
Try not. Do, or do not. There is no try.
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Re: no login after updated to 1.5.1

Post by garvinhicking »

Hi!

Please send me a PM with FTP access to your site so that I can have a look...

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
3nd3r
Regular
Posts: 71
Joined: Tue Aug 19, 2008 12:58 pm
Location: NeoMadrid, Spain
Contact:

Re: no login after updated to 1.5.1

Post by 3nd3r »

Done!

Thanks a lot!
Try not. Do, or do not. There is no try.
3nd3r
Regular
Posts: 71
Joined: Tue Aug 19, 2008 12:58 pm
Location: NeoMadrid, Spain
Contact:

Re: no login after updated to 1.5.1

Post by 3nd3r »

BTW, I've found that piece of strange code! It's inside ._db_update_1.5-alpha1_1.5-alpha2_sqlite.sql :shock:
Try not. Do, or do not. There is no try.
garvinhicking
Core Developer
Posts: 30022
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany
Contact:

Re: no login after updated to 1.5.1

Post by garvinhicking »

Hi!

Those . files are evil, where do they come from? Make sure you never upload them.

BTW: You don't even use SQLIte! You use MySQL :-D So this problem actually doesn't evel apply to you :)

But at least I fixed your SMF problem - http://www.pajareo.com/SMF/ ;)

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/
3nd3r
Regular
Posts: 71
Joined: Tue Aug 19, 2008 12:58 pm
Location: NeoMadrid, Spain
Contact:

Re: no login after updated to 1.5.1

Post by 3nd3r »

garvinhicking wrote:Those . files are evil, where do they come from? Make sure you never upload them.
I've deleted them and did the upgrade fix, and now I can login! The only thing was a message showing something about 'duplicate column hashtipe' that I'm sorry, but I didn't copy...
garvinhicking wrote:BTW: You don't even use SQLIte! You use MySQL :-D So this problem actually doesn't evel apply to you :)
Yes, but the error was there... Strange...
garvinhicking wrote:But at least I fixed your SMF problem - http://www.pajareo.com/SMF/ ;)
Thank you! :)

Thanks a lot!
Try not. Do, or do not. There is no try.
lama
Regular
Posts: 13
Joined: Tue Jan 19, 2010 6:35 am

Re: no login after updated to 1.5.1

Post by lama »

sry have to add to the thread, no login possible for me after upgrading from 1.2.1 to 1.5.1, too.
after reading this thread i checked my mysql-tables with phpmyadmin and found the hashtype missing in the s9y_table authors.
so i opened sql/db_update_1.5-alpha1_1.5-alpha2_mysql.sql and executed (via phpmyadmin, too) the 2 commands in it

Code: Select all

ALTER TABLE s9y_authors ADD COLUMN hashtype int(1);
ALTER TABLE s9y_authors CHANGE password password VARCHAR(64) NOT NULL;
all happy now, login possible again.
dont know what went wrong though..
Post Reply