Some taxonomy term pages don't include all nodes

Created on 11 July 2024, 4 months ago
Updated 17 July 2024, 4 months ago
  • PHP 8.1.29
  • 10.6.18-MariaDB-cll-lve-log
  • 10.2.6 Drupal core with no PHP customization.
  • Taxonomy term view is 100% default without changes.
  • I have only one taxonomy vocabulary (the native "tags" vocabulary).

Some taxonomy term pages don't include all nodes.

The website is otherwise working fine with no errors and I didn't find any warning in the database log at /admin/reports/dblog.

How to solve this problem?

πŸ’¬ Support request
Status

Closed: won't fix

Version

10.2 ✨

Component
CSSΒ  β†’

Last updated about 19 hours ago

Created by

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

Comments & Activities

  • Issue created by @bendqh1
  • I believe that this problem is associated with deleting all revisions except the last one, as I did here πŸ’¬ How to bulk delete all revisions besides current revision for all nodes from all content types? Fixed .

  • Also asked at https://drupal.stackexchange.com/questions/320310/some-taxonomy-term-pag....

    That’s ok. I am only mentioning this so contributors look there in case other information appears there.

  • For support or possibly a bug report, test your theory about revision deletion on https://simplytest.me/ or on another freshly-installed Drupal site and report back here with the steps to reproduce.

  • Steps to reproduce are these:

    1. Install Drupal core 10.2.2 (regular installation, not minimal, not anything special)
    2. Create an article with revisions with one taxonomy term
    3. Add a second taxonomy term to that article
    4. Add a third taxonomy term to that article
    5. Confirm that three taxonomy term pages exist respective to the three taxonomy terms of the article and that each one of them links to the article
    6. Install the Node Revision Delete module in version 2.0.0-alpha2
    7. Delete all revisions of all nodes except the last revision of each node with the command drush node-revision-delete:queue
    8. Confirm that three taxonomy term pages exist respective to the three taxonomy terms of the article and that each one of them links to the article

    If the three taxonomy term pages exist respective to the three taxonomy terms of the article but no longer link to the article, then that's the cause of the problem.

  • Can you reproduce this with Core alone by manually deleting revisions? If not this should be moved to Node Revision Delete module.

  • I have tried this with the core alone by manually deleting all revisions except the last one of a node from a content type with revisions but I couldn't reproduce the problem --- all taxonomy term pages still linked to the node of that content type with only its last revision being preserved.

    As I am not 100% sure that the original problem is associated with the Node Revision Delete module, I will try to refer its maintainers to this post, just to get their opinion.

  • I have claimed here that some taxonomy term pages don't include old nodes but they will include new nodes, but now it seems to me that I was wrong and that even some new nodes from about the last month also don't appear in some of the taxonomy term pages associated with them --- this lowers the chance that the Node Revision Delete module has anything to do with this problem.

    Any recommendation how to proceed?

  • It is indicated that this problem is not from Views module because I put the number 63 in the preview box of the taxonomy term view and instead getting just one node summary I got all ten node summaries.

    The view SQL query is this:

    SELECT "taxonomy_index"."sticky" AS "taxonomy_index_sticky", "taxonomy_index"."created" AS "taxonomy_index_created", "node_field_data"."nid" AS "nid", "node_field_data"."langcode" AS "node_field_data_langcode"
    FROM
    {node_field_data} "node_field_data"
    LEFT JOIN {taxonomy_index} "taxonomy_index" ON node_field_data.nid = taxonomy_index.nid
    WHERE ((taxonomy_index.tid = '63')) AND (("node_field_data"."langcode" IN ('he')) AND ("taxonomy_index"."status" = '1'))
    ORDER BY "taxonomy_index_sticky" DESC, "taxonomy_index_created" DESC
    LIMIT 11 OFFSET 0
    
  • Status changed to Closed: won't fix 4 months ago
  • That was a CSS problem.

    From checking the HTML source, it was evident that the "missing" content was there all along.

    A certain wrong display: none; from a long time ago "deleted" the content from the output.

Production build 0.71.5 2024