Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. Earlier
  3. Thanks for your help.
  4. That is being created by the CharInsert extension combined with the MediaWiki:Edittools page on your wiki. The link to the extension contains more documentation and examples of how to set it up. More advanced uses (such as what you see on Wikipedia with the "Insert" drop-down) also require the Gadgets extension.
  5. I am building a wiki and I was browsing Wikipedia pages to learn more about formatting and templates when I saw this bar at the bottom of the edit window to insert different characters and wiki markups. I was hoping someone here can tell me which extension is being used to add this to the editor or if it isn't even an extension how I would go about adding it to the edit page.
  6. Thank you! I get lost between when it's messages, CSS, or the skin itself that is place to modify different outputs. Or even differentiating between which elements do what. Much appreciated.
  7. Method 1: Create or edit the page on your wiki MediaWiki:Retrievedfrom while logged into an Administrator account and delete the contents (so it is a completely blank page). That should suppress the message from appearing at all. Method 2: Create or edit the page on your wiki MediaWiki:Common.css while logged into an Administrator account and add the following code to the bottom: /* hide the "Retrieved from" message */ .printfooter { display: none; }
  8. First, I didn't know mwusers was back!! I looks great! I'm trying to suppress the 'retrieved from' footer from the printable version of an article. I have no idea where I might override this (do I have to hack the skin?) Using MW 1.23.2 (Vector). Thanks!
  9. These are called "Page status indicators." You can read more about them here.
  10. Fully Managed MediaWiki Hosting

    A fully managed hosting plan lets you not have to worry about MediaWiki installation or upgrades; you only need focus on your wiki, its content, and its community. Our professional staff takes care of the rest.

    What We Include:

    • 99.9% Uptime SLA. If in any given month the service is available less than 99.9% of the time outside of scheduled maintenance for reasons under our control, you may request a full refund for that month as store credit.
    • Fully Managed MediaWiki Install and Upgrades. We'll take care of installing MediaWiki for you as well as keeping it up-to-date. We'll take care of any configuration you may want, and will install approved extensions and skins for you as well. You don't need to worry about any of the technical stuff, just focus on your content and community.
    • Fast Server. Our server runs on SSDs in RAID1 for fast loading times. We also have a gigabit connection to the outside world, so busy sites don't get bogged down.
    • Daily Backups. We keep backups of your files and databases in multiple locations both on-site and off-site, to give you piece of mind in case something goes wrong.
    • Free SSL Certificates. Provided by LetsEncrypt.
    • cPanel Access. You will have full access to your server's files and databases, so you can install other self-managed applications alongside MediaWiki. cPanel also lets you set up and manage email accounts attached to your domain, among a myriad other features.
    • Custom Requests. 1 hour of server administration work is included each month to service custom requests with your hosting account outside of our normal management service. Additional work on top of this will be billed at a discounted rate of $30/hour (normally $40/hour). Custom development is not included.
    • 10 GB of disk space. Additional disk space available for a fee.
    • 100 GB of bandwidth per month. Additional bandwidth available for a fee.

    From $40.00

  11. Professional server administration performed by MediaWiki Users staff.

    Before purchasing this item, please contact our staff by submitting a Pre-Sales Questions support ticket describing your project so that we can give you an estimate. This item is valid for 1 hour's worth of work (2 hours minimum per project). Examples of work that can be performed:

    • Upgrading software necessary to run MediaWiki (web server, PHP, database, operating system, etc.).
    • Configuring MediaWiki or related software for enhanced security, functionality, or fixing configuration issues.
    • Skinning MediaWiki to be consistent with brand standards.

    After purchasing this item, you will be contacted for additional details and to schedule the work. Urgent requests should denote that so they may be prioritized, additional fees apply.

    All work done does not include ongoing support and maintenance.

    Pre-payment is required for the first 2 hours of work. Payment in full is due upon completion of work.

    Return Policy: All pre-paid server administration work is fully refundable so long as work has not yet begun. Once work begins in each 1-hour block, that block is no longer refundable. Once the project is complete, all unused 1-hour blocks will be automatically refunded. You cannot "bank" blocks for later.

    Disclaimer of Warranty: EXCEPT AS EXPRESSLY SET FORTH IN THIS SERVICES AGREEMENT, THE SERVICES TO BE PURCHASED UNDER THIS SERVICES AGREEMENT ARE FURNISHED AS IS, WHERE IS, WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE.

    $40.00

  12. Basically the title. I want to know how to get a lock icon like the one that Wikipedia has for protected pages. I just want one lock, not different types for different types of protection. Thanks in advance!
  13. Ultra03

    MinervaNeue text formatting not loading

    I ended up fixing it by deleting my MediaWiki installation and using the latest version of MW, MobileFrontend, and MinervaNeue (1.31 vs 1.30). Weird. Thanks for your help.
  14. Skizzerz

    MinervaNeue text formatting not loading

    Could be a number of things; do you have a link to your wiki that you can share? This would let me poke around with my browser devtools and see if I can uncover anything (perhaps there are permissions issues accessing the files, or its looking in the wrong place, or there's a version mismatch between your MobileFrontend/MinervaNeue version and MediaWiki version, or it could be working just fine now but a bad cache is making it appear to not be the case)
  15. Ultra03

    MinervaNeue text formatting not loading

    Unfortunately, that didn’t work either (although I just reread the install instructions and it mentioned that). What’s going on here?
  16. Skizzerz

    MinervaNeue text formatting not loading

    Try putting the wfLoadSkin underneath the wfLoadExtension call; I believe the order is important here and loading the skin first will cause issues.
  17. The MinervaNeue skin on my MediaWiki installation is not loading the text formatting of the wiki. The attached image is an example: https://i.stack.imgur.com/GLEOn.png And here is where I load it up in LocalSettings.php: wfLoadSkin( 'MinervaNeue' ); wfLoadExtension( 'MobileFrontend' ); $wgMFAutodetectMobileView = true; $wgMFDefaultSkinClass= "SkinMinerva"; The Vector skin doesn't give me any issues (but it isn't mobile-friendly, either). Does anyone have a solution for this?
  18. This indicates a misconfiguration in your email settings in MediaWiki. Can you please post the relevant bits of your LocalSettings.php that relate to email?
  19. Hello i recently was confirming my email in my mediawiki project and received this message, why is this occurring? This my frecuently email: naturistaneptali@gmail.com. Please help me, best regards, ~~~~
  20. Skizzerz

    MediaWiki 1.31 LTS Now Available

    MediaWiki 1.31.0 has now been officially released. This is a Long Term Support (LTS) release, meaning it will receive bugfixes and security updates for a period of 3 years (until June 2021). Below is a highlight of some of the release notes. To view the full release notes, click here. New System Requirements MediaWiki 1.31 now requires PHP 7.0 or higher. HHVM 3.18.5+ is still supported, but any users still on HHVM should look into migrating into PHP 7, as HHVM will no longer be supported in the future as Facebook will be dropping PHP support from the product. More Bundled Extensions The following extensions are now bundled with the MediaWiki download: CodeEditor -- provides a more friendly editing UI when editing CSS and JS pages MultimediaViewer -- opens clicked images in a lightbox instead of leading directly to the image page OATHAuth -- provides 2-factor authentication (2FA) support using apps such as Google Authenticator Replace Text -- provides a special page for admins to perform replacements across multiple pages of the wiki, for both page content and page titles Upgrading When upgrading MediaWiki versions, it is always important to take a backup of both your files as well as your database, as upgrades cannot be "rolled back" once performed. It is recommended to unpack the new files into a new, empty directory and then move over needed files (LocalSettings.php, images, extensions, skins) rather than unpacking the new files directly over the old ones. Unpacking over the old ones could cause files that were removed in 1.31 to remain in your directory tree, which could cause PHP errors down the line or cause security issues as those files will no longer be updated. The database changes in this release could take a while to run on large wikis.
  21. Skizzerz

    HTTPS Help

    You'll possibly need to modify some settings in LocalSettings.php as well. If you have any things in .htaccess, they may also need changes. As a note, when doing custom ports the port goes after the server name and before the path, e.g. https://example.com:82/mediawiki The redirect in your conf is technically unnecessary so long as you hardcode https into $wgServer in MediaWiki itself -- in that case, the wiki will take care of redirecting the user. Once you have everything working, set up HSTS (HTTP Strict-Transport-Security) so that visitors' browsers will automatically use https in the future.
  22. Guest

    HTTPS Help

    I have been doing a lot of browsing to set my mediawiki up to use HTTPS only. I created my key, i adjusted default.conf to have a virtual host at 81 for the http portion of the site initially and it worked perfectly. I added a permanent redirect into that virtual host and then added a new virtual host at 82 which is where I want my https port to be. I edited default-ssl.conf to point to my server. I updated ports.conf for port 82. I ran a2enmod ssl, headers, default-ssl, and ssl-params and apache2ctl configtest shows syntax ok. I can access the apache default page on both http and https. Accessing http://server/mediawiki:81 forwards me to https://server/mediawiki:82mediawiki/ for some reason and says can't connect to site which is obvious. However manually entering https://server/mediawiki:82 also says can't connect to site. default.ssl default.conf
  23. I usually prefer the non-www URL for my website (http://example.com, not http://www.example.com). While submitting the site to Google one needs to set a preferred domain by choosing either the www or the non-www version of URL. Then, during submitting the sitemap, only the sitemap containing the preferred version of URL should be submitted to Google search console. I have a website run by MediaWiki software. It uses a PHP script (named generateSitemap.php, it is bundled with the MediaWiki installation package) to create the sitemaps. One can set cron jobs to automate the process of updating sitemap at regular intervals. The problem is my sitemaps are being generated containing the www version of the webpages. How should I instruct the programs to generate sitemaps without www in the URLs? Please help.
  24. Skizzerz

    Tables & Templates

    Take another read through https://www.mediawiki.org/wiki/Help:Tables For putting multiple columns in a single line, use !! to separate them for header rows and || to separate for normal rows. If you have formatting, match the ! or |. {| class="wikitable" |+ Caption ! scope="col" style="color:red" | Column 1 !! scope="col" style="color: blue" | Column 2 !! scope="col" style="color: green" | Column 3 |- | data-sort-value="R1C1" | [[R1C1]] || data-sort-value="R1C2" | [[R1C2]] || data-sort-value="R1C3" | [[R1C3]] |- | data-sort-value="R2C1" | [[R2C1]] || data-sort-value="R2C2" | [[R2C2]] || data-sort-value="R2C3" | [[R2C3]] |} Produces the following: If that is what you are doing, try doing each column on its own line, or make use of HTML table markup (<table>, <tr>, <th>, and <td>) instead of using wiki markup for tables.
  25. Guest

    Tables & Templates

    Well I don't know what happened. I entered the code as you described and it worked perfectly as of late this past Wednesday. I checked with the admin and there have been no updates or extension allied since then. I asked for a reboot and that was done. Still fails. I went to go start implementing the templates and it seems the parser isn't working quite right, or the default template{!}. There seems to be a problem with the optHeader and maybe the optRow templates (row may be incorrect because columns are incorrect). Output, Instead of creating a new column for each parameter sent (I used all 6 for example purposes), the parser is combining columns 2 thru 6 together: Second column header !! scope = "col" | Third column header !! scope - "col" | etc.. optHeader: {{#if:{{{1|}}}| !! scope="col" {{!}} {{{1}}} }}. optRow: {{#if:{{{1|}}}| {{!}}{{!}} data-sort-value="{{{1}}}" {{!}} [[{{{1}}}]] }}. Header (part of it): ! scope="col" | {{{1}}} {{Template:Table_optHeader|{{{2|}}}}} {{Template:Table_optHeader|{{{3|}}}}} {{Template:Table_optHeader|{{{4|}}}}} {{Template:Table_optHeader|{{{5|}}}}} {{Template:Table_optHeader|{{{6|}}}}} Row: |- | data-sort-value="{{{1}}}" | [[{{{1}}}]] {{Template:Table_optRow|{{{2|}}}}} {{Template:Table_optRow|{{{3|}}}}} {{Template:Table_optRow|{{{4|}}}}} {{Template:Table_optRow|{{{5|}}}}} {{Template:Table_optRow|{{{6|}}}}} Any thoughts? Rick
  26. Guest

    Tables & Templates

    Thanks a ton for the response. I've been beating my head against my desk for more hours than I'd like to admit. As far as being to complicated, being new to all this my thought was to keep 'code' as clean as possible. It's not a stretch for me to agree that I made it overly complicated. I think where I might have gone a little too far is the idea that when I get DPL working, and therefore I would have a variable number of rows per table, I needed to segregate the row template from the other templates. I will read through and make sure I thoroughly understand what you've posted. Thanks again!
  27. Skizzerz

    Tables & Templates

    In MediaWiki markup, {| indicates the beginning of a new table and |} the end of a table. Your table row template should therefore not include those lines. I'm not entirely sure why you want to turn this into a template (as it is, in my opinion, more complex than just putting the raw table syntax on the page). If you do want to go down this route, you'll need to split things into 3 templates instead of wrapping it all into a single call to {{Table}}: [[Template:Table header]] would contain the table header, along with the parameters to make it sortable, collapsible, etc. [[Template:Table row]] (or just [[Template:Row]] if you want to save typing) would contain the markup to create a single row [[Template:Table footer]] would contain the final closing markup |} for the table and any other footer data you want Perhaps something like the following: Template:Table header {| class="wikitable {{#if:{{{sortable|}}}|sortable}} {{#if:{{{collapsible|}}}|mw-collapsible}} {{#if:{{{collapsed|}}}|mw-collapsed}}" {{#if:{{{center|}}}|style="text-align: center"}} {{#if:{{{caption|}}}| {{!}}+ {{#if:{{{caption-style|}}}|style="{{{caption-style}}}" {{!}} }} {{{caption}}} }} ! scope="col" | {{{1}}} {{optheader|{{{2|}}}}} {{optheader|{{{3|}}}}} {{optheader|{{{4|}}}}} {{optheader|{{{5|}}}}} {{optheader|{{{6|}}}}} Template:Optheader {{#if:{{{1|}}}| !! scope="col" {{!}} {{{1}}} }} Template:Table row |- | data-sort-value="{{{1}}}" | [[{{{1}}}]] {{optrow|{{{2|}}}}} {{optrow|{{{3|}}}}} {{optrow|{{{4|}}}}} {{optrow|{{{5|}}}}} {{optrow|{{{6|}}}}} Template:Optrow {{#if:{{{1|}}}| {{!}}{{!}} data-sort-value="{{{1}}}" {{!}} [[{{{1}}}]] }} Template:Table footer |} Then, you would use it as follows: {{table header |sortable=1 (if you want it to be sortable, otherwise leave this line out) |collapsible=1 (if you want it to be collapsible, otherwise leave this line out) |collapsed=1 (if it's default collapsed, otherwise leave this line out) |caption-style=font-weight: bold; ... (optional, you can leave this line out if no style) |caption=Caption goes here (optional, you can leave this line out if no caption) |First column header (required) |Second column header (optional, you can leave this line out) |Third column header (optional, you can leave this line out) |Fourth column header (optional, you can leave this line out) |Fifth column header (optional, you can leave this line out) |Sixth column header (optional, you can leave this line out) }} {{table row|Row 1 Cell 1|Row 1 Cell 2|Row 1 Cell 3|Row 1 Cell 4|Row 1 Cell 5|Row 1 Cell 6}} {{table row|Row 2 Cell 1|Row 2 Cell 2|Row 2 Cell 3|Row 2 Cell 4|Row 2 Cell 5|Row 2 Cell 6}} ... {{table footer}} First header and first cell are required, 2-6 are optional and are left out if omitted. If you aren't familiar with template syntax, there are a lot of tricks being used here. The #if parser function tests if a value is blank or not. If not blank, it outputs the text. Requires that Extension:ParserFunctions is installed (it is bundled with every mediawiki download) Numbered parameters don't require you to specify the name of them when calling the template; they're taken as positional unnamed parameters. You can still explicitly specify the name though (as 1=Value or 2=Value) -- which is required if the Value contains an = sign. The syntax {{{1|}}} means "If the parameter 1 was passed in, use the value for that. Otherwise use the value after the pipe, which in this case is blank/empty. This plays nicely into trick #1 above. The {{!}} built-in template expands to the pipe character |. Since | has a special meaning inside of templates, {{!}} is used to "escape" the pipe so it doesn't get looked at as part of the template, but rather as part of the resulting table markup. Overall though, this is probably more complicated than just encoding the table markup directly on the pages where you care about it...
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?

    Sign Up
×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.