Most of Vector's collapsible sidebar works fine. My issue is that the first-level headers, normally used for navigation, aren't showing up properly. The formatting works as I intended the first time I use it in the sidebar, with the header as a link with no collapsing.
* CoreTechs
** Main Page|CoreTechs
The second time I use it, I use the exact same formatting and instead it shows up as a collapsible header "Developlement", with a single header, "Home".
* Development
** Dev:Home|Home
I imagine this is hard-coded somewhere, or that I fundamentally don't understand what I'm doing. I've tried pouring through the MediaWiki page on the subject to no avail.
http://www.mediawiki.org/wiki/Manual:Interface/Sidebar
Similarly, the Vector extension page wasn't terribly helpful either.
http://www.mediawiki.org/wiki/Extension:Vector
My PHP & CSS skills are zero at the moment, so being pointed in the right direction would be helpful. It seems like it could be a simple enough fix, but it alludes me.
Here is my wiki if that helps:
http://coretechsgame.com/mediawiki-1.19.2/index.php?title=MediaWiki:Sidebar
Any help is appreciated. Thank you.
SeeJay
the first level by default always showing like that, i don't know how to hack mediawiki to change that default, but you can tricky by adding * with empty word
like this
*
* CoreTechs
** Main Page|CoreTechs
* Collectibles
** Collectibles|Main
Here's a guess.
MediaWiki recognises CoreTech as a link due to the CamelCase. It does not recognise Development as a link since it is not in explicit CamelCase.
Maybe if you're explicit about Development being a link it will work, like so:
* Development|Development
** Dev:Home|Home
Since they removed collapsible from Vector I don't have a handy wiki to test that on, but it's a theory for you to try.
Related
I'm new to mediawiki and want to make my own skin for a mediawiki. For example I have a button (div.button-field > input) and I want to give it height: 100%. I know you can put it in a custom.css like
div.button-field > input {height: 100%;}
But if I do it for every element I want to customize the .css gets very long. The other thing, if I want only to customize a specific button which is nested like "div > div.container > form > div > div.button-field > input" and I add a div or remove a div, then it wont work anymore and I have to adjust the "path". So what would be the right way todo it? Or is the .css the best way todo it?
With kind regards
Oli
The answers depend on how much you want to change.
The first easiest path is to find an existing skin, see on MediaWiki.org.
You can configure some elements like the logo, the favicon or the sidebar, and you can change every text message of the interface.
Then, you can customise, as a logged-in administrator, the CSS rules by modifying the page MediaWiki:Common.css (example on English Wikipedia), or possibly MediaWiki:YourSkinName.css for skin-specific rules (for example MediaWiki:Vector.css to modify only the skin Vector; example on English Wikipedia).
You can also modify add JavaScript features by modifying MediaWiki:Common.js (example on English Wikipedia), or MediaWiki:YourSkinName.js for skin-specific rules (for example MediaWiki:Vector.js to modify only the skin Vector; the page does not exist on the English Wikipedia).
This kind of modification is recommended because it will be kept during MediaWiki updates, although minor adaptations could be needed on the long term.
If you want heavier changes, you can copy an existing skin, rename it, and change the PHP code, for instance by moving or deleting entire blocks. Prefer copying a well-supported skin like Vector or Monobook to be sure it is compatible with most MediaWiki extensions.
But it will take some or lot of work during MediaWiki updates (depends on the quantity of changes), and if you cannot do this work the risk is either you custom skin breaks or you will stay with an old MediaWiki version (which is not recommended for security reasons).
Also, if you choose this path, be warn not to break the structure expected by the VisualEditor if you want it continues to work.
There is a tutorial on MediaWiki.org to adapt the skinning from easiest ways to heaviest, see Manual:Skinning Part 1 and next pages.
This is an odd one, and I'm REALLY hoping someone else has seen this before.
We want a list in our product short descriptions.
As long as we don't add any class names to the description, everything is fine.
But, as soon as I try to give any part of it a class name, the whole thing starts breaking.
Specifically, it renders a broken second copy of the short-desc directly following the opening BODY tag for the page/document.
In that broken instance, it truncates the short-desc before the first CLASS declaration and guts the closing UL tag.
It does also still display where/how it's supposed to ...in the product summary.
See an example here: < link removed >
BTW, I'm currently on the Avada theme, but I tested with the Twenty-Seventeen theme as well and the problem persisted.
Also, I tested with paragraph and span tags as well and that yielded the same broken results.
Has anyone seen anything like this before?
Any suggestions/ideas?
Found it!
I went through all the plugins, and turns out there is one responsible:
TG Facebook Meta Tags
All plugins other than that one have now been reactivated, and the problem is resolved.
Not sure how to really categorize this question, but on this page, the file http://d1el287zd12c0j.cloudfront.net/assets/hitgrid-0a8239a14fba0de87431c06cd75774f3.css seems to be completely ignored by browsers. It appears to load successfully and no different than any other css file on the page, but the styles in it are simply not applied to the page.
The content-type, encoding and everything appears to be working as expected. Roughly the same content "applies" fine on my local installation of the app.
I'm at a loss as to what's going on here.
I just check it out and everything went right.
Try to make the filename shorter in the CDN. Large names tend to make error in some way or maybe check if no other stylesheet is interfering with the styles
If that didn't work, answer these questions and Ill try to git it a try again
Which OS are you using?
2. Are you using wordpress?
Can anyone recommend a module or other Drupal add-on that can be used to format code nicely like I see on a lot of blogs and websites? Ideally something that would integrate with CKeditor, but that's not critical, I can make do with HTML tags if need be. Thanks.
The two most popular Drupal modules seem to be Code Filter and GeSHi Filter for syntax highlighting. For getting GeSHi to work with CKeditor, check out the WYSIWYG - GeSHi bridge module.
Well, there's http://alexgorbatchev.com/SyntaxHighlighter/ which is javascript. It gets applied at view time.
To see your code highlighted in the actual editor, you're probably going to have to work a bit harder. If it were me, I'd start with http://ace.ajax.org/ , which is an editor that grew out of Mozilla's constantly-renamed in-browser IDE project.
Maybe it's to much but check this
http://drupal.org/project/grammar_parser_ui
Quick follow up: as per this post, the WYSIWYG-GeSHi bridge development has been put on hold because of some problems integrating GeSHi buttons into CKeditor's toolbar (they make all the other buttons disappear). I can confirm that this is the case.
However, if I use GeSHi tags in HTML source, they do format things correctly. The really key thing left out of the GeSHi module documentation is that you need to enable it as an input format in Drupal.
Next I'm going to try this method for integrating GeSHi formatting directly into CKeditor without using the WISYWIG module or any bridges. Thanks again for everyone's help.
There's the Prettify module that implements Google Code Prettify as JS library. It works out of the box but it appears to duplicate the pre tags, that is, one pre tag appears as container for the other one:
<pre class="prettyprint prettyprinted">
<pre class="prettyprint">
<code>
.myClass {
<br>
float: left;
<br>
}
</code>
</pre>
</pre>
That's only annoying because you can't really style the pre tag if there's two of them because all your styles are duplicated leading to double margins, padding, borders. etc.
Still, it works out of the box if you can deal with using the default styles provided with the module, and there are a number of them, i.e. Google Code, Stackoverflow etc.enter link description here
I'm looking for some tips to clean the code which is generated by WordPress and some plug-ins, because I'm not happy with the code generated by WordPress for two reasons:
The code isn't well formatted. I know, I know... It isn't important since that the browsers don't need to "parse" a well formatted code. However, I like to keep all codes well formatted and it includes HTML code generated by me or third-part systems.
Unfortunately, some parts of the code that WordPress puts on the <head> aren't well formatted and in some cases those parts aren't really necessary. By the way, I have no idea about how to clean-up it or how to hook the function which prints that code.
Is there some way to add tabs / spaces to the code generated by WordPress without change the core files / code?
Thank you!
Overlooking the overall ambiguity of your question, the file you need to edit to fix the <head> element is header.php. You will find it in your theme's folder in wp-contents.