Skin talk:BootStrapSkin/Flow

Previous page history was archived for backup purposes at Skin talk:BootStrapSkin/LQT Archive 1 on 2015-06-25.

Hello everyone,

I just installed  Bootstrapskin on a Mediawiki with the following verions :

Product	Version
MediaWiki	1.26.3
PHP	5.6.22 (apache2handler)

But I get this exception : Uncaught exception 'Exception' with message '/var/www/html/skins/bootstrap/skin.json does not exist!' in /var/www/html/includes/registration/ExtensionRegistry.php:106

I will be very thankfull if someone help me.

Thank you !

Hi, can you open this topic at the forums.

Lee Miller 15:53, 8 July 2016 (UTC)

This has been solved now, both of our popular skins (bootstrapskin and foundation) can install with composer and have a skin.json file.

How can I get this skin.json file as I can't contact Lee Miller anymore and the foundation skin is no longer working on my wiki. Where also can I find info about this composer?

Or be able to download the latest version from somewhere?

This might be a long shot, but evidently the last version of the skin I had downloaded after purchasing it was bootstrapskin_1.0.43.b. Would anyone potentially be able to share 2.0, the last version?

The only reason I ask is I'm in the process of upgrading a wiki to the latest version and unfortunately the version I have isn't set up with a skin.json and so breaks with the new loading process.

Website is no longer accessible.

Is there a reason behind their closure?

I am asking because there was no notification.

I am using their skins almost for an year

Also keen to find out what's happened with this...we have also been using this skin for over a year...is it supported elsewhere, do we need to change to a new skin? Suggestions for best / closest alternatives?

I have looked very long for contact with Lee Miller. It seems like he has cleared his tracks everywhere. He had developed very beautiful skins and perhaps the most. Other skins of him such as: Halcyon, Nexus, Hadron can not be used anymore.

For now I use Tweeki.

Hello there folks ... I'm searching from days how to add a back to top button. I'm using Bootstrapskin - tryed everything from web, but when i change the code in bootstrapskin.php it gets me a white page. I prefer to add a floating button in bottom right or left of the page. I will be very thankfull if someone help me.

Hi Dottysbb,

Why waste time searching for days? Could have solved this very quickly at the forums, that's why we have forum to support our products :) You are very welcome to join and ask anything.

link is broken. some help would be nice :)

See here for the answer, the forums are always the best route to ask questions as we don't monitor the Mediawiki pages.

Hello,

Thank you for your great work!

I had an error with GoogleSearch extension enabled. Debugging this, I found out that $content is a string, not array, causing some warning.

Anyway, on my local, it doesn't look as good as the version on your website. Is there something I missed ?

Test bootstrap on local

Hi Phuyem,

thanks for your kind words :)

You need to add the bootstrap styling to articles - visit the site again and choose one of the guides, I'd suggest starting with columns first and then adding the content.

Would appreciate it if you could join the forums, it is only coincidence that I visited this page today and I'd hate for your support requests to go unanswered. Using the forums guarantees a response and others will respond if I'm not about, and you're likely to get much more detailed answers there.

A quick tip - visit the site and then view the page source, copy and paste that into your page, will give you some clues on how to incorporate bootstrap styling.

Thanks again, Lee :)

I finally had some time to play around with the skin a bit and tweak it according to my preferences. It's great fun but there's two things I noticed along the way:

• Checkboxes seem to disappear with this skin, perhaps because of some js conflict.
• Using Extension:Semantic Forms and Extension:HeaderTabs, I was not able to add new items inside the form (see this page for the functionality I'm referring to). Again I suspect a js conflict.

One of the errors reported by Firebug is TypeError: this.element.propAttr is not a function jquery.ui.button.js:59, which may or may not be relevant. I'll see what I can find to make this report more useful to you.

I've mailed a response Cavila, many thanks :)

Regarding the check boxes, I found the error, can't think why I did it, but I've included a display:none next to the radio and check box element, must have been while I was testing something or another, the quick fix is editing bootstrap-blue.css line 8119 and comment out display:none.

I have updated the extension so that this is solved, see version 0.0.41 for more info.

Have also added a section on conflicting extensions e.g. HeaderTabs.

Thanks again Cavila, you're a star :)

Just need to address SMW, will need some time to look at this, but I'd really like to get it sorted, so would appreciate a link to your site so that I can take a closer look. If its ok and you don't mind sharing you can email the link here.

OK, thanks for your e-mail and for the fix for #1!

As for #2. It's not SMW, but a form extension called Semantic Forms (SF), which is often used to facilitate data entry in SMW. The issue persists if I remove HeaderTabs tags (so we can rule out interference from HeaderTabs) and was probably there in the original Strapping skin. I'm experimenting with the skin on a private site, but you can try out a form with the "add item" feature at http://discoursedb.org/wiki/Form:Item (use a random title and have a go at "Opinions for this item"). Hope that helps.

Thank you for your effort in creating this nice skin! Will give it a try soon! Cheers

Awesome, nothing beats a great peer review, really appreciate your kind words :)

