12

If you're exporting into an empty site, the Backup and Migrate module is the one you want. It will let you clone all contents on a Drupal site, including comments. (Or only certain tables such as thos associated with nodes and comments, if that is what you want). The Node Export module will only let you import/export nodes. Comments, for instance, is not ...


10

The Migrate module can migrate anything you want from the most databases. Depending on how your content is put together this might be relevant for you. Links: Migrate module architecture Field mapping A great blog I liked using-migrate-module-handle-big-data-imports Related question Migrating Multiple Files in a node Also be sure to look into the Migrate ...


10

UPDATE You might also try Drupal Console's drupal config:export:content:type command. It's description says: The config:export:content:type command Export a specific content type and their fields. Content types and Fields are 2 separate configuration in Drupal 8, so if you want to export content type with fields you have to export all it's fields ...


10

I do this all the time, making use of migration configuration entities (provided by the migrate_plus module). Define a migration plugin in your migration module's config/install directory, using the CSV source plugin from the migrate_source_csv module - omitting the 'path' source configuration, which will be filled in from the form. Let's say the ID of this ...


9

To add a field to custom content type you need field.field.node.content-type.field-name.yml field.storage.node.field-name.yml The easiest way for you is create the content type and fields via UI and then just simply export it in admin/config/development/configuration/single/export (you have to install the config core module). Then remove uuid and you are ...


8

For a single View, there is no difference in functionality really. The view will be the same regardless. I use Features anyway because it's makes it more conventient to organize multiple pieces of configuration into "features". I'm not aware that ctools offers any easy way of doing "This view with that panel and those three dependencies in one module". That ...


8

User passwords are stored using a one-way hashing algorithm and cannot be converted to plaintext. In addition, each Drupal site uses a unique cryptographic salt, so that the same plaintext password on two Drupal sites will not result in the same hashed password. In other words, there is no way to generate a list of usernames and plaintext passwords.


7

You need to specify the full HTTP path. It's possible that something like a file schema might work (public://images/name.JPG), but in my extensive use with Feeds we import file fields (mostly images but also mp3, pdf, etc) by specifying the full HTTP path that the file can be found at, e.g.: http://example.com/sites/default/files/images/name.JPG.


7

Import from two xml files (on for each language), my empiric solution : I created two feed imports. I forced the language field for each one. Two separated nodes were created for each content (one in each language) but it didn't links the translations. So I used a SQL query to finish the job, it's based on the feeds uuid Note: In order for this to work ...


7

A year or so ago I was working on a Drush command to export a working site as an installation profile. I haven't worked on it for a while, but it was my intention to use something like the Configuration Management module, or perhaps Drush CTools Export Bonus to include site configuration information with the installation profile. If you are hand-generating ...


7

You do not need to install a module for this. This sort of thing is provided by the Drupal core. It is called an "Aggregator" and you find it as one of the core modules with the following description: Aggregates syndicated content (RSS, RDF, and Atom feeds). It is not enabled by default. You need to enable it. Here is a rundown of the UI: administer ...


7

