Install Problem pkg_fabrik_3.2.zip installa on Fresh Joomla 3.3.6

[cpnetworld]

Hi
On fresh Joomla 3.3.6 install of pkg_fabrik_3.2.zip gives error
An error has occurred.

1146 Table 'dolab_pubsite1.ypvft_fabrik_elements' doesn't exist SQL=UPDATE `ypvft_fabrik_elements` SET plugin = (SELECT replace(plugin,'fabrik', ''));​

Looking at phpmyadmin - it is observed that the tables are not getting created

Any one encountered this issue ?

 

[troester]

I never heard about such an error.
I just tested, it's creating the fabrik tables and #__fabrik_elements is empty after installation.

On fresh Joomla 3.3.6 install

with an empty DB?
Does your DB user have all access rights?
Did you try to download the package again (in case of your file is corrupted)?
Or try to install "from Web"?

 

[cpnetworld]

Hi
DB has all access rights. I have checked on two physical servers
I have tried again after downloading fresh package, Install from web and also by installing from server - Error remains same.
Same Package installs correctly on joomla 2.5 - joomla 3.0 site and also on sites where fabrik was installed earlier

Rakesh

 

[dwaine18]

I am having this error as well on a fresh install

 

[dwaine18]

Found the reason, the mysql database should be set up manually and must not begin with an integer. So instead of databade 12345, something like r_4322 will work.

 

[zambo.zsolt]

I'm having the same error on fresh Joomla install, but my database name doesn't begin with integer. Must be another reason.
com_fabrik_3.3.1.zip
Joomla! 3.4.1 Stable

database: 5.5.40-log
php: 5.5.20-pl0-gentoo
Linux web 3.17.7-hardened-r1

 

[zambo.zsolt]

My solution (however I still don't know the reason of this error)

In extension manager click on discover button, than Fabrik component, modules and plugins appear.
Install them, and everything will work, and database tables will be created.

 

[cheesegrits]

I just re-tested an install of 3.3.1 on J! 3.4.1, and can't replicate this problem.

Glad you got it resolved, although I wish we could work out what the problem is.

Thanks for following up with your workaround.

-- hugh