I really like the design. A lot of website have become indistinguishable because of BootStrap, but this on adds a reputable and clear note to it.

Wrote a lot of code for the skin, default bootstrap.css is around 6k, mine has over 33k, though the vast majority is for the extra colour classes, but also adds effects and quality, e.g. border shading etc. Plus I've removed some of the default bootstrap js and replaced with (what I consider to be) better code. I have nine other css files ready for future releases, all are pretty much the same but each uses a different base colour, the current version ships with bootstrap-blue.css which is what can be seen at the demo site.

Gonna get on with changing the code now :)

Wow, about 5 times as much CSS. You surely did a big job here. Doesn't this degrade performance a bit. Hmm ..., we are probably talking about miliseconds and the CSS will probably not be stacked or so. I guess it also depends on which classes on is using on the acutal wiki page.

The page partially renders pretty quickly at around 1.25 seconds and The bootstrap-blue file loads in 138 ms.

The biggest resource hogger (as you probably suspected) is the Javascripts, theres a lot of stuff in there, which is what allows for the effects and extra functionality, takes around 4-5 seconds to completely load! Though of course this all goes on in the background, a normal visitor wouldn't notice I don't think becuase the page is viewable at the 1.25 second mark.

Of course after the first visit cache helps.

Indeed, interesting. I have to see it in action. No way around it. Perhaps I can provided numbers from my machine - just for comparison.

That would be very helpful :)

Thank you, Lee Miller, for such a wonderful job! It might come as a culture shock to many MW users who've grown accustomed to ugly layouts, so please bear with us while we're recovering. I will try this out soon (it doesn't work for me yet because the collapsed menus are not expanding, but it might just as well be me).

Hi Cavila,

many thank really appreciate your kind words, they mean a lot :)

Which version are you using, I tested 0.0.40 on a couple of browsers and on xampp and there weren't any issues.

0.0.39 does not work (and suffers from the non expanding menu issue), when I updated from 38 - 39 there was a Javascript conflict (lightbox, magnific-popup and Gritter), which I've now removed at the expense of the Gritter notification and form functionality, all of which were to be included in the July update.

A quick fix to solve the drop down issue is to remove (or comment out i.e. # lines 48 and 50 from bootstrapskin.php;

'bootstrap/bootstrap/js/holder.js',
'bootstrap/bootstrap/js/magnific/jquery.magnific-popup.min.js',
'bootstrap/bootstrap/js/lightbox/lightbox.js',

Please let me know if this solves it for you, it worked for me :)

Many thanks again, Lee :)

Is a bit of nightmare, I don't usually suffer from js conflicts, perhaps more knowledge of Mediawiki would be beneficial, would happily appreciate any support from any developers with this type of experience?

All done, have updated version 0.0.40 shouldn't be any problems now (touch wood!) :)

If you have the time would really appreicate any feedback and reporting of problems.

I think it will be nice to have a more distinct name to activate this skin than "strapping" like e.g. "bootstrapskin". There is at least on other skin around which is activated with the same name. Thus you cannot install and test them at the same time. I think such collisions should be avoided if possible even if there is indeed only a minor chance that this will happen.

Edit: another thing will be to also have consistent naming in the backend like, e.g.

require_once( "$IP/skins/bootstrapskin/bootstrapskin.php" );

since I think this will make administration easier in the long run.

Hi Kgh, will look at changing this for the next update, which is due pretty soon, appreicate your input, thanks, Lee

Great, another reason for changing is that this skin now ended up in the Strapping statistics. So it cannot be discovered.

All done, uploaded the newer version and changed the install info :)

That's really amazing. I imagine that it is fun for you to develop this skin. Do not forget to add it to the gallery of user styles to get more attention for it!

If it does not really matter the skin could go into the "bootstrapskin" directory or does it have to be "bootstrap"?

Many thanks as always your advice is always appreciated, will get round to sending you a beer at some stage :)