You can export the rules configuration via the Rules UI and then implement hook_default_rules_configuration_alter() like this: /** * Implements hook_default_rules_configuration_alter(). */ function MODULENAME_default_rules_configuration_alter(&$data) { if (isset($data['commerce_cart_add_to_cart_message'])) { $data['...


7

I think I've figured this out. You need to define the 'content_translation_source' property on the translated node, so that Drupal knows what language it's coming from. Eg: migrate_plus.migration.articles_fr.yml process: #... content_translation_source: plugin: default_value default_value: en #... (Be sure to substitute the value en for ...


6

For Drupal 7 try WordPress Migrate: wordpress_migrate supports migrating WordPress blog exports (WXR format) into Drupal using the Migrate module. Import of posts, pages, comments, attachments, tags and categories is supported. Imports can be rolled back completely. and Wordpress Import if you are using Drupal 6: This module imports a WordPress ...


6

drush help node-export You can pass --format to supply the format of the output. Try doing drush node-export-export --type=poll --file=xpoll --format=xml


6

There is a way: Go to Configuration > Regional and language > Date and Time > Formats (Tab) Then click "add format" to add a new date format and just type "U" in the textfield. The "U" is actually the timestamp. Go back to "Types" tab and add the new date type you just created and give it some name like "Timestamp". In your view select your date field and ...


5

Here's an updated function that should work for D7. <?php /** * Exports a CSV. * * @param array $variables * An associative array of data containing "header" and "rows" keys. * This is ready to be passed to theme_table(). See api.drupal.org/node/22950. * Also contains the key "filename" specifying the filename. */ function ...


5

There is also Views Data Export. It supports many data formats including Excel and CSV. It also depends on Views. It is designed to handle extremely large datasets by batching the export process but producing one file. Views Data Export


5

You could go to the list of all content in Drupal's admin pages ( /admin/content in D7), then filter by content type, then select all, then select 'Node export' from the dropdown menu


5

I'm not familiar with webform_share, but I have had good experience with a module called Node Export, which works pretty well with webforms, and notably with webforms where the form is integrated with CiviCRM via the webform_civicrm integration module.


5

You can export blocks with the Features Extra module, or better yet, use the Boxes module, which is designed to be exportable. Using MySQL dumps is an advanced trick that gets harder with each version of Drupal as the API becomes more complex. It's not recommended and definitely not for the faint of heart.


5

If you know any php I recommend the Migrate module to easily write a SELECT title, body FROM old_content and map them to Title and Body fields of a Drupal Page type. You would do this with a Migration class. See documentation on the project page. You could also try the Feeds project. There are modules for Migrate to migrate from Wordpress or older Drupal ...


5

The most quick and painless way would be to dump the old content from SQL to a CSV and import using Feeds - this can be done using a SQL program and point-and-click through Drupal. If this is a one-time thing, you should be fine with this. Feeds has mapping for most field types. If you need to fully integrate, or do a more complex migration (import to ...


5

I found my answer. Features creates a module that I need to import in the destination site.


5

Mobile App Generator exports a website to plain .html pages so that PhoneGap can compile it into native mobile apps. Mobile App Generator assists in creating native multi-platform PhoneGap mobile applications for Apple iOS(iPhone, iPad), Google Android, Palm, Symbian, BlackBerry and more. If you want to manage the website through mobile App then take ...


5

Here's two functions, a menu callback with a simple function to query and export all defined variables. No required module dependencies, just Drupal core. /** * Implements hook_menu */ function MODULE_menu() { $items['export/variables'] = array( 'title' => 'Export variables', 'page callback' => 'MODULE_export_variables', 'access ...


5

"Painless" data migration? You're kidding, right? :) There are numerous answers suggesting the Migrate module. It is certainliy an option, but one I've never liked. I've done dozens of projects with migrations of content from external systems into Drupal (sometimes from multiple external sources simulteneously), including projects with millions of pieces of ...


5

I solved the problem this way: set max_allowed_packet = 4M to the file php.ini


5

Stick the following in a file named expusers.module <?php /** * Implementation of hook_menu() */ function expusers_menu() { $items['expusers'] = array( 'page callback' => '_expusers_select', 'access arguments' => array('administer expusers'), ); return $items; } /** * Callback */ function _expusers_select() { // $...


5

@potney i have updated your code.Please check drupal_add_http_header('Content-Type', 'text/csv; utf-8'); drupal_add_http_header('Content-Disposition', 'attachment;filename=csvfiles.csv'); $output = ''; $keys = array(t('User id'), t('Username'), t('Email')); if ($keys) { $output .= implode("\t", $keys) . "\n"; } $members = _get_users_in_group($gid); ...


Only top voted, non community-wiki answers of a minimum length are eligible