Fix features export

Created on 5 September 2023, over 1 year ago
Updated 21 August 2024, 4 months ago

Problem/Motivation

There is a features export built into the 7.x-2.x branch, but it doesn't work. The right type of code is in place, but the naming conventions are not correct for it to work as a features component.

Steps to reproduce

Attempt to configure ImageAPI Optimize and export the settings. The settings will not be exported.

Proposed resolution

See the attached patch. This should take care of the issues. Also moved the imageapi_optimize_features_api function into the main module file, so there's no longer a need for the include_once.

Remaining tasks

Review the attached patch, thanks.

πŸ› Bug report
Status

Needs review

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States ron_s

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Open on Drupal.org β†’
    Core: 7.x + Environment: PHP 5.6 & MySQL 5.5
    last update over 1 year ago
    Waiting for branch to pass
  • Issue created by @ron_s
  • Open on Drupal.org β†’
    Core: 7.x + Environment: PHP 5.6 & MySQL 5.5
    last update over 1 year ago
    Waiting for branch to pass
  • πŸ‡ΊπŸ‡ΈUnited States ron_s

    Ran some tests and realized I forgot to update hook names to match the changes made in hook_features_api. Was able to export, but the revert was failing because of this.

    Looks to be working correctly now, also included an interdiff.

  • πŸ‡ΈπŸ‡°Slovakia gresko8

    Are you talking about exporting the pipelines? I tested it and seems to be working fine in the beta2 version of the module. I added a new pipeline (the ones defined by the module are exported within the module so unless you allow conflicts to be added to your feature, you can not export those), exported successfully and tested updating and reverting as well. Found no issue.

Production build 0.71.5 2024