I am in the throes of upgrading a 1.17.0 MediaWiki instance to 1.29.3 (latest version supported by my MySQL/PHP combo). So, software is basically running, database is updated, I can navigate around. I installed the MonoBook skin (this is a new step as of 1.24.0 it seems). I only have the body section, not the toolbars at the top, left, bottom. The Special:Version page gives the info as:
MonoBook – (cce8e7b) 20:07, 14 October 2018 GPL-2.0-or-later The classic MediaWiki skin since 2004, named after the black-and-white photo of a book in the page background Gabriel Wicke, Isarra Yos and others
I followed all the directions I could find, no luck. Any tips about which variables to look at, directories to check will be appreciated.
Not a complete answer yet ...
I opened a page in "view source" mode and clicked on the load.php href. The useful message was:
1.29.3/includes/resourceloader/ResourceLoader.php: MediaWiki requires the less.php parser
I have a request into my IT people to add less.php (composer require less.php/less.php) as I don't have the right privileges. I'll update after I see if that takes care of it.
Related
I want to use my flowchart as a table of contents that also represents the progression of parallel events vaguely in chronological order and their relation to one another.
I know to create these charts using markdown. By adding the "click" line for the "B" node i can see my cursor change when hovering over the node as if it were a link but any attempt to select it doesn't work.
graph LR;
A-->B;
click B "http://www.github.com"
Is this a limitation of Gitlab itself?
Update:
This is now supported since GitLab 12.1.
The given example works in GitLab Wiki pages.
graph LR;
A-->B;
click B "http://www.github.com"
Thanks, KargWare for pointing this out in the comments.
Yes, this is a limitation of GitLab. There is an open issue requesting the feature:
https://gitlab.com/gitlab-org/gitlab-ce/issues/50459
Hopefully, it will be implemented eventually.
Not only the syntax is supported, but GitLab 15.2 (July 2022) adds:
Live preview diagrams in the wiki WYSIWYG editor
GitLab Flavored Markdown includes extensions to support Mermaid, PlantUML, and Kroki diagrams but writing anything other than the most basic diagrams can be cumbersome without a live preview.
You can toggle between the raw source and static preview and there are external tools you can use to write these diagrams, but the shift away from your content can be distracting.
GitLab 15.2 introduces a live rendered preview of your diagram in the wiki’s WYSIWYG editor.
Now, as you write your diagram in a specialized code block we will detect the diagram type and display a preview icon.
When enabled, the live preview renders above the code block and updates as you type, so you can ensure your formatting is correct and the output will be exactly what you expect.
See Documentation and Issue.
Question
The editor brackets can do that. Supposed that, when I click my html tag in my source code file, the browser would automatically highlight the section/div in the broswer like google chrome developer tools.
Step 1
Click my tag in my source code file
Step 2
the live server will automatically focus on the section I want
How could I make it in VSCode?
VS Code does not have a built-in live server. Whatever extension you are using for live server can implement this, however I am not aware of any ones that do currently. Consider filing a feature request against them for this
Look at Five Server extension.
I used to love this Live Preview of Brackets, mainly for two unique features unlike many other editors and extensions:
It shows the preview live, literally. It doesn’t wait for file save to show the changes.
Highlights the section in the preview, corresponding to the html tag in which the cursor is placed currently.
I have been looking for a similar VS Code extension for a while.
Finally found it, JUST NOW.
I'm using Bolt.cm and when editing a Page or Entry, there is a section on the right called "the stack". On the Bolt site it says
Our Stack functionality contains your latest uploaded files, and allows you to access them as conveniently as possible. So no more searching and no double uploads.
But what does it actually do? I uploaded some images and they are shown on the stack, but I can't click or double-click them, and dragging them to the editor inserts the thumbnail, not the actual image.
The only way I see to add images is to click the editor's image button, then "browse server" and find it that way. So what's the point of the stack?
Good question, I don't think that the Stack is documented anywhere.
I had been neglecting the Stack for some time too, but recently I had to link to downloads (pdfs) in a Wysiwyg field. First I put them on the stack, and then could I link to them via the (chain symbol) link button.
But there's probably other usecases that I am not aware of yet. Anyone?
You have to set images to true under wysiwyg in config.yml to use "the stack." I guess the developers feel that having it enabled opens the editor to "dangerous" behavior. There are worse things the users can do. I was very close to dismissing this CMS because ridiculously enough, it couldn't insert images or embed videos. It can, the developers didn't document this crucial step.
wysiwyg:
images: true
I've been struggling all day trying to build Chromium and understand how branding works, but no luck with the later one.
The question is: how can I change the application name, logo and default search engine in the source files of Chromium ?
Got it:
On Chromium dev by James Atkinson
How to change Chromium app name and logo?
"What is the right place to change Chromium application name, program
title, .exe file name, and logo image. I guess there is place in
source code for windows, where it could be changed centralized for
whole project?"
There isn't a centralized place to change all at once. I'll advise you to go through .grd files search for .ico file an look at resources folder under chrome/browser/ it will give you a good start.
There are actually more places needs to be changed and I didn't found any doc describing the process.
There are some branding constants which are in the source itself, Like the folder name under app data which is embedded inside the code itself.
Have a wiki installed in our organization, and want to start using it.
Failed to find the answers for the next 2 basic questions:
How do I configure the entry page to show a list of all existing pages
How do I create a new page (!). Only succeeded doing it by typing a url of an non existing page. Guess there are nicer methods for this
Thanks
Gidi
For how to show a list of all pages, look at DynamicPageList, which is part of MediaWiki. (There's a more advanced third-party version, but it's not needed for such a simple task.)
Creating a new page really is exactly as you said: Type a URL and save some edits. Most beginning editors will edit a link into a page, and then use that link to browse to the page, so that they don't accidentally forget the spelling and lose the page to the Ether. (Of course it would show up in the recently edited and other special pages.)
This is more of a webapps.stackexchange.com question though.