Error message with Cutting Edge

Installation
1

Hi Ross,

Yesterday, I downloaded the cutting edge edition of Gibbon. The installation went smoothly. When I try to login I get the following error message:

Fatal error: Uncaught exception ‘PDOException’ with message ‘SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘gibbon12b.gibbonstring’ doesn’t exist’ in C:\sis\data\localweb\gibbon12b\src\Gibbon\sqlConnection.php:174 Stack trace: #0 C:\sis\data\localweb\gibbon12b\src\Gibbon\sqlConnection.php(174): PDOStatement->execute(Array) #1 C:\sis\data\localweb\gibbon12b\src\Gibbon\trans.php(68): Gibbon\sqlConnection->executeQuery(Array, ‘SELECT * FROM g…’) #2 C:\sis\data\localweb\gibbon12b\functions.php(28): Gibbon\trans->setStringReplacementList() #3 C:\sis\data\localweb\gibbon12b\index.php(98): setStringReplacementList(Object(PDO), ‘edueodh4g-hyb-t…’) #4 {main} thrown in C:\sis\data\localweb\gibbon12b\src\Gibbon\sqlConnection.php on line 174

I also noticed that older versions of php no longer work. Is this right?

Maybe you have a more stable version of cutting edge available?

Kind regards,
Roman

2

Roman,

I have just installed the latest cut of v12, and the latest Reporting module along with it, with no errors at all.

I notice from the output above that you are running on Windows, where Gibbon is most tried and tested on Linux and Unix based machines. What server stack are you using? WAMP, XAMMP?

The issue is to do with translation and custom strings.

I wonder, if during the installation, in Stage 3, the Cutting Edge code setting is being correctly set to Yes. This is automatically done, but perhaps something is going wrong. This would prevent database updates from being installed, which would lead to the error you are encountering.

Ross

3

Hi Ross,

As reported in https://ask.gibbonedu.org/discussion/652/problem-activating-reporting-module-v1-09-with-gibbon-v11#latest I’m also facing problems under linux. Later versions of v12 cutting edge are affected. Older ones work fine.

I suspect this is php related. Are there new requirements regarding php and extensions?

Kind regards,
Roman

4

Roman,

PHP 5 and 7 are both supported in v12, and as I mentioned on the other posts, there are not installations problems here. Can you try the very latest commit of v12?

If that does not work, let us know the nature of the issues you are seeing, and we can looking it.

Thanks,

Ross

5

Hi Ross,

I just downloaded the latest commit using https://github.com/GibbonEdu/core/tree/v12.0.00.

I get the following error message when trying to install it on Wamp/Windows:

Warning: Unexpected character in input: ‘\’ (ASCII=92) state=1 in C:\wamp\www\gibbon-12-20160507\index.php on line 35

Parse error: parse error in C:\wamp\www\gibbon-12-20160507\index.php on line 35

My older installation of cutting edge dated 29/3/2016 works perfectly.

Kind regards,
Roman

6

Roman,

I’ll answer in https://ask.gibbonedu.org/discussion/652/problem-activating-reporting-module-v1-09-with-gibbon-v11#latest later today. Please post in one place only, just to avoid duplicating work. Thanks : )

Ross

7

Hi Ross,

I did a little research and was able to track it down.

The good news is that Wamp is not causing all these issues.

The first error message in this discussion was caused as you were rightfully suspecting by a failed detection of cutting edge. My unstable internet connection caused this.

The second error message regarding backslash is a PHP issue. It seems that later versions of Gibbon Cutting Edge v12 are no longer compatible with PHP 5.2 and below. I was using v5.2.9 and therefore fell into the trap.

Apparently Gibbon now uses namespaces, which are supported with PHP 5.3. PHP 5.2 and below don’t support namespaces and throw above error when they see the backslash.

I think it would help to list the minimum requirements for Gibbon Cutting Edge somewhere. Maybe this has been done already? I think it’s a fact that Gibbon is no longer fully PHP 5 compatible but requires at least PHP 5.3.

Kind regards,
Roman

8

Roman,

Looks like some good teamwork on solving that one : ) Thanks for picking up on PHP 5.2: this is a new requirement as of v12, as we are moving towards object oriented, and a lot of those features are new as of that version. I have made a note of the requirements in the Installation Guide on our website. Thanks for taking the time to research and feed back to us!

Ross