Slightly recursive,,, commenting on a recentcoments page. The formatting on this age is lovely...but I cant find a reference to this update anywhere, my recent comments action is much more vanilla (like the recentlycommented action is )

Ian, open http://wikka.jsnx.com/css/wikka.css and look for the section starting with:

/* recent comments */

Consider that the code/formatting on this page is not yet released. It will probably be included with the next release.

Thanks,
I already have an intergration nightmare ahead... as my install diverges from the release..

the css section is for tables, though the latest release version of recentcomments.php doesnt use tables, is the dev version of this action posted
(I can't locate it)

Humm, right - I realize that JavaWoman (who has been working on it) has not posted the dev version on the website. She is now on vacation but should be back in about one week.

Four months later ... I stil can't find the file in question.

I have to agree with IanHayhurst, so much time has gone by, dso many proposed items, so many mentioned as possibly being inclyded in the 'next release' ..... yet so much modification has occured in my install, I also cringe at the thought of trying to do the "next install" .... trying to figure out what ws included, what wasn't, and how much of what I've done thus far has been destroyed, crippled, or made into a nightmare to try to re-install ...

This confusion starts pretty much at the beginning .. the 'home' page isn't using either the previous or the current release, but a version of the previous with all sorts of Beta stuff 'only on this server' .... Some suggested code changes/additions/modifications point to even previous versions of the codebase, but no updates on the impact of a later release ...

The Tracking / Milestone pages make the "next release" seem so far out, yet it seems like so much time and so many changes have been put into place 'here' that it does seem past the time for a new release to bring things up to a 'standard' baseline.

WazoO, you are right that there is a lot of material to be included into wikka, for example this page. As you know, the output of new versions (but not the development!) had stopped in the last year which had several reasons. Because of this we have a big amount of code. You can see in the timeline of our wikka-trac, that we are working on the next release (which will not include all the listed items btw, but nobody had yet time to make the list smaller - look for items which have an owner to see on what we are working). Please remember that most of us are no experts with svn but that our skill will improve :)

As to the version used by the homepage, this will change in the future. As a part of the new structures, we have not only moved to a new domain but this wiki will be split, with the "homepage" running only on official releases and another one as a beta server. I know that upgrading heavily modified software is a pain. One of the development goals is to make wikka more modular, so that it will be easier to upgrade. But perhaps trac can help here (in combination with the diffs provided).

If you have the time (and you want to do it), you can help with the development: in cases like this it is the best to open up a new ticket on trac, with a reference to this page. It helps to keep ideas together (for example, the times in which I did know the content of all pages in this wikka are gone)!

Hard to classify things as a "bug" these days. In this case, is the file in question here the same file as found at http://wush.net/trac/wikka/browser/trunk/actions/recentcomments.php ???? It doesn't look like it, actually appears to be basically the same file as found on my 1.1.6.1. release (though again, it's identified as being from the 1.1.6.0 release?)

My last 'big' exercise was actually putting into place the IP address tracking of both posts and comments, which required making my own modifications to the database, extending and changing code found on several pages here by different authors at different times (and left in varying stages) .... I did in fact leave a comment on one of those pages asking for a bit of help in why the code results were different, but ... it could be a bug, it could be that I simply don't understand something, but it's hard for me to make that call and post it as a 'bug report' ... expecially seeing as all the code bits I'm playing with are 'suggested' code functions at this point (and that I had to further modify them to work in my install) ... as the whole anti-spam part of the work cycle seems to have stopped many moons ago, not sure of the interest in my exercises.