You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I suspect most people will want comment counts on the index (and possibly other pages) if they have Disqus-powered comments enabled. Presently that requires uncommenting code in a template page. For one, that is more technical than it should or needs to be.
Moreover, every requirement to uncomment template page content to get a feature causes a fork to permanently diverge from the main (upstream) repo's master branch, which in turn makes submitting clean pull requests (i.e., pull requests that don't contain the diverging commits) an increasing hassle.
So ideally, there is no need to ever uncomment - everything is controlled by config variables. The next best thing is that at least features more commonly desired or useful be controlled by config variables and not commenting/uncommenting.
The text was updated successfully, but these errors were encountered:
I suspect most people will want comment counts on the index (and possibly other pages) if they have Disqus-powered comments enabled. Presently that requires uncommenting code in a template page. For one, that is more technical than it should or needs to be.
Moreover, every requirement to uncomment template page content to get a feature causes a fork to permanently diverge from the main (upstream) repo's master branch, which in turn makes submitting clean pull requests (i.e., pull requests that don't contain the diverging commits) an increasing hassle.
So ideally, there is no need to ever uncomment - everything is controlled by config variables. The next best thing is that at least features more commonly desired or useful be controlled by config variables and not commenting/uncommenting.
The text was updated successfully, but these errors were encountered: