Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-2182

JpGraph Error: 13 The installed PHP version (7.0.15) is not compatible with this release of the library.

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • None
    • Professional Edition
    • Billing
    • Centos7 php 7.0.15 Observium 17.2.8349 (13th February 2017)

    Description

      hi,

      after change the php version to 7.0 I got:

      JpGraph Error: 13 The installed PHP version (7.0.15) is not compatible with this release of the library. The library requires at least PHP version 5.1.0

      Attachments

        1. billing-data_graph.PNG
          billing-data_graph.PNG
          130 kB
        2. observium-bill.jpg
          observium-bill.jpg
          41 kB
        3. Observium-bill-1.jpg
          Observium-bill-1.jpg
          28 kB
        4. Observium-bill-2.jpg
          Observium-bill-2.jpg
          78 kB

        Activity

          [OBS-2182] JpGraph Error: 13 The installed PHP version (7.0.15) is not compatible with this release of the library.

          Yeah, perhaps we should remove the percentage bar when there is no limit set.

          adama Adam Armstrong added a comment - Yeah, perhaps we should remove the percentage bar when there is no limit set.

          you are right Adam. so I thing its on cosmetical to not show the graph if no limit is set.

          rherold Ruben Herold added a comment - you are right Adam. so I thing its on cosmetical to not show the graph if no limit is set.

          yes, this doesn't seem like a bug.

          If you expect a percentage bar to work on a bill with no limit, you have a bug in your head

          adama Adam Armstrong added a comment - yes, this doesn't seem like a bug. If you expect a percentage bar to work on a bill with no limit, you have a bug in your head

          We have it as well since the upgrade. Looks like some division by 0 stuff; since it only appears on bills with no limit set.

          rendest Stef Renders added a comment - We have it as well since the upgrade. Looks like some division by 0 stuff; since it only appears on bills with no limit set.

          Hmm. I wonder what's causing that!

          adama Adam Armstrong added a comment - Hmm. I wonder what's causing that!

          Yes seems to work mostly...
          But the INF% are still there please take a look into my screnshots

          rherold Ruben Herold added a comment - Yes seems to work mostly... But the INF% are still there please take a look into my screnshots

          Thanks ! Can confirm it works (deleted jpgraph)

          rendest Stef Renders added a comment - Thanks ! Can confirm it works (deleted jpgraph)

          Ahh yes. jpgraph was being included in the files where it shouldn't have been. Should work now!

          I guess I still have the jpgraph libraries in the directory here!

          adama Adam Armstrong added a comment - Ahh yes. jpgraph was being included in the files where it shouldn't have been. Should work now! I guess I still have the jpgraph libraries in the directory here!

          Aha, this is useful information. Let me look!

          adama Adam Armstrong added a comment - Aha, this is useful information. Let me look!

          Edit:

          Moved the jpgraph directory as a test, and it resulted in the screenshots Ruben showed. So obviously, there's something still being included.

          billing-data.php returns a HTTP 500 error so graphs aren't being shown.

          Kind regards

          rendest Stef Renders added a comment - Edit: Moved the jpgraph directory as a test, and it resulted in the screenshots Ruben showed. So obviously, there's something still being included. billing-data.php returns a HTTP 500 error so graphs aren't being shown. Kind regards

          People

            adama Adam Armstrong
            rherold Ruben Herold
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: