Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. 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?
  3. 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, ~~~~
  4. Earlier
  5. 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.
  6. 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.
  7. 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
  8. 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.
  9. 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.
  10. 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
  11. 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!
  12. 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...
  13. Guest

    Tables & Templates

    Very new to wiki 'stuff' and I hope this is the right place to ask: I'm trying to create a template for tables, and a template for rows. Here's what I have so far: {{Template:Table |class=wikitable|sortable=sortable|collapsible=mw-collapsible|collapsed=mw-collapsed|style_center="text-align: center;" |caption_style="text-align: left; width: 200px"|caption=Table 1 |header1=My Header1|header2=My Header2|header3=My Header3|header4=My Header4 }} Template:Table {| class="{{{class}}} {{{sortable}}} {{{collapsible}}} {{{collapsed}}}" style={{{style_center}}} |+style={{{caption_style}}}|{{{caption}}} ! scope="col" | {{{header1}}} !! scope="col" | {{{header2}}} !! scope="col" | {{{header3}}} !! scope="col" | {{{header4}}} |- |{{Template:Table_Row| cell_value1 = Row 1 Cell 1}} |} Template:Table_Row {| |data-sort-value="{{{cell_value1}}}"|[[{{{cell_value1}}}]] |} The template for the table works fine, well what I see is what i expected to see. It's getting the rows added to the table that causing the frustration. It could be that I am way off and making this much more difficult than it needs to be! Eventually I want to be able to create a table with a variable number of rows...but just trying to get even basics to work. Thanks very much in advance!
  14. Skizzerz

    AutoCategoriseUploads

    Version 1.0.0

    2 downloads

    This extension automatically adds categories to new file uploads based on keyword metadata found in the file. The following metadata types are supported: XMP (many file types, including JPG, PNG, PDF, etc.) ITCP (JPG) ID3 (MP3) Categories are added to new uploads only (that is, uploads where a file description page does not already exist). This lets editors modify the categories without needing to worry about new versions of the file overwriting their changes. Any form of uploading is supported, whether that is via Special:Upload, the UploadWizard extension, uploading files via the API, or maintenance scripts to bulk-upload files. For installation instructions, please see the documentation page on MediaWiki.org. It is recommended that you "Follow" this download so that you can be notified automatically whenever there are updates. For support, please post a new topic on the forums. Free support is provided on a best-effort basis. Commercial support for this extension is available by purchasing a MediaWiki Support Subscription.

    Free

  15. Guest

    Démarche LUAsandbox

    Hi! i need compiled LUASandBox for php7.1.9 on windows to install on mediawiki, someone have it to share?
  16. Skizzerz

    Cannot find MediaWiki 1.3.0 RPM

    MediaWiki is not officially distributed via RPM. A number of RPMs have been created as unofficial community efforts, but due to the nature of this they often lag behind official releases. It is not recommended that you install MediaWiki via RPM, and instead download the tarball from the MediaWiki website and install it that way. If you want to create your own RPM, you'll need a fair bit of knowledge both in how RPMs are packaged as well as knowledge of how to install MediaWiki from the command line (CLI) by using the install.php maintenance script. I cannot provide much in the way of guidance in this matter as I don't have any experience in packaging RPMs. A second side-note regarding version numbering: don't treat the dot as a decimal point, but rather as a separator. MediaWiki versioning follows the standard of major.minor.patch. The version 1.3.0 is therefore major version 1, minor version 3, and patch version 0. 1.3.0 is ancient and no longer developed (and would be difficult to obtain). The most recent stable version of MediaWiki is 1.30.0, or major version 1, minor version 30, and patch version 0. 1.30.0 is 27 versions newer than 1.3.0.
  17. I've been looking for the MediaWiki 1.3.0 RPM. I cannot find it anywhere online. Do you have a copy of this RPM to distribute? Else, do You have the instructions on how to create RPM?
  18. I've now gotten around this by taking all code out of Common.js and using other methods instead.
  19. I've reduced Common.js to the bare minimum, which passes a JS validator, but the code still isn't being loaded. (The validator complained about the <script> tags so I took them out but I've tried both with and without and neither way works.) $wgUseSiteJS = true; Any ideas?
  20. Skizzerz

    Common.js problem -- script missing

    Your Common.js page has syntax errors, which is why nothing is running. The Common.js page is for js only, whereas you put HTML into that page.
  21. Trying to get statistics page tracking working on a new wiki: https://cardanowiki.info The first stats service tried (Statcounter Free) is working fine, using a script on MediaWiki:Common.js However, we'd prefer to use a different one: Matomo (was called Piwik). There was a problem with the MW extension so we switched to the alternative method of putting a script on Common.js But no stats are being recorded. So I look at the page source coming back to the browser and, though I can see the Statcounter script, there is no sign of the Matomo one. I tried swapping the order of the scripts but that made no difference. Any suggestions?
  22. Skizzerz

    Editing the Index page

    Do not edit any of the .php files that MediaWiki ships with. If you want to edit the content of your wiki pages, make use of the "Edit" tab while logged into your wiki. If you want to implement custom code, write or install an extension. In any case, never edit the core .php files -- doing so will make future upgrades incredibly difficult as any custom modifications to core .php files are completely lost on upgrades and need to be reapplied (unlike extensions, which stick around). Furthermore, the core code changes in structure a lot between versions, and unless you're keeping up with MediaWiki development, your custom hack that works in one version may not work in the next one without significant rewrites.
  23. Carey

    Editing the Index page

    Hi! I am trying to edit code on the home page. The code on the page says (with "enable edit") that the code is on the index.php page, as you would expect. But when I open the page in an editor (I tried Sublime and Komodo), I get a page that does not have much code but instead has this written at the top. This is the main web entry point for MediaWiki. * * If you are reading this in your web browser, your server is probably * not configured correctly to run PHP applications! * * See the README, INSTALL, and UPGRADE files for basic setup instructions * and pointers to the online documentation. I have read the readme, install, and upgrades files, and searched around in databases, but I can't figure out how to get to the code that apparently is on this page. What am I doing wrong? Thanks, -Carey Later Addition to this question/ post: As I keep digging into this, I have a suspicion that I have been sent in the wrong direction with the statement "your server is probably not configured to correctly run PHP applications", as the message says. I suspect that the real issue is that the code for the Index page (and likely most of the pages) is WRAPPED/protected and therefore not able to be directly edited in any way, no matter what I do or how I configure my server. I suspect that the only way to "edit" these pages is to add on script that can be read along with the wrapped code, and the media-wiki community calls these add-on codes "applications", which explains why everything has to be done with applications that someone else has pre-created or you create yourself instead of just messing with the page code. IS THIS ACCURATE? Thanks, -Carey
  24. Thanks a lot for your answer. I will try your suggestion and revert with the result. Kind regards, Christophe
  25. Skizzerz

    Allow user to Input a variable in an inputbox

    This is unfortunately not possible with just the Inputbox extension. You may be able to make use of the Page Forms extension for this purpose (it's part of Semantic MediaWiki but can be installed standalone if you don't want all of SMW installed). However, I've never actually tried it out myself so I cannot say for certain whether or not it will work. You can grab the extension at https://www.mediawiki.org/wiki/Extension:Page_Forms
  26. I had a wiki working six months ago but before I had it backupped I had a hardware malfunction and had to start over again. Ever since I have tried to get infobox working. I would like it to look like this: https://sv.wikipedia.org/wiki/Jimmy_Wales but it looks like this: http://www.skutan.com/wiki/index.php/Testedvin What am I missing? Is it a missing .css? I have googled a lot so any help would be much appreciated.
  27. Hello, I installed MediaWiki 1.29.1 with the Variables and ExternalData extensions. I created pages in which a predefined variable in the body of the page calls external data from a csv file filtered on this variable and returning a table with all the results. I would now like to leave the choice of this variable to the user. It seems that the Inputbox does not allow to assign user's input to a variable. I would not want this entry to create a new page nor a section but serve as a filter to my external data called in the table in the same page / section. I would like to avoid having to install Semantic Mediawiki which seems to provide this possibility. Can someone help me to this point on which I have been blocking for several days. Thank you in advance. Christophe, from Paris.
  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.