When enabled, the "Weighted front page settings" on admin/config/system/site-information conflicts with empty_front_page module (and possibly other modules) because both modules then override the callback for /node.

Since Weight module has a wide audience (it is not only used to sort frontpage content), and since the problem may be hard to diagnose for most users, I humbly suggest that this settings be turned off by default.

Comments

davisben’s picture

davisben
Primary language English
Location NH, USA
commented
Status: Active » Closed (won't fix)

I'm hesitant to change the default behavior at this point, but if most people think it should be changed I can reconsider.

marco.b’s picture

marco.b
Primary language German
commented
Issue summary: View changes
Status: Closed (won't fix) » Needs work

I installed weight on a website with a frontpage consiting of blocks and no content. Of course the default message "No front page content has been created yet" disturbed my design and I used the empty_page module to get along. So all was well before I installed weight. After installing weight that message was at the frontpage again.

It took a while that I noticed the unwanted modification through weight activation on the system. My non-elegant and dirty workaround was to place an empty node as frontpage and use exclude_node_title. That works.
In general I wish that modules behave as neutral as possible to avoid unwanted changes.

davisben’s picture

davisben
Primary language English
Location NH, USA
commented
Status: Needs work » Fixed

I changed the default to have this setting be off.

  • davisben committed d93876c on 7.x-2.x 
    Issue #1958182 by davisben: Weighted front page settings conflict with...

Status: Fixed » Closed (fixed)

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