(un)publishing or deleting an item in EasyBook

[Tschai]

(un)publishing an item from EasyBook in the backend generates the next error:
Unknown column 'id' in 'where clause' SQL=UPDATE jos_easybook SET published = 0 WHERE (id=0)

Deleting an item from EasyBook in the backend generates the error:
Item can not be removed

[serzhinio]

I use Easy Book 2.0.0.Rc3 
Now I can't delete any message from it.
I just see the next error
Notice: Undefined property: stdClass::$id in /.../com_easybook/views/easybook/tmpl/default.php on line 36

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 38

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 36

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 38

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 36

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 38

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 36

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 38

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 36

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 38

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 36

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 38

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 36

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 38

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 36

Notice: Undefined property: stdClass::$id in /..../com_easybook/views/easybook/tmpl/default.php on line 38


Is anybody know how solve this problem?

Thanks

[FW]

The same problem here!

Message: Unknown column 'id' in 'where clause' SQL=UPDATE jos_easybook SET published = 0 WHERE (id=0) after unpublishing.
Also deleting messages is not possible.

I'm using:
Joomla 1.5.7
EasyBook 2.0.0 RC3

Hoping for a quick solution...

[FW]

It's working!!!

I looked at two different installations, one working and the other one not.
I found in PhpMyAdmin that in 'jos_easybook' the key-field was called "gbid" in the installation that didn't work, and "id" in the installation without errors.

Changing the name of the field did the trick!

Now I also see differences in other fields:
* 'gbeditdate' (I think it's not used anymore)
* 'gbdate' has DATETIME as Type, and in the other one it's VARCHAR. (VARCHAR is working with my installation, but in the the other one DATETIME is working. Changing type gives problems, so beware!)

It looks to me like I missed a conversion with one of the updates....
Maybe Achim can tell how to turn the other fields (gbeditdate and gbdate) to normal, so I won't get any probems with future updates?

[serzhinio]

Can you describe this operation more detailed. Where I need change this data.
Thanks

[FW]

This is not in Joomla, but in your MySQL-database management system (my provider uses PHPmyAdmin).

* in PHPmyAdmin I click on jos_easybook
* now you can see all fields used for jos_easybook
* in my installation the first field was called "gbid" instead of "id", so click the pensil icon for "gbid"
* now you can change the name of the field to "id", and click save.

I hope this works for you too....

[David [snipersister]]

Okay guys, after reading your error messages, i know what causes your problems: you migrated from Joomla 1.0 and didn't use our migration plugin which changes the column "gbid" to "id" in the easybooks database table (jos_easybook).
When you change this by hand (as already pointed out by FW in the last post) the book should work like a charm.

Best regards
David

[FW]

Thanks for your reply David.

I think EasyBook in  had more fields that are different, compared with the current version in  .
* I deleted "gbedit" and "gbeditdate" (after backup  ), because I dont see them in a fresh install. I think they are not used anymore.
* There's one difference I don't know how to change, and that's in "gbdate" which shows "varchar(20)" in the table that came with the older install, and "datetime" in a fresh install.

Is it possible to convert the varchar values to datetime, and if so, how? For now, my install seems to work with the varchar setting, but I would like my install to comply with the new table structure in EasyBook 2.0.

I hope you can help....
Thanx in advance.

[David [snipersister]]

* I deleted "gbedit" and "gbeditdate" (after backup  ), because I dont see them in a fresh install. I think they are not used anymore.

Yeah, you're right, i deleted them because they weren't in use anymore.

* There's one difference I don't know how to change, and that's in "gbdate" which shows "varchar(20)" in the table that came with the older install, and "datetime" in a fresh install.

That's right too. I changed the type because with varchar it wasn't possible for mysql to order the entries correctly.

Is it possible to convert the varchar values to datetime, and if so, how? For now, my install seems to work with the varchar setting, but I would like my install to comply with the new table structure in EasyBook 2.0.

Well, it's definitly possible, but you'll have to write you're own little php script which converts all those dates from a unix timestamp to the mysql datetime format.
In the migration plugin, this is done by this tiny line of code:

Code:

$value = date("Y-m-d H:i:s", $value);

The other possibility would be to convert those days by hand into the new format.

Best regards
David

[FW]

I had only about 40 entries, so I converted them by hand.
Everything is working fine.