PseudoTalkPages is a small JS snippet that adds a "Talk Page" tab to user pages on wikis equipped with message walls. It can be paired with UserTalkNotifications. For the script to work as intended, all talk pages must be created on user subpages titled "Talk," an example being /wiki/User:Eizen/Talk.

The script was initially implemented in pieces on the wiki, and as Staff code reviewers apparently had no issues with the script's implementation, it was added to the Dev Wiki.

With the implementation of the new FANDOM header, much of the code that changed the physical appearance of the pseudo talk page to look like an actual talk page was rendered unusable. As such, the current version of the script simply adds the talk page tab to the user page in both Oasis and Monobook.


See also: Help:Including additional CSS and JS, Help:Advanced CSS and JS
  • For site-wide use, an administrator can add the line below to the wiki's MediaWiki:ImportJS page.
  • For personal use, add the code snippet below to your global.js page (for use on all wikis) or your common.js page on your wiki (for use on a single wiki). Note that personal JS must be enabled for your account.
    type: 'script',
    articles: [
importArticles — Best Practices for installing JavaScript on FANDOM

The importArticles statement is designed to combine multiple HTTP requests into a single data transfer, allowing multiple scripts to load and execute faster. If you've been installing several different scripts, your JavaScript file has probably accumulated unnecessary import statements. Click "Expand" to learn how to efficiently batch import scripts to speed up performance and make your code look cleaner. One other approach is by using the MediaWiki:ImportJS.

If your JavaScript file has several lines of code that say importScript, importScriptPage, or importArticles, you may be able to combine them! By batch importing a collection of scripts with a single import, your JavaScript code will load faster and look cleaner. Consider the example below. On the left is an example of what your JavaScript file might currently look like. On the right is how you could improve that code.

Multiple imports — messy and slow One import — clean and efficient
  type: 'script',
  article: 'u:dev:FloatingToc/code.js'
importScriptPage('page1.js', 'wikiname');
importScriptPage('page2.js', 'wikiname');
  type: 'script',
  articles: [

Note: In this example, pay close attention to the placement of commas and other punctuation. For people who aren't familiar with programming (and even those who are!), a common mistake when writing code is to accidentally delete, forget, or misplace critical symbols like commas or quotation marks. This can cause a syntax error that breaks the code. Carefully follow the convention shown here when using importArticles.

But there's much more to importArticles than just this! For more examples and advanced usage, see the help page at Help:Including additional JavaScript and CSS.


Initial revision
Minor bug fixes
Various modifications
Monobook support; general rewrite
Removal of outdated content; rewrite/simplification
Forbid tab from being appended to anon user pages