• 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.

Error on Fabrik 3.0 to 3.2 install

Status
Not open for further replies.

pastvne

Bruce Decker
I've downloaded the latest Fabrik 3.2. I currently run F3.0 on J2.5. When I install the 3.0.9 package installer, it will install. But when I try to install with extension manager the F3.2 download, I get:

500 Error
JDatabaseMySQL::query: 2006 - MySQL server has gone away SQL=SELECT `extension_id` FROM `jos_extensions` WHERE element = 'com_fabrik' AND type = 'component'

And the /tmp directory has a bunch of install_ directories.

Do I need to increase a PHP timeout or do we think it's a database issue?
Tried installing from directory and got the same thing

Thanks,
Bruce Decker
 
I've done it several times and didn't see such an error.
So yes, try to increase php timeout and/or memory limit (although this doesn't sound related).

You can also try to install "from Web".

Or just update from GitHub joomla3 branch.
This won't do any DB modifications, so maybe the Fabrik update won't look at the correct place (I didn't try), but with a GitHub update you have to stay on GitHub anyway.
 
Hi All:
This is to document the solution in my case. My site is on a shared server and the my.cnf file (MySQL) set its wait parameter too low:

my.cnf
wait_timeout = 30

I called my hosting company and requested they bump this up a bit.

my.cnf
wait_timeout = 45

And the installation succeeded.

There is another param in my.cnf that caught my eye:
connect_timeout = nnn

I didn't modify this one but it might be one worth considering if the above doesn't solve the issue for you.

-BD
 
Status
Not open for further replies.
We are in need of some funding.
More details.

Thank you.

Staff online

Members online

Back
Top