Tattler profile wont install from installed Tattler distribution

@iaminawe

This is not an Aegir fault it doesn't work.
See similar issue with their Open Publish distro: http://drupal.org/node/560998#comment-1976300
They need to change current setup also because it will be broken completely under 7.x (namespaces)
Anyway, even when I rename Tattler install profile, it still fails on rdf module, so I need to:

1. install Tattler standalone
2. import installed Tattler as a new platform
3. use clone to create new sites

~Grace

There's no namespace problem in Tattler (lesson learned from OpenPublish, heh), but it seems like Aegir has an issue with RDF module?

The only problem here is likely that the rdf.api.inc file is not being included.

The error I get is:
Fatal error: Call to undefined function rdf_uri_to_qname() in /var/aegir/platforms/tattler/sites/all/modules/rdf/rdf.module on line 325

rdf_uri_to_qname is defined in rdf.api.inc, which is ONLY included in rdf_init();

Looks like drush is bootstrapping at a level thats too low... not sure.

having same problems with 6.x-0.4-alpha3

I'm still on aegir 0.3, I added require_once("rdf.api.inc"); require_once("rdf.schema.inc"); to rdf.module and now I'm getting the following errors after the welcome mail has been sent and the login url:
An illegal choice has been detected. Please contact the site administrator.
An error occurred at function : drush_provision_drupal_provision_install

subscribing

subscribing

subscribing

Almost SOLVED:

1) install the expanded distribution as a new platform
2) create a new site based on that platform (it will fail on Install)
3) enable that site
4) add as the last line on the file <your platforms directory>/tattler-<version>/sites/<your newly created tattler site>/settings.php

$update_free_access = TRUE; 

5) search the aegir database for the site number aegir assigned:

SELECT nid FROM aegir.node WHERE title="<your newly created tattler site>";

6) change the database password for user site_
7) drop and create the site's database;

  DROP SCHEMA `site_<your nid number>`;
  CREATE SCHEMA IF NOT EXISTS `site_<your nid number>` DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

8) edit the file /var/aegir/config/vhost.d/<your newly created tattler site>_80

  ServerName <your newly created tattler site>
  SetEnv db_type  mysqli
  SetEnv db_name  site_<your nid number>
  SetEnv db_user  site_<your nid number>
  SetEnv db_passwd  <your newly created password>
  SetEnv db_host  <db host>

9) restart Apache
10) Start the installation from <your newly created tattler site>/install.php

You will still get errors on the aegir but at least you have the site within the same managed system so it will be (hopefully) easier to migrate it to a newer (less error-prone) version.

That is not a fix: you're just manually creating the site. We need a patch on Aegir or Tattler to go forward here.

My opinion here is that the problem (and therefore fix) lies in the tattler profile, not Aegir, unless someone can prove otherwise. I would be happy to see a workaround in aegir, so I will keep this issue opened.

this is not our bug.

FWIW, I've managed to get Aegir to successfully install Tattler by commenting out line 87 of tattler.profile, which disables the BuzzMonitor modules. Once the site is installed, they can the be re-enabled on the site's modules page.

Following the disable buzz advice in #16 I also encountered a problem with a function call to initialize buzz on line 126 of the profile ...
// _buzz_set_cck_types();

should get you there with a newer release (august 30, 2010).

EDIT

make sure the
'img_extractor',

module on line 86/87 is enabled ... setting up the buzz thereafter ist a bit of work, though

buzz_photos-block_1 for instance needs to be setup manually ... see the profile and search for buzz .... As soon as I have a chance I'll try to modify the profile properly....