Problem/Motivation

I would like to see the sitemap status and priority in views.

Proposed resolution

The sitemap state per entity is stored in serialized format. Its not possible to query it in views. I used a computed field to integrate in views.

Remaining tasks

User interface changes

API changes

Data model changes

CommentFileSizeAuthor
#2 2941322-2.patch4.59 KBwebflo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

webflo created an issue. See original summary.

webflo’s picture

webflo CreditAttribution: webflo at UEBERBIT GmbH commented
Status: Active » Needs review
FileSize
2941322-2.patch4.59 KB
webflo’s picture

webflo CreditAttribution: webflo at UEBERBIT GmbH commented
Title: Expose sitemap index and priority » Expose sitemap index and priority in views

Status: Needs review » Needs work

The last submitted patch, 2: 2941322-2.patch, failed testing. View results

gbyte’s picture

gbyte CreditAttribution: gbyte commented

This is really interesting, might be useful to display sitemap settings through a view.
Patch did not apply for me either, could you check it out?

Also, what is your use case for this feature?

gbyte’s picture

gbyte CreditAttribution: gbyte commented
Version: 8.x-2.x-dev » 8.x-3.x-dev

Patch needs to be ported to 8.x-3.x.

gbyte’s picture

gbyte CreditAttribution: gbyte at gbyte commented

  • gbyte.co committed afc20a1 on 8.x-3.x 
    Issue #2941322 by webflo, gbyte.co: Expose sitemap entity settings in...
gbyte’s picture

gbyte CreditAttribution: gbyte as a volunteer and at gbyte commented
Title: Expose sitemap index and priority in views » Expose entity sitemap settings in views
Status: Needs work » Fixed

I've heavily modified the patch and implemented views integration for all entity settings. Thanks for your input!

Status: Fixed » Closed (fixed)

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

gbyte’s picture

gbyte CreditAttribution: gbyte as a volunteer and at gbyte commented
Status: Closed (fixed) » Needs work

I have been thinking about it some more and I do not like this partial solution. With computed fields, it is impossible to use the calculated values as view filters/sorting, as (obviously) the query is not being affected. A better solution would be to redesign the storage of entity overrides. I will remove this feature before the full release and we can keep this open for a more solid implementation.

gbyte’s picture

gbyte CreditAttribution: gbyte as a volunteer and at gbyte commented
Status: Needs work » Postponed

I believe this can be easily implemented when #3034070: Store entity instance settings as fields on entity is completed.

gbyte’s picture

gbyte CreditAttribution: gbyte as a volunteer and at gbyte commented
Version: 8.x-3.x-dev » 4.x-dev