Feeds JSONPath Parser

Component type

module

Maintenance status

Development status

Downloads

147870

Component created

Component changed

This project is in maintenance mode. No new features will be added. New installs should use Feeds extensible parsers instead.

Features

This is a parser for the Feeds module that allows parsing JSON using JSONPath. It is very similar to the Feeds XPath Parser module.

Installation

The file jsonpath.php must be downloaded and put in the 'sites/all/libraries/jsonpath' folder. After installing the module, clear your cache so that the parser will be available in Feeds.

Documentation

Documentation can be found at http://goessner.net/articles/JsonPath/, and http://code.google.com/p/jsonpath/wiki/PHP.
** The syntax is different for the @ operator. In the documentation, examples look like @.name. That syntax changes to @['name'] since this is PHP and not Javascript.

Joomla-to-Drupal converter

Component type

module

Categories

Maintenance status

Development status

Downloads

3405

Component created

Component changed

Convert from Joomla! to Drupal.

Latest update

- Historically, this module was used to migrated a large Joomla! website to Drupal. The approach was iterative development: fast migration of content, write update functions to migrate other features. Therefore this module uses low level APIs to quickly create content (in dozens of minutes, instead of days).

Update feed CCK field

Component type

module

Maintenance status

Development status

Downloads

929

Component created

Component changed

Development on drupal.org now

Purpose

This is a CCK field which enables you to operate on the data of the update_feed_api and and the modules provided there using autocompletition and so forth.

This cck field is e.g. used to implement drush make files as nodes in drush_make_ui

Drush make UI

Component type

module

Maintenance status

Development status

Downloads

1708

Component created

Component changed

Purpose

This project aims to let you create a drush make file using a UI. The primary goal is not having a UI only but rather saving all the data strucutred for later uses.

That means, that every make file is a node, every module is a part of a CCK field, which seperates the data of a module into 4 fields (server_key, short_name, api_revision, revision).

Macro Code

Component type

module

Development status

Downloads

667

Component created

Component changed

Macro Code extends the Macro module to provide automatic exporting of macros to "component" files. A component file is simply a .macro file with one or more macros. Component files should be used to group form submissions whenever it makes sense.

The purpose of keeping form macros (form submissions) in files is to provide an easy way of duplicating settings (database) changes between multiple copies of the same project (such as development, staging & production environments).

Geonet NZ

Component type

module

Maintenance status

Development status

Downloads

391

Component created

Component changed

Wrapper for talking to Geonet NZ api

Working features

  • search for earthquakes by geoboundaries, time, depth, magnitude.
  • imports earthquakes as nodes (batch or cron)

In development

  • display New Zealand earthquakes on a map
  • display New Zealand earthquakes on timeline

Todo:

  • Views integration

Collaboration welcome. Send me a message.

Webform share

Component type

module

Maintenance status

Development status

Downloads

46067

Component created

Component changed

This is a helper module to prepopulate newly created webforms and to export / import webforms between sites.

Only tested on Webform 6.x-3.x and 7.x-4.x / Exports between different versions (6.x to 7.x or 3.x to 4.x) will probably not work.

Example usage 1: Prepopulated webforms

  1. Create a webform with the required components.
  2. Export the webform
  3. Edit the webform content type and paste in the content from the export (under Publishing options)
  4. Use the standard node add content links and each new content item created should be prepopulated with the exported webform.