Geeklog Forums

Each time I try to edit a story I get the following:

"The ID you chose for this story is already in use. Please use another ID."

Which means I can't edit anything without re-posting..

Any info I should give you to help fix this? What can I do?

Toby W. Allen
President
Game Development Society.
www.gdsleeds.com

Try logging in with another browser that has had all cookies/logins/etc. cleared out of the cache.

Heya,
That does work, however it does appear to be a bug as my webmaster has informed me that he's had to repair some stuff. Also each time we do this we get logged into the error log, so I might have to send Dirk this.

Toby.

Make sure you've updated the template file for the story editor (if you're not using one of the stock themes).

bye, Dirk

Dirk, I'll check this out - Meantime:
Here's the bug report for the Geeklog story editing problem.

Error: Saving a story after editing causes error message: "The ID you
chose for this story is already in use. Please use another ID."

Technical description:
The submitstory() function in public_html/admin/story.php:872 has an
undocumented parameter $old_sid. The function checks for existing
stories with the same ID but then runs the following comparison:
if ($sid != $old_sid) {
$duplicate_sid = true;
}
I have no idea what purpose this is for, but the $duplicate_sid variable
causes the error message to be generated (line 910). I don't have
sufficient access to the system to put in variable watches for debugging.

Steps to reproduce:
1. Create a new story and save it.
2. Go to edit the story, press save.

Work around:
If database access is unavailable, the edited story can be saved by
modifying the hidden SID value live in the page. This can be done easily
using the Mozilla FireFox Web browser with its DOM Inspector.
1. Edit story.
2. Open DOM Inspector, search for node where attribute is 'name' and
value is 'sid'.
3. Increment the value attribute by one.
This duplicates the story so the old one needs to be deleted, and has
the side-effect of losing comments.

Hope that helps.

Toby,

first of all, bug reports should be posted in our bug tracker. Forum posts tend to get overlooked ...

Having said that: I don't think it is a bug. From your description, you seem to be using an old theme that hasn't been updated for Geeklog 1.3.10 (as described in the documentation).

Starting with Geeklog 1.3.10, story IDs are editable in the Admin's story editor. And of course Geeklog has to check that you don't use the same ID for two different stories. So that's what that additional parameter is for. If you're using an old version of the story editor template, that test will fail, though. So make sure to update that template file ...

bye, Dirk

Problem Fixed - It was the outdated template.

Thanks for that and sorry for the disturbance.

Toby.

Why is it that version 1.3.11 can't include updated stock themes? I was using the clean theme, and after upgrading, it complained about some file (archivestorytext.php, i think) not being there. I copied that file from the professional theme, and it worked OK for a while. Now I can't edit any stories and all kinds of sily crap is going on. My site is now slower than hell with 1.3.11, while with 1.3.9 it was pretty snappy.

I'm pissed off. Thanks for nothing. And Dirk, for you to arrogantly just say that this isn't a bug is lame. You're just a smug little snob.

Geeklog 1.3.11 comes with a working theme. Updated versions of the old themes are available here. Also see here and here.



I expect an apology for this.

bye, Dirk

That's my point, why can't these updated themes that you provided links for be provided in geeklog itself? It only makes people (rightfully so) think that geeklog does not work right.



You are right, that was immature of me and I do apologise. I realize that flaming people gets us nowhere, and I know that I was stupid.

The original point remains, can we put working themes in geeklog?

The list of changes for 1.3.10 states that there were theme changes and includes a link to the description of those changes.


Keeping 8 themes up to date is just too much work. We provide one working theme for reference as well as a list of changes. What else do you expect?

Absolutely nothing. Thank you for all your hard work. The original point is moot, since I switched to Mambo last night. No hard feelings, ok?

Hey, if the geeklog developers are too lazy to maintain their templates properly, why should we bother using it? Congratulations for switching to Mambo, everyone should. At least Mambo only includes templates that WORK!

It's unbeleivable how many morons are doing sysadmin these days. If you're too lazy to read and learn some php and html your should stick to frontpage. Dirk has no responsibility for keeping themes up to date. Getting angry at someone who's committed years of hard work to such a valuable project for free is incredibly lame. I've used Geeklog for 4 years now and one has to expect minor bugs between versions and templates. All your whining could have been immediately solved by simply cd'ing to the layout dir, typing yes|cp -R professional/admin/story/* newtheme/admin/story/

Great work Dirk, don't let fools get you down.

Jason Loughead
PLUG
Prairie Linux User Group

Idiots like Angry just used more time whining than it had recuired for updating his theme.
If he cant figure out simple problems by himself, why try doing something he cant?

I had the time to say this since using the forum here solves most my problems quite easily and saves me a lot of time
And then I can again say thank you for geeklog, and great honour to Dirk!

In a few weeks he will do the same at some other support forum. He should start a W3Schools learning some basic HTML, since that's all you need to update older themes (and some patience and a few minutes to RTFM).

But he has a (very small) point, I think it is a good thing to update at least some themes. Since I'm no PHP expert but do have HTML/CSS knowledge I could a look at it next month. But no promises, I don't know when I have some spare time....



Guess I'll have to start with these some time.

For GL2 I think it's nice to only have public theme and a neutral theme-less admin part. This way it's perhaps easier to maintain the themes.

---

Dutch Geeklog sites about camping/hiking:
www.kampeerzaken.nl | www.campersite.nl | www.caravans.nl | www.caravans.net

OK this may seem like a stupid question. How does one update the template for the story editor. Since i am having this same problem.

I simply overwrote my theme's admin/story/storyeditor.thtml with the one from the professional theme. It seems to work at the moment...

P.S. Thanks for all the great work guys. I find the admin load for running geeklog is pretty light, and it's not hard to get less technical folks to work with the submission interface. I get also frustrated with getting fancy older version themes to work, but I found my answer here in this thread real nice and fast.

I agree -- thanks to the FAQ's and forums at this site I've overcome every problem I've hit so far. Problems, I might add, that I caused in the first place.