Test graphs show as grey rectangle

Can you verify that your input formats are set correctly... in particular that none of the following are checked for the input format used by forena:

Display any HTML as plain text
Limit allowed HTML tags
Convert URLs into links
Convert line breaks into HTML
Correct faulty and chopped off HTML

Also visit:
http://forenasolutions.org/reports/sample.svg_demo

So that we can verify that it isn't a browser issue. (Sorry in advance for the slow site performance... cheap shared hosting you know).

Hey Russell, happy to notice you've given my advice a try. Sorry to read that you struggled a bit with the typical input format requirement (as described in the setup guide). From your last comment, I seem to understand the "original issue" (= grey rectangle in state_grpah) is resolved now.

I'd be curious to read another update about the outcome of the custom report/graph you're working on now (in this issue here, or otherwise in the forum topic linked to above). Especially to hear about your perception of the (free) SVG Graph library as compared to the free or commercial version(s) of the jPGraph library.

PS: forena does not require the "libraries" module, what made you add that module? Maybe because of another module that requires it, such as the JpGraph module?

Russell, sorry to hear you're struggling 'a bit'.

About the version you're using as compared to the videos: the most recent 7.x-4.0 version (which you seem to be using) is indeed the recommended version (it is the latest and greatest). If you think it can help to refine your issue details (comment), consider adding the title of the video you are referring to, e.g. via a cut-and-past of that from the community docu about available videos. And add something like "near 3:47 after the video started". That'll give us a pretty good idea what exactly you are referring to. If you're referring to any of the videos related to the prior versions (like the 7.x-3.x), then keep in mind that most of what's in them still applies, but the "user interface" has changed in the current version. I think David is planning to create a refresh of those videos using the 7.x-4.x version "some day" (when time permits?).

With what is now in your comment #4, I suggest you try to "repair" that comment (because "if we don't understand the issue, we cannot get it fixed", right?).

