MEpedia:Suggested tasks

From MEpedia, a crowd-sourced encyclopedia of ME and CFS science and history
(Redirected from MEpedia suggestions)
Jump to: navigation, search


This page lists suggestions for improvements to MEpedia.

Please feel encouraged to consider making the relevant page or edit yourself (see How to contribute to get started!), as many editors of MEpedia are sick and working hard to improve the content in particular areas. We need your help!

But if you can't make the improvement yourself, add your suggestion to the end of the appropriate section. Please briefly detail your suggestion, including the name of the MEpedia page(s) that need creating or editing, and web links to sources/citations (e.g., the published study, a source for a quote, etc.) Then sign your suggestion with your name and the date.

Tip: If you'd just like to keep track of your own goals on site (but make them visible to others), instead of adding suggestions here you can add a subpage to your user page (add a "/" and subpage, e.g., User:Brettz9/To-dos) and then add the category [[Category:User to-dos]] to your subpage article. It will then show up at Category:User to-dos.

Priority pages for expansion[edit | edit source]

High priority[edit | edit source]

When a task is complete move it to the COMPLETED section at the bottom of the page

  • High usage page Esther Crawley needs a cleanup including neutrality improving citations, adding missing citations, and marking any extra citations needed. notjusttired (talk) 18:57, May 24, 2019 (EDT) - add neutrality Aug 12, 2019 - Njt
  • High usage page Fibromyalgia needs a cleanup, mostly adding citations meeting the Science guidelines
  • Female predominant diseases: complete this table of gender ratio + prevalence for chronic illness: Female predominant diseases#List of diseases (will likely be used in advocacy and outreach efforts)
  • Add photos of ALL the May (and Belfast in June) Millions Missing protests to the MM page http://me-pedia.org/wiki/Millions_Missing_protests
  • Add the Stats.org editorial & 7,000 word criticism to the PACE page :
  • Add a portal on Wikipedia for CFS or umbrella (e.g., auto-immune-related conditions), bringing more awareness and contributions on Wikipedia (also through subpages, such as "B cells and CFS"), and which we could reference here
Can this task be removed? Wikipedia tasks should not be in the MEpedia list. If it's a task for MEpedia then also suggest removing since many Portals already need extra work and several comorbidities still don't have pages which is a greater priority (Removal requested by User:Notjusttired Aug 2019)

Admin suggestions[edit | edit source]

When a task is complete move it to the COMPLETED section at the bottom of the page

these have been updated, are you happy that is this done now? (Njt Aug 2019)
It doesn't matter if I'm happy, just whether MEAction is happy. Since these are policy pages, they must be reviewed/approved by MEAction before they can be considered "final". Until then, they're just "drafts"... Hope this helps.
Pyrrhus (talk) 22:41, August 10, 2019 (EDT)
Right, just waiting for MEAction to review then notjusttired (talk) 16:12, August 11, 2019 (EDT)
  • Create MEpedia:Privacy policy - it's linked to from bottom of all pages. Add it to “MEpedia documentation” category. See Talk:Wmf:Privacy policy for details. Make it protected so that only admins can edit it. Also make Wmf:Privacy policy protected because that is an important redirect. (Request last updated by Pyrrhus April 2019)
  • Create MEpedia:Cookie statement - it's linked to from bottom of all pages. Add it to “MEpedia documentation” category. Make it protected so that only admins can edit it. Also make Wmf:Cookie statement protected because that is an important redirect. Requested by Pyrrhus April 2019)
Wmf redirect protected thanks to User:Kmdenmark notjusttired (talk) 16:12, August 11, 2019 (EDT)
  • Create MEpedia:Terms of use - it's linked to from bottom of all pages. Add it to “MEpedia documentation” category. Make it protected so that only admins can edit it. (Requested by Pyrrhus May 2019)

Developer suggestions[edit | edit source]

When a task is complete move it to the COMPLETED section at the bottom of the page

    • Add the Abuse Filter extension so we can have custom editor warnings and certain phrases banned. Configure: in LocalSettings.php add wfLoadExtension( 'AbuseFilter') set to "$IP/extensions/AbuseFilter/AbuseFilter.php"; - requested by Njt, Oct 2019
    • Run Update.php after installing AbuseFilter
    • Add AbuseFilter rights, so admins and bureaucrats have full use -

$wgGroupPermissions['sysop']['abusefilter-modify'] = true; $wgGroupPermissions['*']['abusefilter-log-detail'] = true; $wgGroupPermissions['*']['abusefilter-view'] = true; $wgGroupPermissions['*']['abusefilter-log'] = true; $wgGroupPermissions['sysop']['abusefilter-private'] = true; $wgGroupPermissions['sysop']['abusefilter-modify-restricted'] = true; $wgGroupPermissions['sysop']['abusefilter-revert'] = true;

    • Add an "AbuseFilter editors" group in LocalSettings.php:

//Create a user group called "abusefilter" for filter editors $wgGroupPermissions['abusefilter']['abusefilter-modify'] = true; $wgGroupPermissions['abusefilter']['abusefilter-private'] = true; $wgGroupPermissions['abusefilter']['abusefilter-modify-restricted'] = true; $wgGroupPermissions['abusefilter']['abusefilter-revert'] = true;

  • Add $wgSpamRegex settings to LocalSettings.php to block user page spam, check if this setting already exists first (different code will be needed). (Requested User:Notjusttired Aug 2019)
