BUG#7959 R1.01e4

Jochen: Broken in R1.01e4:

• Notice: Constant *EWIKI_PAGE_POWERSEARCH already defined in \plugins\page\powersearch.php on line 12 Please add @ there
• Notice: Constant *EWIKI_TOC_CAPTION already defined in \plugins\aview\toc.php on line 25 Please add @ there
• Notice: Constant *EWIKI_PAGE_RECENTCHANGES already defined in \plugins\page\recentchanges.php on line 16 Please add @ there
• done: Warning: Invalid argument supplied for foreach() in\plugins\db\flat_files.php on line 148 What the hell...?
• Backlinks lists each page n times n beeing the number of versions of that page, all links go to the actual version
  • milky: bugs in the database backend, no doubt...
• done: Existing pages are marked as not existing In the page text after each wiki word is a questionmark, clicking on it jumps to the existing page
  • milky: Already had that bug earlier, needs investigation...
• done: RecentChanges doesn't work anymore Got it working in R1.01e3 but lists nothing now except for the footer (static text, edit and button)
• New highlighting is not included Why not? I can see it in the cvs...
  • milky: I did that R1.01d4 yesterday, the next R1.01d5 will contain it...
• Empty text-head container is not removed To keep it on the todo list:o)
  • milky: Also only in CVS still
• TOC labels still contain nbsp's To keep it on the todo list:o)

Perhaps it would be a good idea to mark such tarballs very explicit as experimental and unstable (special directory?). Then there should be a (monthly?) built stable(!) tarball. At the moment it's very hard for me as ewiki-newbie to get it working, coz each tarball contains 2/3 buggy plugins...

I use nearly no plugins (coz most seem to be buggy and my time is limited). When even such easy users get so many bugs introduced with a new version at least I will never update ewiki when I finally managed to get it working. And that couldn't be in your interest, could it?

So I think that ewiki is at a stage now where it could do nearly anything - if you know how to configure it and fix all the bugs in the version you want to stick with. Unfortunatelly only very few people on this planet know really about all the config options and have time and pleasure to fix all the bugs...

From my point of view ewiki has lots of potential to fit the needs of many people, including "simple" homepage wikis. But only if they don't have to look into the code of the core script and the plugins. What do you think?

milky: All true, but I don't fear that too many newbies would download it. People are only invited to stable releases (via freshmeat). And we're currently in transition to the ObjectOrientedDatabaseInterface, that's why so many things got broken perhaps. It's not that we don't wanna fix them ;)

Whatever, you're right, we should use a different naming scheme here. All the R1.0nXn releases are in fact development versions. So either a special devel/ download directory must be created, or a -dev prefix should be used. I was after a better versioning scheme anyhow...

milky: The a bit cleaner db_flat_files plugin in CVS may help with half of the problems.

Jochen: I'm never sure if I updated all files manually with the cvs. When will 1.01e5 be out? And will it be in a separate unstable directory?

milky: We'll switch to a better downloads/ dir structure (and bzip2-only tarballs) after the final R1.02a; I'm going to make another intermediate tarball (R1.01e5) tomorrow, after I checked the remaining database backends...

Jochen: Mainly solved, see EachPageListedTimes. Notices and manual vs. preset @ are discussed elsewhere. Closed.