Page MenuHomePhabricator

When wgGEHomepageSuggestedEditsEnabled is false, homepage has a big blank space
Closed, ResolvedPublic

Description

As we decided to make Suggested Edits the center of our features, they are rendered in a prominent space of the homepage. When suggested edits are disabled, it looks like this:

image.png (788×1 px, 56 KB)

(fr.wiktionary)

If we want to deploy our features to other wikis in this configuration, we probably want to improve the look of the homepage in this scenario.

Open questions

How should we deal with suggested edits disabled? Revive variant A? Move modules a bit to make it look better? Something else?

Proposed design

As this is a very exceptional case, I would move the impact module to the place where the Suggested edits module would be.

image.png (824×1 px, 165 KB)

I think this is best as it would also cover the situation when some wikis also have the mentor module turned off:
image.png (824×1 px, 165 KB)

Event Timeline

mewoph added subscribers: MMiller_WMF, mewoph.

Hi @MMiller_WMF @RHo — I'm moving this to Needs Design since the expected behavior is still TBD.

There are 27 of such errors in GrowthExperiments logstash channel during last 24 hours from Nov 1, 2021 @ 22:34:03.569

Screen Shot 2021-11-01 at 3.33.30 PM.png (1×1 px, 208 KB)
.

normalized_message
The configuration title does not exist.
exception.trace
from /srv/mediawiki/php-1.38.0-wmf.6/extensions/GrowthExperiments/includes/NewcomerTasks/TaskSuggester/TaskSuggesterFactory.php(28)
#0 /srv/mediawiki/php-1.38.0-wmf.6/extensions/GrowthExperiments/includes/NewcomerTasks/TaskSuggester/LocalSearchTaskSuggesterFactory.php(55): GrowthExperiments\NewcomerTasks\TaskSuggester\TaskSuggesterFactory->createError(StatusValue)
#1 /srv/mediawiki/php-1.38.0-wmf.6/extensions/GrowthExperiments/includes/NewcomerTasks/TaskSuggester/DecoratingTaskSuggesterFactory.php(53): GrowthExperiments\NewcomerTasks\TaskSuggester\LocalSearchTaskSuggesterFactory->create()
#2 /srv/mediawiki/php-1.38.0-wmf.6/extensions/GrowthExperiments/includes/HomepageHooks.php(724): GrowthExperiments\NewcomerTasks\TaskSuggester\DecoratingTaskSuggesterFactory->create()
#3 /srv/mediawiki/php-1.38.0-wmf.6/includes/deferred/MWCallableUpdate.php(38): GrowthExperiments\HomepageHooks->GrowthExperiments\{closure}()
#4 /srv/mediawiki/php-1.38.0-wmf.6/includes/deferred/DeferredUpdates.php(515): MWCallableUpdate->doUpdate()
#5 /srv/mediawiki/php-1.38.0-wmf.6/includes/deferred/DeferredUpdates.php(391): DeferredUpdates::attemptUpdate(MWCallableUpdate, Wikimedia\Rdbms\LBFactoryMulti)
#6 /srv/mediawiki/php-1.38.0-wmf.6/includes/deferred/DeferredUpdates.php(221): DeferredUpdates::run(MWCallableUpdate, Wikimedia\Rdbms\LBFactoryMulti, Monolog\Logger, BufferingStatsdDataFactory, string)
#7 /srv/mediawiki/php-1.38.0-wmf.6/includes/deferred/DeferredUpdatesScope.php(267): DeferredUpdates::{closure}(MWCallableUpdate, integer)
#8 /srv/mediawiki/php-1.38.0-wmf.6/includes/deferred/DeferredUpdatesScope.php(196): DeferredUpdatesScope->processStageQueue(integer, integer, Closure)
#9 /srv/mediawiki/php-1.38.0-wmf.6/includes/deferred/DeferredUpdates.php(242): DeferredUpdatesScope->processUpdates(integer, Closure)
#10 /srv/mediawiki/php-1.38.0-wmf.6/includes/MediaWiki.php(1136): DeferredUpdates::doUpdates()
#11 /srv/mediawiki/php-1.38.0-wmf.6/includes/MediaWiki.php(846): MediaWiki->restInPeace()
#12 /srv/mediawiki/php-1.38.0-wmf.6/includes/MediaWiki.php(584): MediaWiki->doPostOutputShutdown()
#13 /srv/mediawiki/php-1.38.0-wmf.6/index.php(53): MediaWiki->run()
#14 /srv/mediawiki/php-1.38.0-wmf.6/index.php(46): wfIndexMain()
#15 /srv/mediawiki/w/index.php(3): require(string)
#16 {main}

I think what @Etonkovidova mentioned is a different bug: on some wikis, the NewcomerTasks.json configuration file is not present at all, and this is what happens in that case. I think that should be discussed (and ideally, fixed) as part of another task.

RHo lowered the priority of this task from High to Low.Feb 8 2022, 1:14 PM

Hi @RHo, when the user hasn't made any edits, currently the unactivated state of the impact module with the heart graphic makes a reference to suggested edits in the copy (and on mobile there is a link to open the suggested edits module). Should we still show the unactivated state with a different copy or just use the default state of the impact module?

Screen Shot 2022-02-14 at 3.37.54 PM.png (412×980 px, 50 KB)

Hi @RHo, when the user hasn't made any edits, currently the unactivated state of the impact module with the heart graphic makes a reference to suggested edits in the copy (and on mobile there is a link to open the suggested edits module). Should we still show the unactivated state with a different copy or just use the default state of the impact module?

Screen Shot 2022-02-14 at 3.37.54 PM.png (412×980 px, 50 KB)

Ack. Yes let's use the default state since I would prefer not to introduce another variation of the unactivated state for this edge case.

Change 762927 had a related patch set uploaded (by MewOphaswongse; author: MewOphaswongse):

[mediawiki/extensions/GrowthExperiments@master] Homepage: move impact module to main group when suggested edits is disabled

https://gerrit.wikimedia.org/r/762927

Special:Homepage when GEHomepageSuggestedEditsEnabled is false

Screen Shot 2022-02-15 at 10.50.25 AM.png (2×2 px, 856 KB)

Change 762927 merged by jenkins-bot:

[mediawiki/extensions/GrowthExperiments@master] Homepage: move impact module to main group when suggested edits is disabled

https://gerrit.wikimedia.org/r/762927

Checked on frwiktionary wmf.23:

Screen Shot 2022-02-25 at 3.16.43 PM.png (1×2 px, 262 KB)