$wgSpamRegex = "/visit our website/"; 
  • Consider adding either an MEpedia logo or a particular image to the footer, maybe where "powered by MediaWiki" used to be, this means when you share pages without images this image will be used instead of some tiny icon or no image - this should increase clicks and traffic to articles (added Jul 2019 by User:Notjusttired, passed to developer)
The LocalSettings.php code to do this is as follows. Note that this footer icon does not show up in the Pivot skin, but we can remove the pivot.css code that hides it. More info: https://www.mediawiki.org/wiki/Manual:$wgFooterIcons
Pyrrhus (talk) 14:45, July 20, 2019 (EDT)
$wgFooterIcons['poweredby']['mediawiki'] = [
	"src" => "$wgScriptPath/resources/assets/mepedia_logo_mobile.png";,
	"url" => "https://www.meaction.net/",
	"alt" => "Powered by MEAction",
	// If you have a non-default sized icon you can specify the size yourself.
	"height" => "31",
	"width" => "31",
];
$wgRightsIcon = null;
Yes, pretty simple although which image to choose - round logo, logo with Myalgic Encephalomyelitis underneath (currently being done by developers), or default image of Whitney - see here for it at 31px wide which actually looks ok to me notjusttired (talk) 20:28, July 20, 2019 (EDT)
I think your mobile logo mepedia_logo_mobile.png would be ideal!
Pyrrhus (talk) 21:07, July 20, 2019 (EDT)

(Requested Jul 2019)

  • consider adding a "thanks" button if it can be easily adopted from the WMF software (see: https://en.wikipedia.org/wiki/Help:Notifications/Thanks) -- really nice way for editors to communicate appreciation to one another that costs many fewer "spoons" than writing/reading a note (suggested by Canele, June 2019)
I like this idea but can't see any instructions for doing installing this on those pages. I have copied both the {{Thank}} and {{Thank you}} across notjusttired (talk) 14:25, July 17, 2019 (EDT)
There is a Thanks extension that will probably do the trick, but we can't install it until after we update the MediaWiki software, unfortunately.
Pyrrhus (talk) 22:31, July 17, 2019 (EDT)
I didn't think to look there! We can install it, but need a previous version that matches what we have - REL_1_30 I think, and will need to upgrade it once MediaWiki is upgraded. The code is on github, linked to the page. I think this is worth requesting notjusttired (talk) 15:04, July 19, 2019 (EDT)
Oh super! Smiley faceThank you both, Pyrrhus and Njt! Canele (talk) 16:42, July 20, 2019 (EDT)

(Requested and passed to developer Jul 2019)

  • check why search engine crawls are taking months to reflect updates - Google search console, robots, etc, consider adding site map that including images requested by User:Notjusttired (Recrawl of key pages requested Jul 2019)
  • Improve MEpedia logo quality, requested by User:JaimeS. (According to the $wgLogo page, the logo can not have a resolution higher than 135x135 pixels, but two higher definition versions can be specified with $wgLogoHD.)

(Requested Jul? 2019)

  • Remove the following from LocalSettings.php. Our new policy is that people need to make 50 edits before they skip the CAPTCHA, regardless of whether they are emailconfirmed or not. (Requested by Pyrrhus May 2019)
$wgGroupPermissions['emailconfirmed']['skipcaptcha'] = true;
$ceAllowConfirmedEmail = true;
  • In year 2020, we will need to upgrade our MediaWiki software and extensions to the latest stable versions. The new version of MediaWiki software includes important security fixes. The new versions of the extensions include important fixes and improvements. (Added by Pyrrhus, May 2019) (I suggest doing this later in the year to get a newer version, but to update compatible extensions / skins etc to the newest versions that work with our existing MW version early in the year - Notjusttired, Aug 2019)
    • Any extension with a “compatibility policy” of “release branches” must be updated with any new version of MediaWiki. These include Echo, Scribunto, TemplateData, PageImages, Citoid, VisualEditor, Thanks, StructuredDiscussions, HitCounters.
    • The Linux package Parsoid must also be updated every time VisualEditor is updated.
    • We should also update the DismissableSiteNotice extension so that the dismissals last longer than a week.
    • Although not required, it is advised to also update the Cite extension, and the Pivot and Timeless skins as well. (ParserFunctions update not needed - comes with release 1.31+)
    • Changes can be tested on the staging server before being implemented on the production server. See MEpedia:Developer guide.
  • In year 2020, we will need to do “performance tuning” of the MySQL(MariaDB) database and “performance tuning” of the MediaWiki software as described in https://www.mediawiki.org/wiki/Manual:Performance_tuning (Added by Pyrrhus May, 2019)
  • Apply the HitCounters patch so that the popular pages link is in the correct language (will be done when HitCounters is upgraded for later MediaWiki version) - requested by Njt Oct 2019
  • In year 2020, we can ask a MediaWiki specialist what needs to be done to handle internationalization. Some custom system messages will need to be translated. The LanguageSelector and Polyglot extensions will probably need to be installed. The following will probably need to be added to LocalSettings.php after the extensions load: (Added by Pyrrhus June 2019)
$wgLanguageSelectorDetectLanguage = LANGUAGE_SELECTOR_PREFER_CLIENT_LANG;
$wgLanguageSelectorLocation = LANGUAGE_SELECTOR_AS_PORTLET;
  • After Foreign Language support is installed, consider adding Translation Support so that we can access the volunteer translators at translatewiki.net: (suggested by Notjusttired, Aug 2019)
    • At a minimum, we will need to install the Extension:Translate extension. If we're really ambitious, we could install the entire MediaWiki Language Extension Bundle. (Niklas Laxstrom from translatewiki.net has advised that only the Translate extension is needed for our purposes.)
    • The Translate extension will need to be customized. (See [1] and [2])
    • MEAction will need to assign a Translator Project Liaison with admin privileges in order to:
  • Install Extension:LocalisationUpdate (System message localization can be done via Export from another wiki then Import so not being developer input, although Extension:LocalizationUpdate which adds any new translated system messages could be requested - User:Notjusttired Aug 2019) - added as separate request since many system messages only translated in some languages, plus it saves manually creating many of them) - any system message we don't have we would only need to create in English, then all translations would be created for us notjusttired (talk) 19:27, August 30, 2019 (EDT)
  • Consider updating backup scripts to delete old backups, so that we can ‘rotate’ backups instead of overwriting them. Code for this can be copied from here. Also consider adding automated email notification of backup failure. Also consider adding automated termination of stalled backups. (All to be done AFTER the “New Backup Protocol” request.) (Requested by Pyrrhus May, 2019)
  • IF it is ever decided to limit editing to users with accounts, and to prevent anonymous users from editing, simply add $wgEmailConfirmToEdit=true; to LocalSettings.php. I am not advocating this action, simply documenting this if it is ever so decided. (Added by Pyrrhus, April 2019)
  • IF it is ever decided to add a sitemap to MEpedia, here are possible instructions. This is not a suggestion, rather an attempt to document something which may be decided on in the future. (suggested by Notjusttired July 2019)
    • Add to LocalSettings.php:
