[01:21:46] <ElmerG>	 Evening all. I need some help styling Vector. I'm trying to take the p-personal links and make them white. But when I use Chrome's inspect and the things provided, it changes all links, not just the header links. Any ideas? 
[03:11:09] <Woodpecker>	 question on terminology: what do I call {{template|param=argument}} ??? Wikitag? Lua? Template?
[03:12:02] <Woodpecker>	 Also I what is this doing here: {{#property:P18}} -- I cant find any reference to it.
[03:12:18] <Woodpecker>	 its used in this infobox : https://en.wikipedia.org/w/index.php?title=Apas_(biscuit)&action=edit
[04:33:13] <legoktm>	 Woodpecker: I'd call it a template. #property comes from Wikidata
[04:34:01] <legoktm>	 Woodpecker: see https://www.wikidata.org/wiki/Wikidata:How_to_use_data_on_Wikimedia_projects#Parser_function
[04:34:41] <Woodpecker>	 !cookie | legoktm 
[04:34:41] <wm-bot>	 legoktm: To enable cookies for popular browsers, see <http://www.google.com/support/accounts/bin/answer.py?&answer=61416>
[04:34:45] <Woodpecker>	 lol
[04:34:54] <Woodpecker>	 thanks
[04:34:59] <legoktm>	 np :)
[08:13:12] <khalella>	 anyone here using visualeditor and parsoid? 
[08:13:21] <khalella>	 im trying to share a parsoid in a container with multiple mediawiki installations
[08:13:22] <khalella>	 https://www.mediawiki.org/wiki/Manual:$wgVirtualRestConfig 
[08:13:44] <khalella>	 i can reach parsoid from the mediawiki container pretty easily... its configured in the LocalSettings.php
[08:13:57] <khalella>	 a curl test shows the parsoid API responding
[08:14:20] <khalella>	 but when i try to edit a page in mediawiki, it says "Error loading data from server: apierror-visualeditor-docserver-http: HTTP 404. Would you like to retry?"
[08:17:03] <khalella>	 here's my LocalSettings.php config:
[08:17:10] <khalella>	 https://www.irccloud.com/pastebin/1mI7TKP3/
[08:17:49] <khalella>	 here's me hitting it from within the mediawiki container:
[08:17:54] <khalella>	 https://www.irccloud.com/pastebin/LEfeJ1rR/
[08:18:02] <khalella>	 what am i missing here? 
[08:19:18] <khalella>	 maybe parsoid needs to be exposed to the web?
[08:22:06] <khalella>	 of course, because it would hit parsoid from the browser. THANKS!
[08:38:07] <khalella>	 hmmm... i can get the parsoid API from the web too... so i still have no idea why this is returning a 404
[08:40:24] <khalella>	 error from parsoid:
[08:40:29] <khalella>	 https://www.irccloud.com/pastebin/q8PWEeAa/
[08:41:00] <khalella>	 so parsoid needs to loop back and talk to the webserver that mediawiki is running on? 
[08:41:16] <khalella>	 from the container its running in
[08:42:24] <khalella>	 it can do that... but if it his port 80 or 443, it will get a 301 from nginx
[08:43:18] <khalella>	 if i need to configure parsoid to hit the mediawiki container directly, then i have to run a separate parsoid for each mediawiki site
[08:43:22] <khalella>	 because each mediawiki site runs on a different port
[08:43:41] <khalella>	 either way that should never be "invalid domain" or a "404"
[08:49:35] <khalella>	 i wish i had a clue what URL parsoid was trying to pull when it gets the 404
[09:09:48] <khalella>	 oh i see... it loops back to the mediawiki API via the config.yaml. shit
[09:27:39] <khalella>	 so unless i can pass configuration parameters into each request to parsoid, i need to run a separate parsoid service for each mediawiki installation
[11:24:36] <onei>	 Hey, I'm getting a U+FEFF at the end of an api response to action=edit and can't tell why. The edit is successful, but I can't decode the response because of it. I'm using python3.6 with requests
[11:25:00] <onei>	 Has anyone seen anything similar? I couldn't see any obvious task for it in phabricator
[11:25:23] <onei>	 Oh, and the wiki is on mw1.30
[11:36:24] <parvesh>	 Hi This parvesh 
[11:37:13] <parvesh>	 r u there 
[11:47:35] <tgr>	 onei: that's a valid character, are you saying the API returns it but it's not actually in the page text?
[11:47:57] <tgr>	 or are you getting it at the end of the json payload, not inside a string?
[14:39:46] <onei>	 @tgr|away It was at the end of the JSON response, e.g. {"key": "value"}\ufeff. Turned out to be caused by an extension hook that had a BOM in the file somewhere
[19:02:57] <MGC>	 Some people with +2 permissions here who would like to review a conversion to extension registration that has been waiting for months?
[20:11:12] <sokot>	 I can not remove the pages I uploaded in the user blacklist? !!!!
[20:31:27] <sokot>	 alllllooooooooo
[20:34:05] <bawolff>	 Echo echo...
[20:34:09] <bawolff>	 :P
[20:34:42] <bawolff>	 sokot: im not clear which feature you are referring to as the user blacklist?
[20:40:09] <sokot>	  <bawolff>: Special page:All public logs
[20:42:05] <bawolff>	 sokot: the spamblacklist log? Usually thats not a public log but a restricted log
[20:42:40] <bawolff>	 sokot: that said, log entries are deletable if you have the correct rights
[20:42:42] <sokot>	 <bawolff> :i am admin
[20:43:45] <sokot>	 <bawolff>:What type of access is required?
[20:44:37] <bawolff>	 You need deletelogentry rights
[20:45:21] <bawolff>	 And if you have suppressrevision you can extra delete it
[20:45:54] <bawolff>	 if you go to Special:UserGroupRights on your wiki, you can see which groups are allowed to do that
[20:45:59] <sokot>	 <bawolff>Please read the code for this access
[20:46:12] <bawolff>	 !permissions
[20:46:12] <wm-bot>	 For information on customizing user access, see < http://www.mediawiki.org/wiki/Help:User_rights >. For common examples of restricting access using both rights and extensions, see < http://www.mediawiki.org/wiki/Manual:Preventing_access >.
[20:46:30] <bawolff>	 and also 
[20:46:34] <bawolff>	 !revdel
[20:46:34] <wm-bot>	 RevisionDelete can change the visibility of revisions and log entries. See <http://www.mediawiki.org/wiki/RevisionDelete> for more information.
[20:47:37] <sokot>	 <bawolff> tankyou
[20:47:48] <sokot>	 <wm-bot>tankyou
[20:48:31] <bawolff>	 Your welcome :)
[20:48:55] <sokot>	 please
[20:49:38] <sokot>	 Why are I thrown out of the wiki after 10 minutes and I have to re-enter...
[20:49:56] <bawolff>	 Wiki may be misconfigured
[20:50:13] <bawolff>	 e.g. session cache storage is too small
[20:50:57] <sokot>	 what's the solution?
[20:51:05] <bawolff>	 or something else is probably wrong. Generally sessions expiring so quickly should not happen
[20:52:16] <bawolff>	 it depends on what sort of caching is in place. If the wiki is using apcu as its cache, increasing apcu.shm_size can help a lot
[20:52:31] <sokot>	 Probably a problem with plugin settings
[20:53:01] <bawolff>	 if all else fails, setting $wgSessionCacheType = CACHE_DB; can often help
[20:53:17] <bawolff>	 or it could be causes by something totally different
[20:53:24] <bawolff>	 *caused
[20:53:49] <sokot>	 I use my memcached
[20:54:52] <sokot>	 $wgSessionCacheType = CACHE_MEMCACHED; # optional
[20:56:20] <sokot>	 I do not know which plugin was configured incorrectly ??? Do you have a solution
[20:56:42] <bawolff>	 Ok, so check if memcache has sufficient memory
[20:57:23] <sokot>	 How to check؟؟
[20:57:30] <bawolff>	 E.g. the -m option to memcached
[20:58:28] <bawolff>	 try doubling however much memory you give memcached and see if it affects the problem. If problem is unchanged probably caused by something else
[21:00:35] <sokot>	 I am writing to the command line: memcached -m But nothing happens
[21:01:38] <bawolff>	 Thats not really what i meant. I mean adjust the config for it (how to do this depends on your os and what init system you are using and other factors)
[21:02:15] <sokot>	 sorry. ubuntu 18.04