Not sure how familiar you are with using the available facilities on drupal.org to create/update issues, so here are a few suggestion about that (sorry if I'm just repeating things you already know, just trying to help, OK?):

1. Using the 'edit' link below that comment #4, e.g. to insert some text like an error message. Then select that error message and use the "code" button (right above where you are editing the comment.
2. To upload screenprints, use the "Choose files" button and select the file containing the screenprint to be uploaded. That requires (a) the screenprint to be saved first locally of course and (b) it is saved in a format (file extension) that is allowed to be uploaded (look at the allowed file types just below the "choose files" button, typically you'd use jpg, jpeg, png or gif).
3. After you uploaded such files, refer to it in your issue description like "see myfilename.png".
4. While editing your comment, use the preview (instead of save) near the button, so you'll have an idea how your comment will look like if you'd save it. Keep editing and using the preview button until it looks good enough, and then save the comment again. If after saving you still notice anything that needs further editing, just edit it another time.

Also you could paste the snippet of the svg graph into a code section like this:

<svg frx:renderer="FrxSVGGraph"
  frx:series_1="{height}"
  frx:label="{age}"
/>

By seeing what the graph example looks like we might be able to point out anomalies.

Thanks for refining the issue details Russell. 1 more question: where within the body tags do you have something with an svg tag with that FrxSVGGraph renderer, similar that what David mentioned in #6? If you excluded it from the code you pasted, please "edit" the pasted code. If it just isn't anywhere (which I start to assume), then THAT is the direction to continue working on. Because if such SVG tag is not included, forena's output you currently get is what your report specification includes (ie: just a report, no SVG graph to be inserted).

If you want to edit your report by just editing your FRX file (instead of using the WYWiWYG editor, i suggest you look at the source (frx fie) of the svg_demo sample, then cut-and-paste any of the svg related content from there, and tweek it to match your needs.

Maybe David will have other suggestions? If not may we say "your turn again"?

PS: that "doc type" of SVG you added is only to later on "save" (or export) your report/graph (don't get confused with "inserting an SVG inside your report"). And since your report output doesn't contain an svg tag yet, your ...4.png output is correct (= empty) for now.

Also looks like from the fact that we don't see the SVG icons on the edit screen that there are still potentially tags being stripped or mucked with in your html. Is this the same site that you are referring to in Comment #2? Are there other things in your text format that may be interferring with the display of SVG data?

Sorry this is being so rough for you.

David, sorry for questioning "the expert" (aka you), but because of Russels's "I can raise sample.state_graph, and sampl.svg_demo also runs fine" in #2, it appears to me that the text format config should be OK, at least if it is indeed the same site. Am I right in assuming that those would not display correct either if the typical text format setup is not completed yet? FYI: My "bet" is that the svg tag with the SVGGraph renderer is missing. Curious to read Russell's next update ...

I totally could be wrong, but I was responding to the absence of the "pencil" and "gear" icons in the snapshot. These are currently SVG icons and it makes me wonder why they are text instead. Feel free to question me any time. There may be other things going on here in addition to that.

Dave

Russell, looks likes your new attempt is not as I suggested in my #9 comment: you used an embed-tag in which you refer to a graph with a .svg at the end. However in #9 I suggested an svg-tag instead, something for which the syntax looks like what David mentioned in #6. It appears to me that at this time it may not be obvious to you to use the frx editing approach (yet). Therefor, to get started, you should consider retrying using the WYSIWYG editor approach to get that chart "automagically" inserted by forena. Something similar to what you can see starting from about 6:00 minutes in the 2nd video of the 7.x-4.x series. Note that in that video David nowhere had to edit the frx file (only the SQL file earlier on in that video). After you get your chart show up and save it, you might then want to look at how the frx file content looks like.

1 more hint (if that might help): the tabular output you get so far corresponds to some "data block" you added in your report. If you ALSO want a graph (probably related to the same data to be shown), you MUST "insert" another data block (like before the previous block you already have). And in that (inserted) data block, you then have to specify that you want a "graph" to show those data, which is also what David does at some point in his video. Just adding this because when I at first started with charting in forena, it took me some time before I realised that.

To be complete: your " ... working out how to PRODUCE the graph from the data in my database ..." is exactly how it should (and does) work, also shown in that video above. Pretty sure your 'success' is close also. So please hang on, keep trying, and asking where needed, ok?

PS: in case David is a bit less responsive the coming days, might be because he's digesting the turkey and/or pumpkins (thanksgiving).

Could you post the middle section of the screen shot showing the detected columns? You should have age specified as the label? Is that true?

To Russell: looking at the screenshots (5 and 6) I just don't see anything that rings a bell about what is still wrong. If you are able to SAVE the report (frx file), can you try to copy it to a file with a txt extension, and then attach that txt file to the issue also? Especially I'd want to "see" the part of it with the SVG tag and the renderer in it. Such as what are the "field names" (surrounded by curly braces) that are used for the series and the labels (look at the frx file of the svg_demo sample to get an idea of what I'm looking for).

To David: could it be related to that "Not enough Values" as mentioned in #13?

Aha, "now" we have something to look at. I did some eyeballing and compared it with what's included in the frx file for the svg_demo, located at http://cgit.drupalcode.org/forena/tree/repos/reports/sample/svg_demo.frx

Here are a few frx:-options within the svg tag I have "new" questions about (some of them might explain the "Not enough values" error msg):

1. The frx:block that is included outside the svg tag, shouldn't that be moved to within the svg-tag?
2. There is no frx:type present, so what kind of chart are we expecting here (I'm not sure if forena has a default if it's missing).
3. There is no frx:xpath either, not sure if it is required, but maybe try adding something like frx:xpath="*"
4. The various other frx options related to colour, title, etc are probably only like "nice to have" (only add those after a first basic chart gets created)

From Screenshot 10, check the include table box, and change the radio for column age to "label", presss preview and show me what you get.

@Pierre.

Regarding 1. No that is unnecessary. The sample states graph demonstrates that.
Regarding 2. xpath="*" is the default so no problem there.
Regarding 3. I can't remember whether type is defaulted, I think it's required.

I would expect the following to work. Provided SVG is displayable on the web site.

<div id="growth_block" class="FrxTable" frx:block="dashboard/growth">
     <svg frx:renderer="FrxSVGGraph" width="600" height="400"
  frx:type="linegraph"
  frx:series_1="{height}"
  frx:label="{age}" />
</div>
    <table>
      <thead>
        <tr>
          <th>age</th>
          <th>height</th></tr></thead>
      <tbody>
        <tr id="growth" frx:foreach="*">
          <td>{age}</td>
          <td>{height}</td></tr>
     </tbody>  
</table> 
</div>

Hey Russell, "sunrise in EU again" ... Can't see/find any of the 6 png files you mentioned in #25, maybe you forgot to attach them?

Also it looks like my frx:type in #20 somehow got confirmed by David in#22, though he made some typos in the numbering he used to refer to my #20 (he swapped 2 and 3). So to eliminate the doubts if frx:type is yes/no required, make sure you do specify that in your next experiments.

Curious to soon see your next status updates ...

Now I'm really running out of inspiration, except that we can now see that funny string of data below where the chart should be shown. So I rechecked the various comments again starting from my #20. And the "regarding 1" in David's #22 ... I'm sorry to question "the master" (aka David) again, but the sample state graph does NOT illustrate what David wrote there. Instead, if I look at http://cgit.drupalcode.org/forena/tree/repos/reports/sample/state_graph.frx I see an frx:block within the svg tag. So I'd be really curious to know what result Russell would get by editing the frx files in #26 (either one or both), by ONLY "moving" the frx:block from the DIV tag to the SVG tag.

If that doesn't help either, at this time I do not have any other ideas for further debugging, except "maybe":

• Could it be related to some logic error in the SQL statement in see now in #26? That SQL error must be there for some reason. How about for now trying to first simplifying that SQL statement to the bare minimum needed for some type of chart output? Maybe David (as an SQL expert) has other suggestions in this area?
• Would it help to enable some type of data block "debugging" (an option somewhere in the forena admin screens)?
• Does Russell have some online (available to us) test environment where he could create a temporary account for us to do some similar debugging in his environment?

About sunset in EU again right now ... (and time for cocktail hour over here now ... just can't find the cocktail "bar" ...).

Pierre, this is the one I was talking about that shows the block in an enclosing tag.

http://cgit.drupalcode.org/forena/tree/repos/reports/sample/state_summar...

The sql error is because you are using double quotes where you should be using single quotes. I still believe that your input formats are mucking with your svg after the graph is being generated. That is why you see the numbers only.

Also be sure to add a column label to your count(1) column.

Ok David, the state_summary you pointed to in #38 indeed convinces me now, but since you first mentioned 'state graph' I thought you were talking about ... Euh ... Indeed ... State_Graph, sorry I got confused on that. Thanks for the SQL error stuff also.

Actually I'm also starting to believe "must be the input format". I suggest Russell will try to proof us with 2 more screenprints (a) which input format he is using for forena and (b) the typical tuning for the selected format are correctly set. So that we can eliminate that as a possibility. While trying to create those screenprints, maybe something unexpected becomes visible that actually will resolve the remaining mystery ... If that doesn't help, I would really like to LOOK at his site as I suggested before (with a login account).

Russell, #40 does not help at all to "me" (and I'm curious if it'll help David ...). Rather the opposite, in my opinion it just complicates things even more, because to me it provokes more questions.

Please confirm you applied the SQL changes suggested by David in #38, and add the 2 screenprints I asked in #39. The way I usually try to resolve support requests, is to eliminate all possible causes, verifying, verifying and verifying. Sometimes I add to that "I'll believe it after I've seen with my own eyes", which is why I asked the question in my 3rd bullet in #37.

FYI: I found the time to do a brief Skype with Russell. Confirmed the primary problem was Text Format config. Also corrected the SQL, so I think Russell is in business for now.

Because of #42, it appears to me that the current status of this issue (as described in the title of this issue also) should be different from ACTIVE. Is it FIXED now? If new issues came up, please create a new issue for it.

I think we can call this fixed. Rusell, please change case status to active if you have more troubles.