Geeklog Forums

Thanks for geeklog. I enjoy using it. Here are some suggestions for future versions:

- Could the word "Contribute" in the top nav bar be changed to "Submit a Story" or "Contribute a Story" or some other inviting phrase? The word "contribute" implies a monetary contribution (not always, but most of the time). Changing the words may promote more participation.

- Could there be a way to store the site logo in the database so it could be upgraded along with the rest of geeklog? Now, everytime you upgrade, individual files need to be tweaked to make sure the logo is correct. (logo.png and header.thtml in professional) I know custom themes would be difficult to upgrade directly, but the professional theme could work "out of the box."

These are small nits which only speak to the relative greatness of the rest of geeklog. Keep it up. No need to reply.

-gwilson.

$LANG01[71] is where the text for Contribute is stored. Not very intuitive, I know.

You can always modify the header.thtml in your theme under the layout directory.

I agree. Like I said, it's a small nit. Also, thanks for tip regarding the location of the "Contribute" text.

I can't speak for anyone else, but, for me, it is frustrating to remember all of these little "one line" changes everytime I do an upgrade. I know that some custom stuff will always be trouble, but the site logo? Can we store that in the database?

The time between upgrades is just long enough to allow me to forget how and where to make the changes. Has this happened to anyone else? In any case, I've started to keep a log of the customizations I've made after an upgrade..

Thanks again for Geeklog. Upgrading is already very painless, so that's why these small annoyances are noticeable.

-gwilson

Add a MyChanges file to your server next to the config.php. When you make a change document how and where the change was made in this file. Primitive but effective.

Remembering all those changes is a problem. If you do not want to document your things in a textfile then add a string to the files you changed such as

<!-- #myname start# --> and <!-- #myname end# --> in thtml files or

/* #myname start# */ and /* #myname end# */ in php files before and after the text you changed.
Afterwards you can search for #myname end# in the code with GREP (or wingrep if you are on windows) and find all that you edited.

this saves you from noting down line numbers etc where you made changes.
We are trying to improve geeklog constantly, and one big effort is to reduce places where you store your data.

So far, we do not store image locations in the database since the dimensions should be given with the image in the HTML and those will also change whn you change the image. To do it properly it becomes very complicated.