I'm trying to add browse server image option to my ckeditor.
I know I need to add this:
CKEDITOR.replace('editor', {
filebrowserImageBrowseUrl: ''
});
But what then? What am I to do in order to add this feature to my ckeditor?
What link should I put there?
How I build a directory with all of my images?
What is the difference between "filebrowserImageBrowseUrl" and "extraPlugins: 'imageuploader'"?
CKEditor itself does not provide any server side code that handles image uploads. It just provides JavaScript plugins which let you integrate your own file manager/uploader (if you have any).
If you don't have a file manager, you may try CKFinder, which integrates well with CKEditor: https://cksource.com/ckfinder/download
There is a "CKEditor" example included in the samples folder which shows both applications running together. Make sure to enable CKFinder in config.php - due to security reasons it's disabled by default.
Related
I'm using the swagger-editor docker.
It produces, in the right column, a beautiful and functional interactive version of the documentation I'm writing in the right column.
I am trying to export such documentation but to no luck.
Is it possible to export an interactive, stand alone, documentation looking and working as the one shown in the right column?
The right-side panel of Swagger Editor is Swagger UI. You can download Swagger UI assets and host them on your own website.
Download (or clone) the Swagger UI repository:
https://github.com/swagger-api/swagger-ui
Take the dist folder - it contains the static assets.
Put your OpenAPI YAML/JSON file to the dist folder.
In the dist\index.html file, change the url parameter to point to your YAML/JSON file:
const ui = SwaggerUIBundle({
url: "myapi.yaml", // <----
Put the files from the dist folder on your web server.
It's also possible to embed Swagger UI into your existing web page, e.g. if you want to have your custom branded header and footer.
See also:
Is it possible to get an offline version of Swagger documentation for a website?
Swagger UI single interactive HTML
I trying to use CKEditor5 and CKEditor-react in my electron app.
And i want to paste image in editor, but i have an error
filerepository-no-upload-adapter: Upload adapter is not defined.
Docs says that I mast using cloud. But my app must working locally and without internet
Can someone help me?
The docs say, in short, this:
To handle image upload in CKEditor 5 you can use one of these:
use the built-in Easy Image adapter (cloud service),
use the built-in CKFinder adapter (can work locally if you want),
write your own adapter (in which case, please refer to the UploadAdapter interface documentation).
The last option gives you a complete freedom on how and where you want to send those files.
PS. You can find a bit more details in this question: How to enable image upload support in CKEditor 5?
I want to change the look and feel(ui customization) of Jenkins. Also I would like to add new views(say like new html pages or web pages) with navigation to the required jenkins pages etc.
Please let me know if any single plugins will help me to do so.Any relevant information(how ever generic) will be very helpful.
Any suggestions or links or tutorials is also appreciated.
PS:- Pretty new to jenkins.The inputs from here will help me to add more details to the questions.
I am looking for documents or tutorials that specify Skinning Jenkins using plugins like :-
https://wiki.jenkins-ci.org/display/JENKINS/Simple+Theme+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/jQuery+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/jQuery+UI+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/JSWidgets+Plugin
The plugin page is providing very little information on how to use these and the benefits and the extend to which the UI can be changed.
Any doc or link is appreciated.
Assuming you don't want to write a Jenkins plugin, for adding pages, the best suggestion I can make is to use an HTTP proxy such as NginX, and configure it so that the pages you want to add are plain html files, and Jenkins is proxied for the rest of them. To a visitor, they will look like they are all part of the same site; you could copy code from the head and body sections of Jenkins-served pages to include some of the navigation.
The Simple Theme Plugin, which you found, will let you do basic customization of the look and feel of Jenkins. I do that for my build server and proxy it using this configuration fragment for NginX. The relevant CSS is in this CSS file - toward the end, look for the // JENKINS CUSTOMIZATION comment.
We use the Simple theme plugin - pointed at a css file for the simple styling, and a JS file to fix a couple of DOM oddities (some of the tables in the new look and feel have mismatching column counts).
Those two files need only be hosted either a handy http server, or you can place them in usercontent.
You need only refresh the page in the browser to see the changes. Both files can then happily reference other files served up too.
Handy things to note:
Jenkins has jquery, parts of YUI loaded and prototype loaded - so you can use them in your scripts.
If while debugging, the refresh gets in the way then use the console to enter the following to temporarily stop it without pausing JS: refreshPart = function() {}
When making DOM tree changes to content that is refreshed - attach it to the layout updates with:
layoutUpdatecallback.add(my_function) - that way your changes are applied to new incoming content.
Does anybody know how to disable certain plugins from loading in the back-end/admin area of Wordpress?
Currently I'm running a site that has many plugins mainly geared towards front-end manipulation yet when I access pages in the backend (ie. /wp-admin/edit.php) all CSS, JS and plugin files are being loaded for plugins that are not required there, thus increasing the load-time and responsiveness of the admin area.
I'm looking for a solution, either plugin based for code that can selectively load admin only plugins, ideally without having to hack the core files.
I'm using wordpress 3.5.1.
Checkout Plugin Organizer. I haven't used it but according to it's description, you can "Selectively disable plugins by any post type or wordpress managed URL". I would guess that you could disable certain plugins from running on urls that contain /wp-admin/.
You can also modify the plugins themselves. It depends how they are written, but you can find where they are enqueuing the css and js files and wrap those in an is_admin() statement like this:
// Make sure we aren't in the admin area
if ( !is_admin() ) {
wp_enqueue_script('plugin-script');
wp_enqueue_style('plugin-style');
}
That will ensure that the scripts/styles are only loaded on the front end.
Another possibility is to find all of the css and script files that are being loaded via plugins and deregister them in your functions.php file. This will require you to poke around the plugins a bit to find the handles of all the files, but it should work well. This would deregister some of the default stuff enqueued in the admin area, so you can see what I mean.
add_action( 'admin_init', 'remove_admin_styles' );
function remove_admin_styles() {
wp_deregister_style(
'wp-admin',
'ie',
'colors',
'colors-fresh',
'colors-classic',
'media',
'install',
'thickbox'
);
}
As you said, you don't want to mess with core files, but if you absolutely need to you can implement the solution described in this article. As I'm sure you know, it's not a good idea to alter WordPress core files unless you absolutely have to. Just keep in mind that the changes will be wiped out if you upgrade WordPress in the future.
I have an ASP.NET MVC 3 website that works perfectly in IIS7 integrated mode. However, I need to deploy this in classic mode.
In order to do so, we manually inserted the handler mappings in IIS to handle urls for .mvc extensions as suggested in the link in the global.asax file.
But in classic mode, none of the static files (css, images, javascript) are getting loaded. Is there some other setting that I need to do to get these working.
When I tried to see these in fiddler, I can see an HTTP error 500 for all of them. I have already tried the following approaches:
Added the following line of code in the web.config httpHandlers section
add verb="" path=".png" type="System.Web.StaticFileHandler"
Checked the 'Static Content' in Common HTTP features on IIS.
I am not sure what to try next.
The usual workaround is to configure "Wildcard Script Map", please read more here.
The issue was related to improper relative paths, which didn't work out when we deployed. Having the proper relative path showed the images and other files perfectly.