My issues at drupal.org

I'm using the migrate module to migrate content from a D6 site.
The D6 site used the image module, with image_gallery.
I can create Gallery nodes [terms in the D6 site].
I can create Media items [image nodes in the D6 site] using MigrateDestinationFile.

What I can't do is wire them together.
It would appear that media items are stored as a reference on the Gallery node.
So I should be able to map that.
I can get a comma separated list of file ids, [or what was their Node ids before import],
so passing that in like this should work

<?php
    // $media_list looks like this
   // $query->addExpression('GROUP_CONCAT(n.nid)', 'media_list');
    //$media_list = "234,456,789";
    // Pass in the list if images
    $this->addFieldMapping('media_gallery_media', 'media_list')
         ->sourceMigration('GalleryImage')
         ->arguments(array('source_type' => 'fid'))
         ->separator(',');
?>
but it doesn't.
Any clues?

Any ideas on how to get php5.2 up and running with Vagrant?
It would be good to have a VM with that instead of 5.3

I have an XML file that I can importing into a custom table [as part of a larger routine].
In general, importing into the custom table works well.
But some of the XML files are structured a little differently, and I'm not sure how to approach it.

<CourseProperty>
<CourseID>52797</CourseID>
<PropertyID>27</PropertyID>
<PropertyValue>ABC</PropertyValue>
</CourseProperty>
<CourseProperty>
<CourseID>52797</CourseID>
<PropertyID>31</PropertyID>
<PropertyValue>More text here</PropertyValue>
</CourseProperty>
I'm unsure how to setup the query in the import class
$item_xpath = '/ROOT/CourseProperty';  // relative to document
$item_ID_xpath = 'CourseID' . 'PropertyID';         // relative to item_xpath and gets assembled
       
Any suggestions?

I've been unable to get this working on my Vagrant installation.
Just wondering what the best way to figure out what is going wrong.
troc
'vagrant ssh' works
'vagrant ssh-config' works

'drush vagrant' works and the output matches that of 'vagrant ssh-config'

but using the alias from the local machine fails

drush @troc-vagrant cc all --verbose
Load alias @troc-vagrant                                                                                   [notice]
Command cache-clear needs a higher bootstrap level to run - you will need invoke drush from a more      [error]
functional Drupal environment to run this command.
The drush command 'cc all' could not be executed.                                                       [error]
The directory /vagrant/public/troc.loc/www does not contain a valid Drupal installation

output for Drush sa

drush sa --full
$aliases['troc-vagrant'] = array (
  'uri' => 'troc.loc',
  'root' => '/vagrant/public/troc.loc/www',
  'remote-host' => '127.0.0.1',
  'remote-user' => 'vagrant',
  'ssh-options' => '-o\'HostName 127.0.0.1\' -o\'Port 2222\' -o\'UserKnownHostsFile /dev/null\' -o\'StrictHostKeyChecking no\' -o\'PasswordAuthentication no\' -o\'IdentityFile /Library/Ruby/Gems/1.8/gems/vagrant-0.8.7/keys/vagrant\' -o\'IdentitiesOnly yes\' ',
);
Any ideas?

Patch forthcoming

I'm using profiller to define several default user accounts like so:

users[superduper][uid]    = 1
users[superduper][name]   = admin
users[superduper][mail]   = admin@example.com
users[superduper][roles]  = administrator
users[superduper][status] = 1

users[manager][uid]       = 2
users[manager][name]      = manager.test
users[manager][mail]      = manager.test@example.com
users[manager][roles]     = manager
users[manager][status]    = 1

users[editor][uid]        = 3
users[editor][name]       = editor.test
users[editor][mail]       = editor.test@example.com
users[editor][roles]      = manager
users[editor][status]     = 1

As far as I can tell, the user accounts are crated correctly. However, no welsome email are sent and there are errors reported stating "Error sending e-mail (from tom@example.com to ). So the to address for these users is blank for some reason when drupal tries to send the emails - even though they have been defined in the .info file.

This stops installation from completing when run from Aegir, as these are reported as errors.

I don't have our repo scrubbed to provide right now, but if you're interested, you can share the local ~/.drush dir and so create drush aliases for the host machine

You'll need to use vm.define "myvagrantbox" in the vagrantfile, and then tell people to run "vagrant ssh_config >> ~/.ssh/config" after provisioning. This not only allows you to easily ssh into the box from anywhere on the host, but also primes you for easily creating drush aliases in ~/.drush

Anyhow, just food for thought. I'll try to open up our internal vagrant repo soon, as I hate to work in isolation

This might not be something that this project should do by default, but one that many users could use.
I work on many different projects at the same time, each with their own code repo.
But they don't need their own virtual machine instance.

If these projects are all in the same directory and follow some naming patterns, would it be possible for vagrant to automatically build vhosts.
Eg - Within the directory called public
With a folder structure something like this
public
--project_a
--www
--project_b
--www

Vagrant would automatically create vhosts at project_a.local and project_b.local, with matching databases.

And when project_c comes along, just adding it to this projects directory, and then running 'vagrant provision' should do the magic.
Or something like that...

Maybe this is too much to ask for, but any tips welcome.

Upgraded to Views 6.x-2.16 from Views 6.x-2.14 and all of the Views references appear to work correctly - but when you change them, they disappear from the associated nodes.

Just getting familiar with this module but I can confirm the display ceases to function post-save to database when making changes. If the nodes are left unchanged, the views still appear correctly.

Digging around, there is nothing in the error log on the server, so, unsure what is causing it. Researching at the moment.

There is two slashes on the path provided.
Patch forthcoming

Annertech has been posted

Two different role

• The first one who's content needs to be moderated by an other role to make its content published.
• The second one who's content can be published directly

I simply can't find a way for doing this. If I set the "Bypass moderation restrictions" I still see its new content appear as a Draft and than it has to be set manually to published.

Would appreciate your help.

On some of my migrations, the source table is missing values for some of the fields.
When migrating into Drupal, it still imports that missing value.
So some fields have a label, but no value.
If I even just edit and save the node (with no other changes), the blank value is removed [and the label no longer shows].

Is there any way to avoid these 'Phantom Values'?