• Hello Fabrik Community

    Fabrik is now in the hands of the development team that brought you Fabrik for Joomla 4. We have recently transitioned the Fabrik site over to a new server and are busy trying to clean it up. We have upgraded the site to Joomla 4 and are running the latest version of Fabrik 4. We have also upgraded the Xenforo forum software to the latest version. Many of the widgets you might have been used to on the forum are no longer operational, many abandoned by the developers. We hope to bring back some of the important ones as we have time.

    Exciting times to be sure.

    The Fabrik 4.0 Official release is now available. In addition, the Fabrik codebase is now available in a public repository. See the notices about these in the announcements section

    We wish to shout out a very big Thank You to all of you who have made donations. They have really helped. But we can always use more...wink..wink..

    Also a big Thank You to those of you who have been assisting others in the forum. This takes a very big burden off of us as we work on bugs, the website and the future of Fabrik.

Latest Github from today kills site

nbradshaw

Active Member
My dev server is on J!3.7.2. I just did a master github today and it killed my dev site. Blank white page on front end and backend. Rolled back to 3.6 package and all is well.
 
It's ok on my site
Which php version?
Did you try to download GitHub again? Maybe some corrupted file?
 
Thanks...Yea, I am running close to Joomla minimums. I will try the error reporting and report back...unfortunately, it would take much effort to upgrade our servers.
 
It's likely that Fabrik may not be able to run with PHP 5.3.x. Most likely candidate is the new shorthand array syntax introduced in 5.4. While we avoid using it, to try and stay within J!'s 5.3.10 minimum version, we now ship a number of 3rd party libs maintained via the Composer dependency manager, which may use that syntax.

Might not be that, could be something simple like just tipping over your memory limit. But without an actual error report, it's obviously impossible to say. So as Troester says, whack your error reporting up to maximum, either in J! prior to updating, or in your PHP ini. Also maybe take a look at your server error logs, there should be something in there.

As for 5.3 ... it's a decade old version, that has been "end of lifed" for three years. It may be effort to update your servers, but you need to bite the bullet and do it. Moving forward you will find more and more code that won't run on it (I'm certainly not making any effort to be backward compat that far, don't even have 5.3 to test on) and at some point you'll hit an insurmountable issue, and have to do it. Better to do it now, while you can take a little time over it, than (say) when a J! security fix comes out for some evil bug, won't run on 5.3, and you are sitting ducks.

-- hugh
 
Ok - I finally go back to this & turned on error reporting:

Here is the error:
Parse error: syntax error, unexpected '[', expecting ')' in /var/www/html/Ops/Ext/libraries/fabrik/vendor/guzzlehttp/promises/src/functions.php on line 45


Is this file/function needed - or is this optional stuff that I can turn off?

BTW - I have already installed a new VM with PHP 7.0...so long term I will be moving my site to this new server....but until then...

Looks like Guzzlehttp php requirement is 5.5: http://docs.guzzlephp.org/en/stable/overview.html#requirements
 
Last edited:
Yup, that error you saw is as I said, "the new shorthand array syntax introduced in 5.4", which allows you to specify arrays as ...

$foo = ['one', 'two', 'three'];

... instead of the original 5.3 way of ...

$foo = array('one', 'two','three');

And indeed guzzle uses the new syntax. And as I said, "while we avoid using it, to try and stay within J!'s 5.3.10 minimum version, we now ship a number of 3rd party libs maintained via the Composer dependency manager, which may use that syntax."

And although the stuff in the Composer library isn't used by the "core" of Fabrik, it is used by our installable plugins. And the problem is, the way Composer works, we can't have a separate Composer library for each plugin. So for example, the Stripe payment gateway form plugin uses guzzle (as a dependency on the stripe API composer lib). And although you may not be using Stripe, and don't have it installed, the only way we can manage and distribute that library is as part of the monolithic ./libraries/fabrik composer lib (now an installable lib_fabrik.zip).

The only way we could have separate Composer libs would be if I split out every single plugin into it's own github repo, with it's own IDE project and build file. Which would be a complete nightmare.

So moving forward, Fabrik's minimum requirement is PHP 5.4. Although frankly, I only develop and test against 7.1, and would strongly recommend that everyone running a J! / Fabrik site runs 7.1.

-- hugh
 
Just FYI, if you don't run github, if you just install the Fabrik package ZIP, it won't install that Composer lib. You can then optionally install lib_fabrik.zip if you install any Fabrik plugins which require anything from the Composer lib.

There are a couple of core features (like PDF rendering) which won't work without the library, though. But that's always been true of PDF, you had to install github to get it. Now at least it's part of the new Composer lib, with an installable ZIP.

-- hugh
 
We are in need of some funding.
More details.

Thank you.

Members online

No members online now.
Back
Top