1. Fabrik 3.9 has been released. If you have updated Joomla to 3.9, this is a required update.
    Dismiss Notice

Moving a very large Fabrik based site

Discussion in 'Community' started by Racmitch, Jun 13, 2018.

  1. Racmitch

    Racmitch Member

    Level: Community
    Hi Guys,
    We need to move our site built with fabrik to a new hosting co with a new domain, from a fabrik stand point what do we need to do to make sure it doesn't break?
  2. troester

    troester Well-Known Member Staff Member

    Level: Community
    After moving your site (e.g. with Akeeba backup + kickstart installation) log in, open the Fabrik connection and re-save with the new Joomla DB creditals.
  3. jfquestiaux

    jfquestiaux Well-Known Member

    Level: Community
    Also a warning in case you use the encryption feature for some elements (in the "access" section on the elements settings, "encrypt data" set to yes): when you move a site with Akeebackup, as a final step, it will re-create a configuration.php file and during this process it will generate a new "secret" word. Since this is the "salt" used by Fabrik to encrypt data, your previously encrypted data won't show anymore.

    So you have 2 options :
    • The easy way is to just copy the old "secret" (from the original site) and paste it over the one in the new configuration.php file.
    • The more secure way (it's good to change passwords form time to time) is to re-encrypt the data with the new secret word. Hugh posted the code to do that (in phpMyAdmin): UPDATE `table` SET `element` = AES_ENCRYPT(AES_DECRYPT(`element`, 'old_secret'), 'new_secret')
    samani and troester like this.
  4. cheesegrits

    cheesegrits Support Gopher Staff Member

    Level: Community
    Wow, I was not aware that Akeeba changed the secret. Thanks!

    -- hugh
  5. cpnetworld

    cpnetworld Member

    Level: Community
    Just a suggestion - may be there can independent secret which can be defined set in Connection. That way the fabrik application can be independent of joomla configuration setting.

  6. cheesegrits

    cheesegrits Support Gopher Staff Member

    Level: Community
    But that would then put the secret in the database ... which would rather defeat the purpose of encrypting the data at rest in the database, the point of which is to protect against the data being readable even if someone obtains your database. We would need to create our own file based connection configuration. Not impossible, but a lot of work for little gain.

    -- hugh

Share This Page