Page 1 of 1
always same content_id when adding a page.
Posted: Sat Apr 09, 2005 6:18 pm
by Chris
Dear all,
When add a page is always gets a content_id of "0" and I can't find out what's wrong here. Can anyone give me a hint....
Thanks in advance...
Chris
Re: always same content_id when adding a page.
Posted: Sat Apr 09, 2005 6:27 pm
by Ted
Sounds like the sequences didn't get setup right. Is this 0.9.2 and MySQL?
Re: always same content_id when adding a page.
Posted: Sun Apr 10, 2005 8:11 am
by Chris
Yes it is. Do you know how I can solve this ?
Re: always same content_id when adding a page.
Posted: Sun Apr 10, 2005 12:41 pm
by Ted
I would try a reinstall first.
Re: always same content_id when adding a page.
Posted: Mon Apr 11, 2005 6:46 am
by Chris
I've tried that already... Can you describe the problem further plz.....
Thanks in advance...
Chris
Re: always same content_id when adding a page.
Posted: Mon Apr 11, 2005 9:33 am
by Ted
We use a layer called ADODB that handles the databse work in a cross-db way. Because half of the databases out there use sequences instead of auto incremental primary keys (which are harder to work with -- thanks mysql), there is a way that sequences are emulated using a separate table with one row and one column.
So, there should be a table in your database called cms_content_seq. If you "SELECT * FROM cms_content_seq;" on a fresh install of CMS, you should get a 5, because that's the next id that would be used. However, it seems to me that this query is returning 0.
To be honest, I'm not sure what would be causing it. The seqences (and their tables that emulate them) are created on install, as is the id that is put in there.
Does that make any sense?
Re: always same content_id when adding a page.
Posted: Mon Apr 11, 2005 1:57 pm
by Chris
Thanks Wishy !! I changed the values in the _seq databases to the correct values (if there were any) and then it worked ...
Thanks for all the help !!!!!!
Re: always same content_id when adding a page.
Posted: Mon Apr 11, 2005 2:02 pm
by Ted
Very strange that it didn't work out of the box. I haven't heard about any problems with that with the 0.9.2 release (I know it was bugged previously).
Anyways, glad it worked.
