Jump to content

All Activity

This stream auto-updates     

  1. Yesterday
  2. Last week
  3. Hi everyone! Is it possible to show the whole(!) file name while browsing in categories? See my screenshot for an example: I'm looking at my category "Agrar / Ernährung". It shows several files and you can read the first letters of each file. In my case the file name is important, so I'd like to have it shown completely (maybe over 2-3 rows instead of only 1). Does anyone know how I make this work?
  4. Earlier
  5. Namespaces are generally the recommended way of going about this. As you've discovered, you do need to specify the namespace in each link, however. There is no way to avoid this without an extension, although you can work around it by using a template that auto-fills the current namespace instead of directly using link markup.
  6. I created a wiki site using miraheze for a project with several independent groups who will create an individual wiki that I need to monitor the progress of. The problem I am facing is that group articles keep colliding with one another. So if group A makes a page called "Focus Group" then group B would have to make a differently named page or it would link back to group A page. Since each group will have over 100 articles this will become a nightmare for the 10+ groups to manage. I tried using namespaces, however, this did not accomplish my intended result as now a page would be "GroupA:Focus Group", "GroupB:Focus Group". I was hoping the namespaces would create more of a separate branch, so a link to "Focus Group" would go to the focus group page within the namespace. Apparently that is not the case (or I am doing something wrong). At this point it seems like the best solution would be to just create separate wikis for each of the groups, however, that will add a LOT of time to function as an admin for 10+ wiki pages independently. Is there a better solution???
  7. You'll want to install some anti-spam extensions. I recommend ConfirmEdit (adds a CAPTCHA) and AbuseFilter (lets you manually define filters that can block edits) at a minimum. This will prevent spambots from being able to easily sign up and create spam pages on your wiki. For the email issue, I can't really say what may be going on there. It could just be confirmation emails, because I'm not aware of any active security vulnerabilities that allow users to send email to arbitrary other addresses via the wiki.
  8. I'm fighting with Wikimedia installation. Months ago, my provider alert me that one of my sites, the one that use Wikimedia, had spammed a lot of porn email everywhere. In the db, I've found a lot of users and the table (prefix)text was overload of records. My provider had blocked my site and I've not checked the situation anymore, that's why the site was not in production. Now, I've ported the site from the provider to my server and, after porting, the tables I've told before was full again of spam, just after cleaning all the garbage. Today, I've decided to install a fresh new one of Wikimedia, ver. 1.34.1, starting from scratch. After few minutes from installing Wikimedia, the tables (prefix)text and (prefix)user and others was totally full of garbage again and the mail server has spammed a lot of emails. I've no idea what could be the problem. I've other three sites on that hardware and there was no problem. In which way they can do that? My VM is a Ubuntu 18 upgraded, with ClamAv (obviously, there was noting on his log), Phpmyadmin 4.9.1, PHP 7.2 running on fpm mode, ISPConfig and Roundcube, with Apache and MySql. I've changed the users from the first installation, everytime I did another installation. Any ideas?
  9. I have a list of 150,000 financial terms in english. I want to get a file of links to Wikipedia entries for these terms. How can I do this? Paddy Corley.
  10. I have moved my MediaWiki from a Raspberry Pi to an Intel NUC. I want to leave the MediaWiki on the Pi running, just in case I missed something in the move. But I want to turn off editing so that I don't accidentally try to dd new information to an old wiki. I put this into my /var/www/html/LocalSettings.php file (on the Pi) #Restrict editing by absolutely everyone $wgGroupPermissions['*']['edit'] = false; $wgGroupPermissions['user']['edit'] = false; $wgGroupPermissions['sysop']['edit'] = false; Yet, I can still edit. What did I miss? Thanks.
  11. Found some Discussions touching this ideas over several years... but no definitive solution: Authored by Fixuture on Jun 21 2015, 10:44 PM "What links here" for article sections
  12. i am a newbie , i have started installing mediaiwiki with xampp. I got vector based default skin . then i successfully changed my skin to CHAMELEON with is boootstrap friendly. now i need to edit my navigation horizontal bar with adding some more drop down menus but i am unable to identify like from where i need to do changes in my code . i found SCSS and XML files but still confused . Please help
  13. I believe this will no longer be needed as I have found something that'll be just as satisfactory.
  14. You could use ParserFunctions #ifeq to compare the version a page is for with the current version, and display the warning banner and related things if they don't match. More complicated things can be done as well by making use of other functions that can split strings up to compare each component of a version number independently. See https://www.mediawiki.org/wiki/Help:Extension:ParserFunctions for some more details on the ParserFunctions extension. Other extensions exist which add even more capabilities compared to what is listed there.
  15. Hello, I was looking to pay someone to make a sort of global blocking extension so I could use it with my wiki family setup. I know GlobalBlocking already exists on mediawiki.org, however I want an extension that also blocks registered user accounts. I'll be able to pay any reasonable price (up to perhaps $500 USD.) Can go higher depending on the circumstance.
  16. We maintain a MediaWiki space to support an Open Source program. Targeted support MediaWiki subsections are linked from the Help buttons within the program. Every time we rollover to a new software release, the features & interfaces change. We can't retroactively modify the links in the program ... so we rollover to new editions of the user manual pages & freeze the superseded pages. The big problem is that the Categories & Google search results withe superseded pages badly obscure our current content pages. (Worse, we have translated versions of each page in a multitude of languages. That can multiply the clutter.) So I'd like to add a transclusion template that suppresses the indexing (probably using nocat & noindex magic words) but also has a user friendly set of messages. (Friendly as in telling them: the page was intended for a particular superseded version of our software; providing a link to the next releases page; AND, if the that release & the current release don't match, a link to the most current page with an upgrade recommendation. Since changes are incremental, this could allow them to step through release revisions or skip to the most current.) Our site has a template with the current software version. Page title links (OUTSIDE the main manual chapter pages) use templates to transclude the release number into the pagename: [ [Software{ {man version} }-ch1#subsection|feature name] ] I'll have to figure how to use subclusion together with transclusion to build the content of the user messages. I'm mostly looking for help with building a templates with the magic words to suppress indexing, categorization. Thanks in advance -Brian Here an obsolete MediaWiki page with a primitive banner [[https://mediawiki.org/wiki/Project:Support_desk/old|Project:Support desk/old]]
  17. Thanks Skizzerz for the help . the person that built my wiki a few years ago must of done it
  18. Did you install parsoid and ensure it's accessible?
  19. I am getting an issue whenever i am trying to edit the views 'Error loading data from server: apierror-visualeditor-docserver-http-error: (curl error: 7) Couldn't connect to server. Would you like to retry?'" Please help me its urgent
  20. Have you considered converting the data to a table? I had an XLS file with a bit over 100 rows and four columns. Here is a site that does the conversion for me.
  21. The first one will cause issues so I wouldn't recommend it. For options 2 or 3: Make a very heading, such that it wraps around multiple lines on a desktop browser. See which of the options looks better there. Try it on tablet and mobile devices (or use browser dev tools to emulate those device sizes if you don't have any actual devices available), focusing mostly on normal-sized headings. These headings will probably not wrap on tablet, but may wrap on mobile. See which of the options looks better there. As for where to put it: depends. Common.css affects every skin, Vector.css affects only the vector skin. Given that skins can put edit links pretty much wherever they want, there's no guarantee that your change for vector will work properly on other skins.
  22. One more question, please. All three of the following definitions work- which is correct? .mw-editsection { position: absolute; right: 0px; } .mw-editsection { text-align: right; } .mw-editsection { float: right; } And would you put it into Custom.css or Vector.css?
  23. Thanks. I am a complete novice at CSS but the class name should help with my experiments. I did try a few things in my Common.css such as align:right, but the only thing that moved the [edit] links was to increase the spacing.
  24. You can add custom CSS to your wiki to move it back to the right; you may wish to test that your edits look good across a variety of screen sizes from mobile phones up to desktops. The edit section tag is in a class called "mw-editsection", so you can use that for your selector. To add custom CSS to your wiki, edit the page MediaWiki:Common.css while logged into an administrator account, or MediaWiki:Vector.css if you wish for those changes to only apply to the Vector skin. See the manual page on mediawiki.org for more information.
  25. I moved my local MediaWiki form a Raspberry Pi to an Intel NUC, and in the process upgraded to the latest MediaWiki version. I was using the vector skin in both the old and the new location. In the older version, the [edit] links were all on the right side of the page, and now they immediately follow the heading text. Can I move the [edit] links to the right side of the pages? Thanks
  26. Limitations in MediaWiki, for the most part. Injecting javascript into <head> is a chore, injecting javascript at the end of <body> is natively supported. In practice where you put the code makes no difference whatsoever.
  27. It was number 3... I am using multiple browsers, one without any ad related extensions, and I had the impression that the browser I was using for testing was the one without an ad-blocker installed. Just another question in order not to start another topic. Google suggests "To install the global site tag, copy the following code and paste it immediately after the <head> tag on every page of your site". Any reason GTag calls the script near the end of the <body> tag?
  28. Try the following troubleshooting steps: Verify that you have the correct analytics ID in the extension Verify that the analytics code is appearing in the page source. If it does not, you either do not have the extension enabled (check Special:Version), or the extension is configured to not track you (because you are sending DNT with your requests, or you are part of an exempt user group). If the latter case, you can modify the extension config in LocalSettings.php. If the code appears but you still see no data, ensure that your browser isn't blocking the request. Many ad blockers will block Google Analytics and some browsers such as Firefox have built-in privacy settings that may block trackers as well.
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...

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.