$wgSitemapNamespaces = array( NS_MAIN, NS_FILE, NS_CATEGORY, NS_PORTAL , NS_PROJECT, NS_TALK, NS_HELP );
$wgSitemapNamespacesPriorities = array(
   NS_MAIN => '1.0',
   NS_FILE => '0.8',
   NS_PORTAL => '0.7',
   NS_CATEGORY => '0.6',
   NS_TALK => '0.3',
   NS_PROJECT => '0.1',
   NS_HELP => '0.0',
);
    • (Alternative, less helpful option if sitemap won't recognize some namespaces: $wgSitemapNamespaces = array( 0, 6, 14, 3006, 4, 1, 12 );
    • Create a "sitemap" directory in a publicly accessible directory eg /var/www/me-pedia.org. Ensure sitemap folder is accessible via external URL with read / execute access to everyone.
    • Create sitemap - first check fspath and urlpath in the following match the newly created sitemap directory.
php maintenance/generateSitemap.php --memory-limit=50M --fspath=/var/www/me-pedia.org/sitemap/  --identifier=MEpedia --urlpath=https://www.me-pedia.org/sitemap --server=https://www.me-pedia.org --compress=yes --skip-redirects

Developer: New backup protocol[edit | edit source]

Update backup protocol to more closely adhere to industry norms: (Requested by Pyrrhus May 2019)

  • Move the staging server's web root directory from /var/www/me-pedia.org to /var/www/staging/me-pedia.org. This will allow us to automatically detect whether or not the LocalSettings.php file is being used on the production or the staging server.
  • Update the production server's LocalSettings.php file as follows:

Change this:

## STAGING SERVER SETTINGS
## Pyrrhus, May 2019
if (strpos($IP, 'staging') !== false) {
   ## Basic settings for the staging server
   $wgServer = 'https://staging.me-pedia.org';
   $wgLogo = 'https://upload.wikimedia.org/wikipedia/commons/5/5e/Commons-emblem-Under_construction-green.svg';
   $wgEnableEmail = false;

   ## Database settings for the staging server
   $wgDBname = "";
   $wgDBuser = "";
   $wgDBpassword = "";
}

To this:

## STAGING SERVER SETTINGS
## Pyrrhus, May 2019
if (strpos($IP, 'staging') !== false) {
   ## Basic settings for the staging server
   $wgServer = 'https://staging.me-pedia.org';
   $wgLogo = "$wgScriptPath/images/c/c3/Under_construction_warning.svg";
   $wgLogoHD = false;
   $wgEnableEmail = false;
   $wgDefaultRobotPolicy = 'noindex,follow';
}
  • Download the Fullsiterestore.sh script from https://www.mediawiki.org/wiki/Fullsiterestore into the /home/cloud/backups directory on both servers. Verify that both servers already have a Fullsitebackup script in the same directory.
  • Update the cron job for the Fullsitebackup script to backup the production server once a month, not every 2 days, at midnight New York time. This will serve as the monthly portion of the backup protocol. (Assuming that each new monthly backup will overwrite the last monthly backup.)
  • Remove the cron job for the staging server backup, as changes to the staging server are so infrequent that it does not merit a regular backup, and we would rather save the disk space for multiple production backups, when possible. (We can always do a staging server backup manually when needed.)
  • Assuming that there is sufficient disk space to store an additional seven production backups, create 7 new cron jobs for each day of the week, run at 1:00am New York time. This will serve as the daily portion of the backup protocol. (Assuming that each new day-of-week backup will overwrite the last week's day-of-week backup.) This also assumes that the backup process takes less than 30 minutes to complete. If there is insufficient disk space, or if the backup process takes more than 30 minutes, please let us know!
  • Check the Fullsitebackup and Fullsiterestore scripts for the production server to make sure that the 5 configuration settings (dbname, dbhost, dbuser, dbpw, and webrootdir) are correct for the production server. (This will make sure that we can quickly restore backups when needed.)
  • Also check the Fullsitebackup and Fullsiterestore scripts for the staging server to make sure that the 5 configuration settings (dbname, dbhost, dbuser, dbpw, and webrootdir) are correct for the staging server.
  • In the production server's Fullsitebackup script, find the line that starts with mysqldump and add nice -n 19 to the front of it:
nice -n 19 mysqldump --host=$dbhost --user=$dbuser --password=$dbpw --add-drop-table $dbname > dbcontent.sql
  • Add the following code to the production server's Fullsitebackup script, right before the "TAR website files" section:
#
# Put MEpedia into read-only mode
#
echo " Placing MEpedia into read-only mode ..." >> $logfile
msg="\$wgReadOnly = 'We are currently performing a regular backup of MEpedia.  Access will be restored shortly.';"
grep "?>" "$webrootdir"/LocalSettings.php > /dev/null
if [ $? -eq 0 ];
then
	sed -i "s/?>/\n$msg/ig" "$webrootdir"/LocalSettings.php
else
	echo "$msg" >> "$webrootdir"/LocalSettings.php
fi 
  • Then add the additional following code to the production server's Fullsitebackup script, right before the "Create final backup file" section:
#
# Take MEpedia out of read-only mode
#
echo " Taking MEpedia out of read-only mode ..." >> $logfile
sed -i "/$msg/d" "$webrootdir"/LocalSettings.php
  • Add the following code to the end of the staging server's Fullsiterestore script, just before the "Exit Banner":
#
# Overwrite any production robots.txt with staging robots.txt
#
echo " overwriting robots.txt in $webrootdir ..." >> $logfile
cd $webrootdir
echo 'User-agent: *' > robots.txt
echo 'Disallow: /' >> robots.txt
chmod a+r robots.txt
  • Test the new backup script by making a backup of the production server. Check the log file for any errors. Note how long the backup takes to finish.
  • Next "re-image" the staging server to be the same as the production server. Use the staging server's Fullsiterestore script, along with the backup from the production server, to update the staging server with the latest copy of the production server. (The staging server is currently outdated.)
  • After restoring on the staging server, run the update.php script in the maintenance directory to update the database for the staging server. Also make sure that the OS file permissions are correct for the restored files, especially that the "uploads" directory is writable by the web server and that the extensions directories are executable by the web server. (Perhaps this can be accomplished by setting the user "apache" as the owner of the files?)
  • Finally, consider doing a one-time backup of MEpedia’s entire account, including the backup scripts, using Dreamhost’s one-click backup: https://help.dreamhost.com/hc/en-us/articles/215089918-How-do-I-backup-my-entire-account-

Discussion on backup:

Problems need not be fixed in 2 days, they only need to be identified - is this for server or database (ie MEpedia content only)? The norm would be a series of backups at different intervals, kept for different times - eg every 2 days, plus a weekly backup kept for at least a month, plus a monthly backup kept for at least a year. Changing the most frequent backup to 7 days means risking losing a week of editing. notjusttired (talk) 19:04, May 24, 2019 (EDT)
Thanks, you’re assuming that multiple backups are stored User:Notjusttired. Normally this is a perfectly correct assumption, but in our case it appears that only the most recent backup is stored and it is immediately overwritten by the next backup. Therefore, if we wait more than 2 days, the good backup will be overwritten with a corrupt backup. This is why I suggested that at least two backups be stored, so that we can back up at least twice a week. Maybe what we really should ask for is daily backups, with each backup kept for a week. Disk space is cheap, we should be able to store seven backups at a time. Hope this clarifies.
Pyrrhus (talk) 20:01, May 24, 2019 (EDT)
I'm still not sure if this is a database backup you are talking about, or the server backup. I'm unsure of the hosting plans and how far we are from the current limit. I believe that we should definitely keep some backups For than a week notjusttired (talk) 06:25, May 25, 2019 (EDT)
The Fullsitebackup script backs up all MediaWiki files, including the database. There is also a DreamCompute backup option here. Yes, it would be nice to have a monthly backup that is kept for a month, in addition to 7 daily backups kept for a week. We should be able to find enough disk space to store 8 backups at a time, although I know nothing about our hosting plan. Hope this clarifies, User:Notjusttired!
Pyrrhus (talk) 12:27, May 25, 2019 (EDT)

Developer: Install StructuredDiscussions[edit | edit source]

The following instructions are to be completed AFTER the “New Backup Protocol” request.

Prepare for StructuredDiscussions extension (PART ONE): (Requested by Pyrrhus May, 2019)

  • First comment out the two lines towards the end of the LocalSettings.php file that concern the DiscussionThreading extension on the production server. This effectively uninstalls the DiscussionThreading extension.
  • Also comment out the line in LocalSettings.php that says wfLoadExtension( 'NewUserMessage' );. This effectively uninstalls the NewUserMessage extension, which is not compatible with StructuredDiscussions.
  • Verify that the Echo extension is the latest version on production server. (Update requested Sep 2019)
  • Confirmed that ParserFunctions extension is the latest version on production server, MediaWiki 1.31 automatically includes parser functions. Add $wgPFEnableStringFunctions = true; to LocalSettings.php
  • Install new BetaFeatures extension on production server
  • Install new CLDR extension on production server (Requested within translation tasks Sep 2019)
  • Install new Thanks extension on production server (Requested Aug? 2019)
  • Backup production server with Fullsitebackup script
  • Use backup file to re-image the staging server. Use the staging server's Fullsiterestore script, along with the backup from the production server, to update the staging server with the latest copy of the production server. Run update.php script. Check that file permissions are correct. (uploads directory must be writable by the web server and extensions must be executable by the web server.)

Install StructuredDiscussions extension (PART TWO):

  • Set up a memcached daemon service on the staging server on port 11211:
    • First verify that PHP was compiled with “--enable-sockets” by running “php -i”. (If not, PHP must be recompiled.)
    • Install memcached as described here: https://github.com/memcached/memcached/wiki/Install
    • Configure memcached’s config file (or init script) to run with the following options:
memcached -d -l 127.0.0.1 -p 11211 -m 64 (More info may be found in the documentation included with the download.)

Replace

## Shared memory settings
$wgMainCacheType = CACHE_NONE;
$wgMemCachedServers = [];

with the following

## Shared memory settings
$wgMainCacheType = CACHE_MEMCACHED;
$wgSessionCacheType = CACHE_MEMCACHED;
$wgMemCachedServers = ["127.0.0.1:11211"];
php maintenance/populateContentModel.php --ns=1 --table=revision
php maintenance/populateContentModel.php --ns=1 --table=archive
php maintenance/populateContentModel.php --ns=1 --table=page 

php maintenance/populateContentModel.php --ns=3 --table=revision
php maintenance/populateContentModel.php --ns=3 --table=archive
php maintenance/populateContentModel.php --ns=3 --table=page 

php maintenance/populateContentModel.php --ns=5 --table=revision
php maintenance/populateContentModel.php --ns=5 --table=archive
php maintenance/populateContentModel.php --ns=5 --table=page 

php maintenance/populateContentModel.php --ns=7 --table=revision
php maintenance/populateContentModel.php --ns=7 --table=archive
php maintenance/populateContentModel.php --ns=7 --table=page 

php maintenance/populateContentModel.php --ns=9 --table=revision
php maintenance/populateContentModel.php --ns=9 --table=archive
php maintenance/populateContentModel.php --ns=9 --table=page 

php maintenance/populateContentModel.php --ns=11 --table=revision
php maintenance/populateContentModel.php --ns=11 --table=archive
php maintenance/populateContentModel.php --ns=11 --table=page 

php maintenance/populateContentModel.php --ns=13 --table=revision
php maintenance/populateContentModel.php --ns=13 --table=archive
php maintenance/populateContentModel.php --ns=13 --table=page 

php maintenance/populateContentModel.php --ns=15 --table=revision
php maintenance/populateContentModel.php --ns=15 --table=archive
php maintenance/populateContentModel.php --ns=15 --table=page

php maintenance/populateContentModel.php --ns=3007 --table=revision
php maintenance/populateContentModel.php --ns=3007 --table=archive
php maintenance/populateContentModel.php --ns=3007 --table=page
  • Add the following to LocalSettings.php on the staging server to define the namespaces for StructuredDiscussions:
$wgNamespaceContentModels[NS_TALK] = 'flow-board';
$wgNamespaceContentModels[NS_USER_TALK] = 'flow-board';
$wgNamespaceContentModels[NS_PROJECT_TALK] = 'flow-board';
$wgNamespaceContentModels[NS_FILE_TALK] = 'flow-board';
$wgNamespaceContentModels[NS_MEDIAWIKI_TALK] = 'flow-board';
$wgNamespaceContentModels[NS_TEMPLATE_TALK] = 'flow-board';
$wgNamespaceContentModels[NS_HELP_TALK] = 'flow-board';
$wgNamespaceContentModels[NS_CATEGORY_TALK] = 'flow-board';
$wgNamespaceContentModels[NS_PORTAL_TALK] = 'flow-board';
  • Finally, spend a week testing out both production and staging servers.
  • If both production and staging servers pass the tests, then repeat PART TWO on the production server and re-test.

LocalSettings.php changes[edit | edit source]

  • category changes to appear on Recent Changes list - set **$wgRCWatchCategoryMembership to true
  • allow recent changes to be up to 2 years ago (helpful for system messages or MEpedia documentation pages, will default to 30 days still), with options for 6 months, 1 year and 2 years ago added, and up to 1000 changes shown (currently limited to 90 days / 500 changes)- set
    • $wgRCMaxAge to 731 * 24 * 3600
    • $wgRCLinkDays to [1, 3, 7, 14, 30, 90, 180, 365, 731]
    • $wgRCLinkLimits to [50, 100, 200, 250, 500, 1000]
- added by User:Njt Sep 2019
  • Count Portal pages as content? This affects popular pages stats. But exclude them from the ShortPages count. - added User:Njt
$wgContentNamespaces = [ NS_MAIN, NS_PORTAL];
$wgShortPagesNamespaceBlacklist = [ NS_PORTAL];

Completed developer tasks[edit | edit source]

All completed tasks. Condensed...
Disallow: /wiki/MEpedia talk:
Disallow: /wiki/File talk:
Disallow: /wiki/Help talk:
Disallow: /wiki/Category talk:
Disallow: /wiki/Portal talk:
Disallow: /wiki/User:
Disallow: /wiki/User talk:
Disallow: /wiki/MediaWiki:
Disallow: /wiki/MediaWiki talk:
Disallow: /wiki/Template:
Disallow: /wiki/Template talk:
Is this done now? notjusttired (talk) 17:46, August 6, 2019 (EDT)
Yes! Pyrrhus (talk) 21:38, August 7, 2019 (EDT)
# Allow the Internet Archiver to index action=raw and thereby store the raw wikitext of pages
User-agent: ia_archiver
Allow: /*&action=raw 
UPDATE - how do we test this? (User:Notjusttired, May 22,2019)
Tested and workin notjusttired (talk) 18:48, May 24, 2019 (EDT)
Disallow: /wiki/Talk:
  • Create a user right group that automatically turns off the CAPTCHA after the user has made 50 edits - requested by Canele (talk) 18:26, 30 March 2019 (EDT)
One way to accomplish this is to add the following to LocalSettings.php. This will require 50 edits before a user is given the "autoconfirmed" role. (which is different from the "emailconfirmed" role) Pyrrhus (talk) 22:10, 16 May 2019 (EDT)
$wgAutoConfirmCount = 50;
$wgGroupPermissions['autoconfirmed']['skipcaptcha'] = true;
(hide)
(read more)

Withdrawn developer tasks[edit | edit source]

Tasks no longer needed since either another solution was found or they don't seem worthwhile given the work involved.

  • pivot not showing Potential treatments banner - fixed by User:Notjusttired with Common.js changes as suggested by User:Pyrrhus
  • all editors to see visitor stats eg popular pages or searched for terms - it's hard to know what topics to work on
Is this necessary? Popular pages are visible via the link in lefthand sidebar. I don’t know of any way to find “searched for” terms without a custom database query. Pyrrhus (talk) 19:21, 16 May 2019 (EDT) - withdrawn by Notjusttired - Google analytics is the best solution but no way to link it here
Could it be that this page list is updated daily or weekly rather than immediately? The example given is now sorted - I presume without any intervention. notjusttired (talk) 19:04, May 24, 2019 (EDT)
(hide)
(read more)

Images needed[edit | edit source]

Suggest an image and mark the page it's needed on with {{NeedsImage}}. See Category:Articles_that_need_an_image_or_photo.

Small tasks[edit | edit source]

When a task is complete move it to the COMPLETED section at the bottom of the page

Mensah, F.K.F., Bansal, A.S., Ford, B. and Cambridge, G., 2017. Chronic fatigue syndrome and the immune system: Where are we now?. Neurophysiologie Clinique/Clinical Neurophysiology, 47(2), pp.131-138. http://dx.doi.org/10.1016/j.neucli.2017.02.002 Immune system where are we now https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1440524/

Other suggestions[edit | edit source]

When a task is complete move it to the COMPLETED section at the bottom of the page

Historical articles[edit | edit source]

Add these articles:

There are also a very large number of resources here that need to be added: http://forums.phoenixrising.me/index.php?threads/historical-me-research-literature-and-related-information.10282/

Stem cell treatments[edit | edit source]

Info such as at http://www.bbc.com/news/health-35065905 and http://www.prohealth.com/library/showarticle.cfm?libid=14735 would be interesting to have. Brettz9 (talk) 11:37, 19 January 2016 (PST)

Treatments[edit | edit source]

A great rundown of infections related to ME/CFS and potential treatments. Link can be added to "Further reading" on the List of treatments page. Information here can also be included on the appropriate pages for specific infectious agents and specific antivirals. https://sites.google.com/site/cfstestingandtreatmentroadmap/ --JenB (talk) 09:24, 11 December 2015 (PST)

Basic biochemistry[edit | edit source]

Infectious disease[edit | edit source]

New study shows that EBV can infect neurons. Apparently we didn't know this before! http://www.meaction.net/2015/12/10/study-shows-epstein-barr-virus-can-infect-human-neurons/ Consider updating the Herpesvirus page with any relevant information. I think it would be really great to expand the EBV (and really all the herpesvirus pages) with information on the association of these viruses with both CFS and other diseases, especially those involving B cells and the possible infection of nervous tissue. --JenB (talk) 08:38, 16 March 2016 (PDT)

Completed[edit | edit source]

When a task is complete move it HERE

Developer Completed[edit | edit source]

content hidden
  • Add EmbedVideo extension from https://www.mediawiki.org/wiki/Extension:EmbedVideo to allow us to embed YouTube or Vimeo clips, eg Linda Crowhurst's on Severe M.E., videos for symptoms like muscle twitches, myclonus, and advocacy clips/explanations - the MEAnalysis PACE video for instance - this would help those with photophobia
  • WikimediaMessages added
  • Skins: Add a stable dark/dark grey skin that's mobile friendly (and migraine friendly) eg Timeless DarkCSS as custom CSS on Timeless skin - requested by User:Notjusttired
  • Skins: Add Pivot and Foreground (both mobile friendly), consider defaulting to Pivot for all mobile devices requested by User:Notjusttired
  • Add the Visual Editor to the “MEpedia:” and “Help:” namespaces so new contributors don’t need to learn wikitext to edit a page. To do this, first verify that "MEpedia" is listed in $wgExtraNamespaces in LocalSettings.php, then add the following to the LocalSettings.php file:

$wgVisualEditorAvailableNamespaces = [ "Help" => true, "MEpedia" => true ]; (Requested by Pyrrhus, Feb 2019)

  • allow search engines to crawl the Files namespace eg http://me-pedia.org/wiki/File:example.jpg so images come up when doing Google search on images for reuse requested by User:Notjusttired
  • Install AddThis extension for sharing - if poss with Facebook, Twitter and pinterest links showing - requested by [[User:
  • Turn on setting to autofix redirects in LocalSettings.php - as per Mediawiki configuration info - requested by User:Notjusttired
  • Can Citation bot be set up for all new users - see Wikipedia for link & institutions (Requester unknown)
This task has been abandoned because the required PHP compilation, template setup, and bot registration is beyond the capabilities of our developers. See https://github.com/ms609/citation-bot for more details. Pyrrhus (talk) 22:01, 22 May 2019 (EDT)
$wgMaxShellMemory = 524288;
$wgUserEmailUseReplyTo = true;
$wgVisualEditorEnableDiffPage = true;
  • Add the following to the end of LocalSettings.php to disable email on the staging server (staging.me-pedia.org): (Requested by Pyrrhus May 2019)
/* CHECK IF STAGING SERVER DETECTED */
if ((strpos($wgServer, 'staging') !== false) 
    or (strpos($IP, 'staging') !== false)) {
   $wgLogo = 'https://upload.wikimedia.org/wikipedia/commons/5/5e/Commons-emblem-Under_construction-green.svg';
   $wgEnableEmail = false;
}
  • Fix the wiki emailer so that new users can receive the “confirm your email account” email and so that established users can receive email notifications of changes, etc. (Requested by Pyrrhus, Feb 2019)
  • Edit pivot skin's Pivot.skin.php to set autocomplete to on for mobile devices only. notjusttired (talk) 18:52, May 24, 2019 (EDT)
  • Fix email sending from MEpedia. Either configure sendmail properly on the production server or configure $wgSMTP properly in the LocalSettings.php file. If we are going to use $wgSMTP, here are some links that provide the exact SMTP information to use: configuration and protocols. For $wgSMTP, one can set up a new email account called "donotreply@me-pedia.org" using the DreamHost dashboard: https://panel.dreamhost.com/index.cgi?tree=cloud.compute& This new email account can either reject all incoming mail or forward all incoming mail to mepedia @ meaction.net (requested by Pyrrhus May 2019)
  • Add $wgDismissableSiteNoticeForAnons=true; to LocalSettings.php file. (Requested by Pyrrhus May 2019)
  • Consider making the members of the "emailconfirmed" group visible only to administrators. There is a theoretical risk of email spam when anyone can see who has confirmed their email and who hasn't. To do this, simply add $wgImplicitGroups[] = 'emailconfirmed'; to LocalSettings.php. I am not advocating for this action, merely documenting this if it is ever needed. (Removed, since the members of emailconfirmed are already mostly invisible to the public.)

Completed in 2019[edit | edit source]

  • Categorize all uncategorized pages (list of uncategorized pages here: http://me-pedia.org/wiki/Special:UncategorizedPages)
  • Make sure this Lightning Process study is on the LP page https://www.ncbi.nlm.nih.gov/pubmed/26983138?dopt=Abstract
  • Add this UK TV segment about a patient https://www.youtube.com/watch?v=I8lsRlUhRps&feature=youtu.be Where? Added to pediatric page
  • Add a malaise image to the PEM page. If we can get a volunteer to have an image of them perhaps out at a cafe' (before) and two or three days later at home with the impact showing on their face (after) this would be a very helpful illustration. (Done with #TwoFacesofME Tweets)
  • Fix the email address "mepedia@meaction.net". It currently rejects emails with a "Google Groups Error". (Requested by Pyrrhus, Feb 2019)
  • Add significant ME/CFS (or related) Facebook groups to the Social media page. Canele (talk) 15:35, 29 March 2019 (EDT)
  • Fix the New User Message as suggested on the User talk:New user message talk page. The New User Message has already been moved to Template:Welcome, all that remains to be done is to delete the MediaWiki:Newusermessage-template page. (Requested by Pyrrhus, Feb 2019)
  • Add extra code to Common.css from Notjusttired/common.css (except for the end section that's commented out) - for alternating table rows and minor tweaks
  • Add these Google fonts to Common.css to make them available for all skins: Oswald, Oswald italic, Oswald italic small-caps, Oswald small-caps, Oswald bold italic, Oswald bold italic small-caps, Oswald bold, Oswald bold small-caps, Permanent marker, Permanent marker bold, use Oswald small-caps for MEpedia logo text. Let us know the CSS font family names for all fonts above. - notjusttired (talk) 10:58, May 25, 2019 (EDT)
  • Adapt/copy Wikipedia's general disclaimer to replace our current general disclaimer at MEpedia:General_disclaimer. The specific copy of Wikipedia's disclaimer to use is https://en.wikipedia.org/w/index.php?title=Wikipedia:General_disclaimer&oldid=860114216 Be sure to note that full URL address in the edit summary in a brief acknowledgement that our disclaimer has been adapted from theirs. (Requested by JaimeS June 2019)
  • Rewrite MEpedia:About according to the ideas raised on MEpedia talk:About. (Requested by Pyrrhus April 2019)
  • Mark all pages in the Category:MEpedia documentation and Category:MEpedia help categories as "semiprotected" by marking them as "Allow only autoconfirmed users" to edit them. Except for the "Sample page", which needs to be editable by all users. (And except for any talk pages, or any pages that are already protected and editable only by Administrators.) (Requested by Pyrrhus May 2019)
Not sure how/who needs to do this - is it a LocalSettings.php request that's outstanding? Should a semi-protection message by added to all first? notjusttired (talk) 16:12, August 11, 2019 (EDT)
An admin needs to mark those pages as “semiprotected”. That is all.
Pyrrhus (talk) 16:25, August 11, 2019 (EDT)

B cell - B lymphocyte, or a type of white blood cell, which is involved in the immune response by secreting antibodies to ward off infections. In mammals, they are mostly matured in the bone marrow.

Canadian consensus criteria (CCC) - A set of diagnostic criteria used to diagnose ME/CFS, developed by a group of practicing ME/CFS clinicians in 2003. The CCC is often considered to be the most complex criteria, but possibly the most accurate, with the lowest number of patients meeting the criteria. Led to the development of the International Consensus Criteria (ICC) in 2011.

Myalgic encephalomyelitis (ME) - A disease often marked by neurological symptoms, but fatigue is sometimes a symptom as well. Some diagnostic criteria distinguish it from chronic fatigue syndrome, while other diagnostic criteria consider it to be a synonym for chronic fatigue syndrome. A defining characteristic of ME is post-exertional malaise (PEM), or post-exertional neuroimmune exhaustion (PENE), which is a notable exacerbation of symptoms brought on by small exertions. PEM can last for days or weeks. Symptoms can include cognitive impairments, muscle pain (myalgia), trouble remaining upright (orthostatic intolerance), sleep abnormalities, and gastro-intestinal impairments, among others. An estimated 25% of those suffering from ME are housebound or bedbound. The World Health Organization (WHO) classifies ME as a neurological disease.

B cell - B lymphocyte, or a type of white blood cell, which is involved in the immune response by secreting antibodies to ward off infections. In mammals, they are mostly matured in the bone marrow.

Myalgic encephalomyelitis (ME) - A disease often marked by neurological symptoms, but fatigue is sometimes a symptom as well. Some diagnostic criteria distinguish it from chronic fatigue syndrome, while other diagnostic criteria consider it to be a synonym for chronic fatigue syndrome. A defining characteristic of ME is post-exertional malaise (PEM), or post-exertional neuroimmune exhaustion (PENE), which is a notable exacerbation of symptoms brought on by small exertions. PEM can last for days or weeks. Symptoms can include cognitive impairments, muscle pain (myalgia), trouble remaining upright (orthostatic intolerance), sleep abnormalities, and gastro-intestinal impairments, among others. An estimated 25% of those suffering from ME are housebound or bedbound. The World Health Organization (WHO) classifies ME as a neurological disease.

Myalgic encephalomyelitis (ME) - A disease often marked by neurological symptoms, but fatigue is sometimes a symptom as well. Some diagnostic criteria distinguish it from chronic fatigue syndrome, while other diagnostic criteria consider it to be a synonym for chronic fatigue syndrome. A defining characteristic of ME is post-exertional malaise (PEM), or post-exertional neuroimmune exhaustion (PENE), which is a notable exacerbation of symptoms brought on by small exertions. PEM can last for days or weeks. Symptoms can include cognitive impairments, muscle pain (myalgia), trouble remaining upright (orthostatic intolerance), sleep abnormalities, and gastro-intestinal impairments, among others. An estimated 25% of those suffering from ME are housebound or bedbound. The World Health Organization (WHO) classifies ME as a neurological disease.

ME/CFS - An acronym that combines myalgic encephalomyelitis with chronic fatigue syndrome. Sometimes they are combined because people have trouble distinguishing one from the other. Sometimes they are combined because people see them as synonyms of each other.

Myalgic encephalomyelitis (ME) - A disease often marked by neurological symptoms, but fatigue is sometimes a symptom as well. Some diagnostic criteria distinguish it from chronic fatigue syndrome, while other diagnostic criteria consider it to be a synonym for chronic fatigue syndrome. A defining characteristic of ME is post-exertional malaise (PEM), or post-exertional neuroimmune exhaustion (PENE), which is a notable exacerbation of symptoms brought on by small exertions. PEM can last for days or weeks. Symptoms can include cognitive impairments, muscle pain (myalgia), trouble remaining upright (orthostatic intolerance), sleep abnormalities, and gastro-intestinal impairments, among others. An estimated 25% of those suffering from ME are housebound or bedbound. The World Health Organization (WHO) classifies ME as a neurological disease.

The information provided at this site is not intended to diagnose or treat any illness.
From MEpedia, a crowd-sourced encyclopedia of ME and CFS science and history.