Cross referencing from a views thread:
See attached photo: I've ... tried creating a new view from scratch, and added to it two "content: title" fields, each with its own Administrative title. The administrative titles are not shown at all, and clicking on either (ie: to edit), takes me only to the details' modal for the first item in the list.
...
UPDATE: After much troubleshooting, this appears to be related to a core update that occurred at the same time, from 7.34 to 7.36. The error persists in Views 3.8 and 3.10, but goes away when I roll back core to 7.34.
| Comment | File | Size | Author |
|---|---|---|---|
| breaky-breaky.png | 89.37 KB | jweirather |
Comments
Comment #1
David_Rothstein commentedI tried to reproduce this but wasn't able to. I used Views 7.x-3.10 and a fresh installation of Drupal 7.34 to create a view with two "Content: Title" fields and gave each an administrative title. The administrative titles showed in the user interface both before and after updating to Drupal 7.36.
Then I created a new view in Drupal 7.36 that was configured the same way, and the admin titles worked fine there too.
Can you reproduce this with just Drupal core and Views, and if so, what are the exact steps? Or could there be another module that is causing this?
Comment #2
jweirather commentedNo, I haven't tried to replicate the issue in a clean install (and I do know that I should), and yes, it could certainly be another module or combination of modules, but I've not been able to narrow it down yet to anything else.
Currently scrambling on another issue right now, I will try to replicate in a clean install and post back when I have a moment...
Thanks for the prompt attention, it is appreciated. Sorry for the firedrill.
Comment #3
jweirather commentedPosting an update for posterity. At this point it appears this may be somehow related to the (also updated) Ember theme for D7 (7.x-2.0-alpha3) and possibly, somehow its relationship to core. Rolling back Ember to 7.x-2.0-alpha2 appears to fix this issue for me, though I haven't yet narrowed down why. I will post back more details if I find them. In the meantime, I wanted to document this for others.
At the time of the original issue I had a complex development site, and reached a point where I was ready to apply version updates to about a dozen modules plus core. The modules included, most notably:
plus similar version updates for several other modules, including: entity, token, rules, panels, and several others.
After applying all of those udpates the issue surfaced. I began pulling at threads and ended up in a disaster recovery situation, due to 2 months worth of incomplete (timed out) database backups. At this point I have rolled back to a February image of the same site, which needed the same list of updates. I used drush up [module] to apply these same core and module updates one at a time, checking the views issue (among others) after each update.
All of the module updates apply cleanly and without issue, including core, which was the first update I made. The last update I made is the Ember update, which causes the issue immediately upon cache clear. Rolling back that one specific update eliminates the issue, even with core updated as noted.
I'm still in DR mode, but will troubleshoot the Ember issue as soon as I can. I realize this is likely an issue for that module's queue, but will leave this open and postponed until we have some more information. Again, sorry for the firedrill.
Comment #4
jweirather commentedThe Ember theme has a template.php file that overrides aspects of the Views UI. Opened an issue there. Closing this one for now on the (increasingly strong) assumption that that's where the issue lies.
Comment #5
jweirather commentedComment #6
David_Rothstein commentedNo problem, and thanks for posting back with the additional information! Good luck tracking down the issue.
Comment #7
dremy commented@jweirather That makes sense. We have been seeing the issue as well in Views UI and we also roll with a subtheme of Ember.