Steps to reproduce:

  1. Enable the Disqus module on an existing Drupal site
  2. Enable Disqus commenting "Visibility" for a content type, then disable the "Default Option" for that same content type.
  3. Visit an existing node of that type and observe that the Disqus box appears, even though you've disabled commenting by default.

Comments

rbayliss’s picture

StatusFileSize
new1 KB
rbayliss’s picture

Status: Active » Needs review
slashrsm’s picture

Version: 7.x-1.x-dev » 8.x-1.x-dev
Status: Needs review » Needs work

Patch looks ok. Thanks!

Since we already have D8 port we'd need to get that in there first.

eric_a’s picture

Why is it that you want existing content to suddenly switch value to a (new) default value? Nowhere in Drupal do we have that behavior. Default values are only applicable to new content. Existing content just has its existing value.

slashrsm’s picture

Priority: Normal » Major

Somehow related to #2508561: Default value handling is broken (Impossible to enable commenting). We should try to resolve all "default status" problem in one shot.

chegor’s picture

Still not fixed in 8.x-1.0-beta1

dawehner’s picture

Still not fixed in 8.x-1.0-beta1

Well, this is opensource, if someone works on something, stuff gets better.

nick dewitte’s picture

Status: Needs work » Needs review
StatusFileSize
new1.32 KB

The patch in #1 doesn't seem to apply to the latest 8.x-1.x version.
I changed the behavior of the widget instead.

  • RobLoach committed 0136901 on 8.x-1.x authored by nick.dewitte
    Issue #2438717 by rbayliss, nick.dewitte: Default status per node is...
robloach’s picture

Assigned: Unassigned » robloach
Status: Needs review » Fixed

Thanks!

Status: Fixed » Closed (fixed)

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