Project:Current issues

Jump to: navigation, search

About this board

This page is for discussing issues related to MediaWiki.org site. To get help with MediaWiki software, ask on Project:Support desk.
Archives 

Current issues archive overview

By clicking "Add topic", you agree to our Terms of Use and agree to irrevocably release your text under the CC BY-SA 3.0 License and GFDL
Nanoukaplus (talkcontribs)

Hello,

I've got a query #ask using the format template, with a template and an introtemplate. I want to display the results in a table.

{{#ask:[[Category:Objects]]
|?=name
|?date
|?user
|format=template
|namedargs=no
|introtemplate=Header search object
|template=Search Object
|outrotemplate=Table footer
}}

In my outrotemplate I only have the caracters |} In my template I display the informations of my query. In my introtemplate Header search object I want to display the columns only with certain conditions, so I have this code :

{|class = "wikitable"
{{#if:{{{1}}}|!Object's name}}
{{#if:{{{2}}}|!Date}}
...

But it didn't recognize the parameters into the balise {{{1}}},{{{2}}}.. Does anyone have a solution please ?

Reply to "Ask and introtemplate"
Yolo33s (talkcontribs)

After installing PdfExport Extension (v3.2.0) for mediawiki 1.27.0, I have the following error message :

Fatal error: Call to undefined method Article::preSaveTransform() in /var/www/wiki/extensions/PdfExport/converters/HtmlDocPdfConverter.php on line 151

This comment was hidden by Seb35 (history)
This comment was hidden by Seb35 (history)
Seb35 (talkcontribs)

@Yolo33s: This extension is hardly maintained since some time. In fact the line you pointed probably didn’t work since MediaWiki 1.18. I just solved a number of issues I experimented when launching this extension with MediaWiki 1.28alpha, PHP 7.0 and Dompdf 0.7 (installed with Composer), whose this issue. Finally it worked with Dompdf – I didn’t tested other backends. When the change I04eda179bab689e29b9f26caf10807f4136afa3f will be merged, it should work, but you will have to install the very last version (it will be available on ).

62.102.229.98 (talkcontribs)

@Seb35: Thanks for support. I first tried to install dompdf 0.7 with composer but as I don't master it I was not sure about what I was doing. The unzipped dompdf folder is in /usr/bin/dompdf. In LocalSettings.php, I added "require_once '/usr/bin/dompdf/autoload.inc.php';" but when I try to print a page, I get an error message saying that no pdf converter software has been found.

Is it good to place the require_once in LocalSettings.php ? I also tried in index.php. More precisions on how to install dompdf would be much appreciated.

Thanks.

Seb35 (talkcontribs)

I tested the following commands (probably you did some of these):

  1. Download Dompdf 0.7 from GitHub
  2. Unzip it in the MediaWiki directory, next to LocalSettings.php, the subdirectory is named "dompdf"
  3. Add require_once __DIR__ . '/dompdf/autoload.inc.php'; in your LocalSettings.php
  4. Download the patched version of PdfExport from my website (when the change above will be merged, it will be available in the "official" version on )
  5. Unzip it as usual in extensions/ (if you had a previous extensions/PdfExport move it to another location or delete it)
  6. It should work

I guess you are under Linux, right? If so, the path /usr/bin is reserved for general commands, but not for librairies (as is Dompdf); I said above to put it in the MediaWiki directory, it is probably a good place; else web applications sometimes have a subdirectory "lib" where are the external librairies (MW doesn’t have this subdirectory, external librairies are in the subdirectory "vendor" managed by Composer -- prepared by the release manager in the case of the tarball).

62.102.229.98 (talkcontribs)

Thank you for the tips @Seb35. I did everything listed above. Now it is installed but when I print an article I get an error message Exception encountered, of type "Dompdf\Exception" without more informations. This is a blank page. I checked that all requirements are OK (Dom extension, GD extension, MBString, php-font-lib, php-svg-lib) and they are, then I restarted apache...

Do you have any idea about this error message. I read some posts about Dompdf Exception but generally the error message is more precise than just "Dompdf\Exception".

For information, I'm on Ubuntu 16.04 with PHP 5.6 and I run a 1.27.0 version of MW.

Regards

Seb35 (talkcontribs)

Great! At least the MW part seems to work. I didn’t have this exception myself – different config: Debian+PHP7, but yours seems to be quite good also. Can you add ini_set( 'display_errors', 1 ); on the top of your LocalSettings.php? It could display a more detailled information about the exception (you will have to remove it in production).

Yolo33s (talkcontribs)

Yes I also thought to display errors but unfortunately it is not more verbose...Only a strict standard warning unrelated to PdfExport or Dompdf. I wonder if an installation with composer would be safer but I do not feel comfortable with that.

Seb35 (talkcontribs)

If you feel comfortable with command line (quick guide: directories are separated by a slash "/", the main commands are "cd the-directory-you-want-go-to" and "ls" to display the content of the directory), you can install Composer inside the main MediaWiki directory (instructions), then add Dompdf as dependency by creating the file composer.local.json in MediaWiki directory (next to LocalSettings.php) with the content:

{
   "require": {
      "dompdf/dompdf": "*"
   }
}

and executing (in command line in MediaWiki directory) "composer update --no-dev". If you install it with Composer, remove the require_once from LocalSettings.php (else it could be installed two times). There is a guide for Composer on Composer/For extensions. Thanks for your perseverance!

62.102.229.98 (talkcontribs)

And thank you very much for your help @Seb35, I really need to make this extension work. When running "composer update --no-dev" it seems that this is mbstring and gd extension the problem. It is missing. What I don't understand is that I'm using php 5.6 and it requires mbstring and gd extension for php7...Strange. Anyway, it is installed but I still have the same exact error message. Note that in my mediawiki installation folder, the .json file is named composer.json and not composer.local.json. But if dompdf had not been installed, I would have had another error message.

Ma persévérance atteint ses limites.

Seb35 (talkcontribs)

Don’t you have some sysadmin or a geeky person near you? It becomes difficult to follow remotely. For Composer I guess there are dependency issues, probably because some dependencies require PHP7, so probably a bad idea to try in this direction, stay with your downloaded version 0.7 of dompdf. And it is absolutely required for PdfExport, so you (or anybody who could help you) have to make Dompdf work to make PdfExport work. Perhaps add also ini_set('error_reporting', E_ALL); in your LocalSettings.php.

If it cannot work, I tried to install Extension:Collection but, as I was afraid of, it is horribly difficult to install. And an external solution but functionning without any burden for the MW admin is to use the link 'Printable version' in the sidebar section Tools, then use the Print feature of the browser and select 'Print in file'. Depending on the browser, it will save in a Postscript file and/or PDF file. With this way to export PDF, the result can be different from a brower to another (e.g. I was surprised of a document where the font size was about the double between Firefox and Chrome -- it was quite small with Chrome and quite big with Firefox).

62.102.229.98 (talkcontribs)

Yes I already tried collection, and I already add ini_set('error_reporting', E_ALL); in LocalSettings.php. I think dompdf is installed because wether I install it through composer or simple folder, I had the same error message at the end. I will wait for the return of a sysadmin to debug this issue. Anyway thanks a lot for support.

62.102.229.98 (talkcontribs)

@Seb35 I did it ! I found on the general support someone with a completely different problem who needed to run the "jobs". After a php maintenance/runJobs.php, I could print articles to pdf.

I'm still convinced that the mediawiki documentation needs drastic improvements.

Seb35 (talkcontribs)

Ok, I didn’t know it could have an influence, but it’s great! Happy the problem was solved! (and aggree about documentation, it’s a lot of work, you’re welcome if you want to add something, but this thread will probably help other people also :)

Reply to "PdfExport does not work on 1.27.0"
PrimeHunter (talkcontribs)

Is there a way to make an edit request for a protected page at mediawiki.org? I tried to use Template:Edit Protected on Template talk:Clear but it seems Category:Protected edit requests isn't added on Flow pages, and many of the pages in the category have old unanswered edit requests anyway.

Ciencia Al Poder (talkcontribs)

On flow messages categories don't work, but try to add it to the board description (that's at the right side), I think categories work there

Jdforrester (WMF) (talkcontribs)

Please do not edit the description of a Flow board to add a category; they aren't meant to be edited frequently. Post here if you have an unusual edit request (most pages that need editing are not protected; most likely if you need to edit it we need to unprotect it).

Reply to "Making an edit request"
Shayegan1980 (talkcontribs)

Hello there

I want to start a website same as Wikipedia for Iranian with many subjects. Can I use Mediawiki for it?

I attached my site address .

thank you for your guide

Ciencia Al Poder (talkcontribs)

See Manual:Installation guide

Wargo (talkcontribs)

Yes, you can.

Reply to "start new project for Iranian"

I want to use the "get extensions",but it shows the"Unable to fetch extension list!"

2
Wujiang2016 (talkcontribs)

The webshows"Unable to fetch extension list!" Where am I supposed to go?

Ciencia Al Poder (talkcontribs)

Can you try again? It works for me atm

Reply to "I want to use the "get extensions",but it shows the"Unable to fetch extension list!""

Using watchlist notice for Code of Conduct calls for feedback

7
Qgil-WMF (talkcontribs)

At Talk:Code_of_Conduct/Draft#Wider_participation.2C_still there is a discussion about how to announce calls for feedback about the proposed Code of Conduct for technical spaces to mediawiki.org contributors. The idea of a watchlist notice has been suggested. As far as I am aware, we haven't used this feature in mw.o before. I guess this is a good place to ask for feedback about using this feature for this purpose.

Technically, this seems to be done by editing MediaWiki:Watchlist-details. Questions:

  • Is this use of watchlist notice OK or not?
  • Should we do it by editing MediaWiki:Watchlist-details or is there another way?
  • Should we use plain text with links or i.e. a Template:Notice?
  • How often and how long should these notices be kept, i.e. One week every time that there is a major call for feedback or more often?
Jdforrester (WMF) (talkcontribs)

Personally, I really dislike the abuse of that part of the interface for important messages, but I understand that some wikis think it's OK. We've never done it here, and I'd be sad to see it start.

More objectively, however, I also think it would be a waste of time for this wiki; very few people are active on MediaWiki.org in the way that editors of other wikis are, because a lot of the "action" occurs off-wiki, in tasks (Phabricator), in code (gerrit/GitHub/etc.), or for third party users of MediaWiki in particular, on their local systems, and so the use of the watchlist as the key place people see is not likely to work. The people who use their watchlists on this wiki (like me) are mostly wiki gnomes rather than the key people to involve. A logged-in-only sitenotice would probably have a much better effect at reaching the useful people for this work.

Mattflaschen-WMF (talkcontribs)

I have no objection to using a watchlist notice, though I agree with James a lot of contributors don't use the wiki that often, and probably use the watchlist even less. I also think the site notice is a good idea, but we probably want to limit it to text approvals (rather than "please help discuss this"). We don't want to be too intrusive, and the site notice appears on every page.

Ciencia Al Poder (talkcontribs)

I personally find CentralNotice banners way more obtrusive than a one-line text on the sitenotice. CentralNotice banners appear for me several days on a week, with images, even if I dismiss them, while the sitenotice can be dismissed once and forever (until someone updates the sitenotice ID)

Qgil-WMF (talkcontribs)

I propose to try something, be ready to pull back if there are justified complaints, and then fine tune next actions based on feedback.

A logged-in-only sitenotice looks like a good candidate for a first try, indeed. How is that requested and implemented? I propose to figure out these details and prepare a sitenotice for the approval of the Cases page, expected to start in a couple of weeks, after the call for feedback started yesterday by Matt has settled and remaining issues have been identified.

Mattflaschen-WMF (talkcontribs)

It may be just one week before starting the approval discussion, depending on how much feedback on Cases there is.

Mattflaschen-WMF (talkcontribs)

I agree a simple dismissable text sentence is fine. No need for an image.

The documentation is at Manual:Interface/Sitenotice , but I'm not entirely clear from that how it interacts with CentralNotice. Someone from Fundraising Tech probably knows.

@AGreen (WMF), how would we configure it if we want a dismissable text notice here and on wikitech.wikimedia.org?

Reply to "Using watchlist notice for Code of Conduct calls for feedback"
George.boeck (talkcontribs)

Friends:

I would like to mention that, needing a couple of popular images of eucalyptus trees from Wikicommonst, I was totally encumbered by exact specification of species. Wishing to comment about this, I was again encumbered by tremendous exactitude. Lord knows where I should have made this comment. It's wonderful that we can have species specific images, but a handful of useful for popular needs would not hinder the project, eh?

Ta',

Geope

Jdforrester (talkcontribs)

Hey there,

I don't think this relates to this website but to Commons. You should probably ask on their Village Pump instead.

Reply to "Access"

Special:MyLanguage/ links don't work

2
Summary by FeelUs

thank you

FeelUs (talkcontribs)

When I click on link, I always go to english version.

May be I not comletely configure my account? Help me please

Seb35 (talkcontribs)

You have to configure your prefered language in your preferences.

git.wikimedia.org down

1
Summary by Nemo bis
Christian75 (talkcontribs)

Is git.wikimedia.org down? I tried to look in the irc logs for mediawiki/mediawiki tech and search here, but could not find anything about it...?

Summary by Jdforrester (WMF)

User was blocked.

Kghbln (talkcontribs)

User:QNguyen. It is starting to become painful to cleanup behind him or her.

Another question. Is there an Admin board here on this wiki? Though I here for seven years now I never really needed to contact admins.

Koavf (talkcontribs)

You can post to Project talk:Administrators

Kghbln (talkcontribs)

That's what I was looking for. I guess it is amazing that I never needed this in all these years. Great wiki to work on and cool work what is probably done in the background by all the admins here without me noticing it.

Koavf (talkcontribs)

There is definitely some spam and trolling here but much less noise than signal since this is such an underground wiki. There is little moderation here and generally not much needed.

Kghbln (talkcontribs)

You're right! Never seen this as an underground wiki but rather as an special interest wiki. :) Yeah I know what you mean. :)