If the configuration has been tampered with, some settings may cause the module to fail: this can happen is the main page node or function, or the disambiguation node are removed.

Requirements check should catch these.

CommentFileSizeAuthor
#4 1242092.patch8.83 KBfgm

Comments

fgm’s picture

fgm
Primary language French
Location Paris, France
commented
Status: Active » Fixed

Fixed in today's dev version.

fgm’s picture

fgm
Primary language French
Location Paris, France
commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
Status: Fixed » Patch (to be ported)

Need to be ported to D7.

fgm’s picture

fgm
Primary language French
Location Paris, France
commented
Version: 7.x-1.x-dev » 8.x-1.x-dev
Issue summary: View changes
Parent issue: » #3362685: Port to Drupal 10

D7 doesn't have long enough to live, moving to D10.

fgm’s picture

fgm
Primary language French
Location Paris, France
commented
Status: Patch (to be ported) » Needs review
StatusFileSize
new 1242092.patch8.83 KB

Port completed and improved: previously, it didn't check that nodes were not published

  • fgm committed 3e30acf7 on 8.x-1.x 
    Issue #1242092 by fgm: Harden requirements check based on D7 version.
fgm’s picture

fgm
Primary language French
Location Paris, France
commented
Status: Needs review » Fixed

Merged to current dev HEAD.

Status: Fixed » Closed (fixed)

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