Problem/Motivation

See: #2886357-69: Changing default "<response>" and "<item>" tags in XML export for more details.

Sort of tempted to remove the cheeky addition of the encoding="utf-8" bit, and then the changes here really will be absolutely minimal and could get merged right in.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork views_data_export-3522528

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

steven jones created an issue. See original summary.

steven jones’s picture

steven jones commented
Assigned: Unassigned » steven jones

Lets see if we can set the encoding to be enabled by default for new installs, and otherwise keep things as they are for everyone until 8.x-2.x.

steven jones opened merge request !77

steven jones’s picture

steven jones commented
Status: Active » Needs work

I've added the start of this. Still need a post update hook that'll update all existing views to set their encoding to the empty option, which will then preserve what they're doing already.

steven jones’s picture

steven jones commented
Assigned: steven jones » Unassigned
Status: Needs work » Needs review

Sorry about the noise there, was on a machine without access to running PHP unit!

Anyway, I think this is ready to be committed now.

steven jones credited xperd.

steven jones’s picture

steven jones commented

Going to credit users who contributed to #2886357: Changing default "<response>" and "<item>" tags in XML export relating to encoding.

  • steven jones committed 8843239c on 8.x-1.x 
    Issue #3522528 by steven jones, xperd: Allow specifying the XML encoding...
steven jones’s picture

steven jones commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.