Required D6 administration steps

The 6.x versions were quite finicky about making sure it was fully configured, and really required you to save settings on each of the configuration pages after selecting the options. In particular, verify the directory where forena stores its reports and press "Save", but you'll also want to configure document types, etc.

If you're just getting started, I'd recommend looking at the old videos section of the project page. The 7.2 versions and 6.2 versions were very similar in the way they behaved. There's a walk through of configuring forena for the first time.

Of course I would also recommend looking the Drupal 7 versions as I believe you will be much happier with that product.

Ok, but I had a lot of trouble with this in D7. In particular guessing the right filter was a bit problematic. Patches are welcome.

Paul, can you provide some details about those minor install changes as you mentioned in #3 ? If you can, I'd like to recreate the issue in a D6 setup and try to create a patch for it. Better still: maybe you can create the patch as you mentioned in #3 and attach it to this issue (I'd review it and if OK get it committed to the D6 DEV branch)

No more news from Paul anymore about this D6 related issue. And the weekly forena usage stats indicate that the D6 usage has gone up lately quite a bit again. So I think it's worth trying to get some of these D6 issues sorted out somehow, at least to try to document some of things David mentioned in #1. For now I'm just going to use this issue to "report" (oeps) about the issues I discovered, and what I did to get them resolved. Probably followed by a combination of (small) D6 related fixes and/or documentation updates later on, hoping "Le Patron" will agree on it. Depending on how it turns out it may end up in something like a 6.2.3 version. Hope it's OK to update the issue meta data as I did here, if not please correct.

Read on for more details about it all ...

There isn't much small that can be done with regard to 6.x on meeting this issue. You can document the changes (these have already been addressed in youtube videos), but the mechanism used for storing reports ultimately needed to be reworked to make this happen. That has a lot to do with major work in refactoring this code in 7.x-4.0. Because I'm starting to work towards Drupal 8, I'm unlikely to be doing another major rework of drupal 6.x (although I'm happy to fix bugs if they are found).

OK, here is the very first D6 issue I ran into, and an easy work around for it ...

Instead of a quick issue update here, I decided to document it (together with the suggested work around for now) in the community docu, within Getting Started. If some day it gets resolved in some 6.2.3 version, we probably want to remove it from that community docu again, agree?

While working on that docu, I decided to add a pointer to this issue there also, regarding the "Page not Found" issue where this issue started from. Fingers crossed that soon I'll have some time to try to recreate this "Page not found" issue. When that happens I plan to refine the Getting Started page about it. If anybody runs into it before I do, don't wait for me to apply the community docu update for it ...

David, your #7 makes a lot of sense to me (hadn't seen it before I wrote my #8), and I bet many will agree that D8 investments are much more valuable then D6 "enhancements". Just documenting some of those (minor) D6 issues seems to me the most effective approach. While doing so, I'd be happy to also submit suggestions for tiny corrections to the D6 version in cases where they seem to make sense. E.g. even if it was only to refine some warning/error messages to indicate some problem, and a recommended action to solve it.

And yes the available videos address quite some issues already, which is why I always try to add pointers to it in the docu where appropriate. As you must know also, videos have 1 major disadvantage: search engines don't help a lot to find the videos (and the actual location within the video) when you're looking for specific keywords. So that seems a good reason to have some type of docu somewhere, like in the community docu.

About your rework to store the reports: that's one of those recent forena enhancement I really enjoy. Including those "revert", "clone" and "delete" links in the forena admin screens. When I first discovered those new links I asked myself "what is the actual logic behind each of these links". I think I now know (from experience) what they do, but at first I hesitated a bit to use them. I might create a new issue to submit some extra update about that logic, either in the tutorials, or via tiny coding corrections related to each of such links, describing what will happen if you click such links. Eg, for revert: remove from custom folder and re-enable the delivered version.

Update about what I wrote in #8 above, regarding bullet "1" within Getting Started (the community docu): the workaround I documented for that issue solved my problem in a (production) site running in Linux (CentOS). But when I retried the same scenario in my local dev environment using VirtualBox running Linux (Ubuntu), I get the very same problem, but the workaround seems to NOT get it resolved. I'm planning to further research what might cause the problem (and how to solve it). For now I get the impression that it might have to do with some type of missing file permissions for the web user, though what is strange is that I encounter no problem to create a new report. That leads me to believe that the file permissions to save reports in my report directory are OK, but it might be that something is wrong regarding the READ access to copy the delivered reports FROM the forena module subdirectory. I'll update this issue (and the community docu) when I figured out what is wrong, and how I resolved it, but in the meantime any extra hints to further debug this issue would be appreciated.