email info@... returned 550 No such recipient here.
Jump to navigation Jump to search
Reply to "Hi your email on Professional_development_and_consulting is broken"
Reply to "Starting conversion of LiquidThreads to Flow at mediawiki.org"
Reply to "The future of skins"
Reply to "Erm"
Reply to "RTL help with BootStrapSkin"
Reply to "Extension:BootStrapSkinContactForm"
Hi your email on Professional_development_and_consulting is broken
Starting conversion of LiquidThreads to Flow at mediawiki.org
Hello. I'm sending this to you, because you've been one of the top 50 users of LQT on mediawiki.org over the last 360 days, and I wanted to make sure that you'd seen the announcement at Starting conversion of LiquidThreads to Flow at mediawiki.org. There are links in the topic-summary at the top, for other discussions (wikitech-l and Project:Current_issues), and a link to the planned process and timeline (scheduled to begin April 6, with smaller conversions at first). Please do test Flow out at Talk:Sandbox if you haven't tried it recently, and give any feedback/suggestions/requests at that main discussion location. Much thanks.
The future of skins
An rfc on the future of skins is open here:
I am notifying you as you're maintaining (at least) this skin:
Please consider participating. Thanks. :-)
Hey, nice integration, however I noticed that MW (1.23.2, anyway) seems to strip out the <i> tags in articles, and renders HTML as plaintext in the sidebar; any tips or prerequisites you are aware of which might get this working? :)
can you include a screenshot and which extension are you refferring to?
There's not really anything to show in a screenshot; I'm talking about FontAwesome. Simply, <i class="fa fa-whatever"></i> gets stripped by the parser in MW 1.23.2 articles, and MediaWiki:Sidebar renders the htmlchars, rather than parsing the markup. Your extension page suggests this should work in Vector, with just the one modification to Vector.php.
Hi, thanks for the heads up, will have to run some tests on the latest version of Mediawiki. Strange that this is the case as I use the same folder layout and structure for BootStrapSkin and there are no problems with it there.
Have you tried looking for faults in the console it maybe that the css isn't located correctly or maybe (and I hope this isn't the case) the files have changed in some way (another developer in my team maintains this and the other css extensions) so that the css isn't pointing at the font files correctly.
I've download the latest version and my suspicions are correct, someone will be getting a bollociking tommorrow lol
Open to edit, FontAwesome.php and change line 17 from;
'styles' => array('font-awesome/css/font-awesome.min.css'),
'styles' => array('font-awesome/css/font-awesome.css'),
The minified css file is pointing towards a non-existant file, whereas the unminified css is correct, make the change, refresh the cache and it will work ok.
Will update the corrected file tommorrow.
Again thanks for the heads up, cheers :)
Hmm, thanks for the fix; I notice another strange problem. icons are rendered fine on some pages, but not others.. I can't figure out what is the deciding factor as it seems inconsistent even within a single same namespace :/
At the time of writing:
Whaaat, that's bizarre. They work on special pages and the occasional other article. Looking at the source it seems that something is arbitrarily stripping the tags from the output. Perhaps the markup enabling hack is responsible.
I'll consider the bootstrap skin if all else fails aha :)
Can I consider your issues solved?
Hah not as such, but thanks for your help in any case.
Okay, so I reverted the hack I had applied to Vector.php in favour of CSS :nth-child() selectors for our community favicons; I'd still like to use the font-awesome package if possible, but this happens by following the instructions as set out on the extension page.
It would seem that mediawiki will not parse HTML in the navbar, so how could a simple import of the style sheet allow for proper rendering? I'm afraid it simply isn't possible without further hacking to the skin.
Ok cheers for letting me know, will add a note on the download page, it was our first extension, so I might delete it from the extension directory, appols for the inconvenience. I did join your site to take a look but I assume you deleted the code from the sidebar.
Very interesting wiki btw, I've experienced a couple of events as you describe on your pages, though mine where through meditation, two actually, one was very profound and was induced simply by reading a passage from a book by Nisargadatta Maharaj. The other occured while in a very deep state of meditation, and was induced simply by focusing consciousness on itself.
Both experiences where beyond words, but bliss comes the closest. I "practice" (for the want of a better word) Advaita Vedanta.
RTL help with BootStrapSkin
Hi Lee. I took a look at your skin, but I don't know that I understand what the problem is. It works fine in Hebrew and RTL. There's one issue I did find immediately - the header is flipped; in RTL, the logo should be on the right and the menu on the left, so you need to flip the pull-right and pull-left classes when in RTL mode. You can do that in the PHP end by checking the page direction settings in MW itself.
You mentioned you have a problem with the editor - do you mean the wikitext editor? (I didn't see problems with that) or VisualEditor? If you mean VisualEditor, we don't yet support external skins, especially ones as complex as this one just yet.
many, many thanks for taking the time to look at this for me, really appreciate it.
I've created a flipped bootstrap rtl css which solves the logo/menu issue, but I'm going to investigate your suggestion "page direction settings" because the css fix feels "dirty"!
Regarding the wikieditor; When writing in Hebrew using the editor does the user write rtl, its just that when I open the editor and write, the words still appear ltr, appologies for my ignorance - or will editing the page direction settings solve this?
Best wishes, Lee
Heiya Lee, I have put some suggestions on the talk page of your extension which will probably help you a lot with improving it and point you to a direction. Addidtionally Skizzers added a note about a security issue which you already anticipated. I really should learn basic PHP to be of better help in such cases in the future.
If you have no knowledge of php and want to learn, I'd suggest learning mediawiki mark-up, it is confusing making the transition, as I have found myself, but making the transition to Mediawiki has been less steep than I'd expected.
I started with the Font-Awesome extension, which is pretty basic and looking at it now, I'm almost embarressed to have my name to it lol It works I know but requires too many edits to the vector skin, when I'm were I want to be my skin and its accompanying extension I'll look at those css extensions again so that no core edits are required.
Maybe download that extension and look at how it works, or modify it for something you want to make yourself, just as a learning process.
awesome thanks, though strangely I cant use the same tool to email you lol
You should be able. Just change the username.
Ah your username is different to your signature.
I believe that this is a good strategy. I already started to do some learing by doing but a seemingly easy task turned out to be a disaster. Still, I am learing though this was the wrong spot to start. I think MediaWiki-Vagrant will be an option. Thank you for your encouragement.
You should try modifying fontawesome because it is VERY basic as it is just a css extension, see fontawesome.php which shows how to include the css and scripts which are loaded through resourceloader, also naming the ext.files found in the modules folder. Also look at fontawesome.i18n.php which shows how to add messages i.e. developer name, links and extension title.
Start there, and see what results you get, also you will find the following very helpful;
You will enjoy, but please do contact me if you need any help :)
I18n is the part I currently understand most of. Still heaps of gaps even there. I have a couple of unmaintained extensions in mind which I would like to foster in the future. Thank you for the pointers to crank up things!
even though I'm not an expert with php you're welcome to my css knowledge whenever you like :) Never be affraid to ask ever :)
Wow, thats quite impressive, have your email address now - Be afraid, be very afraid! lol just joking would invade your privacy like that, but it would have been useful for the other issue.
Also hope you don't mind me saying, if you are German as your github page suggests, your use of English is impeccable, would never have guessed in a million years, there hasn't been a single error in grammar, congrats for your brilliant skill :)
Yeah, I am. Writing is ok but as soon as I start talking it gets undeniable. Thank you for the cheers!
There are no older topics