Problem/Motivation

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#9 Views_Global_TextArea-3223529-9.patch1.65 KBsundhar
#7 Views_Global_TextArea-3223529-7.patch1.61 KBjustachris
#6 drupal_8_view_3223529.yml4 KBjustachris
#6 drupal_7_view_3223529.txt3.77 KBjustachris

Comments

ankurkumar.mishra created an issue. See original summary.

ankurkumar.mishra’s picture

ankurkumar.mishra commented
Title: Broken field or missing field showing is view after view imported. » Broken field or missing field showing in view after view imported. For exposed filter.
sundhar’s picture

sundhar
Location Coimbatore TN - India
commented

Hi ankurkumar.mishra,
Thank tou for take time to post the issue.

Could you check All Drupal 7 fields available in Drupal 9 site & Upload Your Drupal 7 views export Configuration.

ankurkumar.mishra’s picture

ankurkumar.mishra commented

Hi Jeya Sundhar,

Thanks for the comments , yes i have checked all the fields are available in Drupal 9 that are there is Drupal 7,
but still i am getting error for broken filed for some exposed filter and when i am adding manually its working but we don't want any manually work for view migration because we have lot's of view to migrate.

Also we are getting below warning after migrating the view,
Warning: Illegal string offset 'value' in Drupal\views\Plugin\views\area\Text->preQuery() (line 50 of C:\xampp\htdocs\drupal-test-5\core\modules\views\src\Plugin\views\area\Text.php)

It's really helpful if you help on these issues.

Thanks
Ankur Kumar Mishra

sundhar’s picture

sundhar
Location Coimbatore TN - India
commented
Assigned: ankurkumar.mishra » Unassigned
justachris’s picture

justachris commented
StatusFileSize
new drupal_7_view_3223529.txt3.77 KB
new drupal_8_view_3223529.yml4 KB

Deducing from the error given, I'm able to replicate the error by setting a Global Text Area in the Header section of the View in Drupal 7 and referencing an exposed filter using the replacement tokens. Not certain if adding the replacement token is required to cause this error OR if just setting the text area in the Header is the problem. I've attached an export of a sample view in D7 and the resultant migration into D8. May have some time this week to take a look at the cause.

justachris’s picture

justachris commented
Status: Active » Needs review
StatusFileSize
new Views_Global_TextArea-3223529-7.patch1.61 KB

The problem is that Global Text Area fields (Area Plugin) should have a value and format in the content array element, this is handled differently between D7 and D8. Attached patch to map these correctly and convert the token symbol.

sundhar’s picture

sundhar
Location Coimbatore TN - India
commented
Status: Needs review » Needs work

Hi @justAChris :D,
This patch not applied. It throws error
error: corrupt patch at line 33

sundhar’s picture

sundhar
Location Coimbatore TN - India
commented
Status: Needs work » Needs review
StatusFileSize
new Views_Global_TextArea-3223529-9.patch1.65 KB

  • Jeya sundhar committed 269aaa3 on 1.1.x 
    Issue #3223529 by justAChris, ankurkumar.mishra: Broken field or missing...
sundhar’s picture

sundhar
Location Coimbatore TN - India
commented
Version: 1.1.4 » 1.1.x-dev
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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