The main issue is a dialog for links: for external links the target dialog is empty.
But the issue itself seems to be that this dialog and also other dialogs of TinyMCE and the control panel for TinyMCE is in english, not the language of the website, which is not english.
Any hint where to start debugging?
Plone 4.3.11 , TinyMCE 1.3.23 default for Plone 4.3.11
german
Looks like the translation-files aren't compiled and that you ran into https://github.com/plone/Products.TinyMCE/issues/149, where M. v. Rees makes several suggestions for resolving.
If you have monolingual site, you can also quickly compile the German files manually, like:
$ cd eggs/Products.TinyMCE-1.3.23-py2.7.egg/Products/TinyMCE/locales/de/LC_MESSAGES
$ msgfmt -o tinymce.po tinymce.mo
$ msgfmt -o plone.tinymce.po plone.tinymce.mo
Related
HCL Connections has some kind of customized build of TinyMCE, which could be officially used as replacement for the old CKEditor. I'd like to know which version is installed. Especially on test systems I'm not sure which version is currently installed on which system.
Found out that this could be fetched from JS variables in the browser console:
tinymce.majorVersion + '.' + tinymce.minorVersion
"5.1.1"
But it misses the patch version 5.1.1-XX where XX is a number. Is there any other way how to find out detailled information about the installed version?
There is a test page avaliable on the following url: https://cnx.host/connections/resources/web/tiny.editors.connections/verify.html
When TinyMCE was successfully installed (may require a restart of at least the common app), you'll see something like this:
Tiny Editors for HCL Connections has been successfully installed. This
is release 4.1.0.15
The TinyMCE version in this release is 5.1.1-57.
The Textbox.io version in this release is 2.4.2.95.
This gave you four information:
The installation itself works. When enabled in config.js, you'll use TinyMCE instead of CKEditor in all Connections applications (Wikis, Blogs, ...)
The exact version numbers of TinyMCE = 5.1.1-57 (independent from Connection)
The Connections Editor version = 4.1.0.15 (HCL bundle of TinyMCE and Textbox.io editors)
The Textbox.io version = 2.4.2.95 (also independent from Connections, only relevant when using Textbox.io instead of TinyMCE)
The TinyMCE version we ship for connections isn't a customised build; our customisations are all done through public APIs and configuration options (including the premium plugins).
If you see 5.1.1-57, that should be an exact copy of the public 5.1.1 release available on our website. 57 is just an internal packaging build system number.
If you open the editor help dialog there should be version information there as well (but only the connections package version and current editor version, not both editor versions).
The help dialog also contains the version of the editor and the integration. This is true for both textbox.io and TinyMCE and the steps are roughly the same. I show images for TinyMCE below.
First open the "cog" menu and click on the "Help" entry:
Second select the "Version" tab to view the version:
I try the latest Play Framework 2.3.7 on Mac OS Yosemite, then I followed the tutorial to create web page
$ activator new my-first-app play-scala
$ cd my-first-app
$ activator run
It's generated a nice looking page with colors and many contents and a header like this:
Then I type Ctrl+D to close this application, and use the production mode:
$ activator start
It only generates a plain text web with only the header like this:
What should I do to show all the other stuffs in the production mode?
That's expected. The Play welcome page helper includes a stack of things, including links to the full locally served documentation and stylesheets/images/etc, that are (rightly) turned off in prod mode. So in prod mode, because all that stuff that the welcome page needs is turned off, the welcome page instead renders an unstyled one liner, as you can see.
So, I've been using Sublime for a while as a simple text editor, but I'm venturing into the land of plugins for work and I've run into an issue getting pylint to work. Specifically I have it installed and have the Sublime package manager working, but I'm not sure how to include paths in my sublime settings.
I haven't found very useful documentation on this point, but if you are willing to point me towards it that would be a perfectly acceptable answer. My basic issue is that currently every time I save a file, the following error message shows up:
"Please define the full path to 'lint.py' in the settings"
I understand this error message which is great, I just have no idea where the sublime settings are or what the standard format for defining a path is. Any help would be appreciated.
There are quite complete directions at the SublimeLinter GitHub page that should describe how to set everything up. Briefly, go to Preferences->Package Settings->SublimeLinter->Settings - Default to see where the different settings are defined. Then, open Preferences->Package Settings->SublimeLinter->Settings - User to change anything, as the main settings will be overwritten when the package is updated. Remember that settings files are in JSON format, so you'll need opening and closing curly brackets to enclose settings, and a comma between them:
{
"sublimelinter_delay": 30,
"sublimelinter_mark_style": "none"
}
I haven't gotten the error you have, are you sure you're using the regular SublimeLinter and not the new beta version? I just installed it fresh on my work machine (I've been using it for a while at home) and after restarting ST2 it's working like a charm with Python.
I had the same problem. I found it to be coming from the package "Pylinter". I removed Pylinter and added SublimeLinter, it covers more than python and is well used. I'm enjoying it quite a bit.
From your command line just run:
sudo easy_install pylint
sudo easy_install pep8
After that restart your sublime.
I encounter the same situation today. In my case, that is because I have not installed the 'pylint' in my system yet. It works fine after I installed the 'pylint' through pip.
Just for other people reference.
I'm finding myself unable to add links ("a" tags) via the version of Products.TinyMCE in Plone 4.3b1. Switching to a non-visual editor and manually adding a link works fine, but using the chainlink icon in TinyMCE brings up an insert/edit popup window that doesn't appear to have anyplace to enter the destination address. There's a "search" text field, but entering text into it does not enable the "OK" button.
Here's a screenshot of what I am seeing:
Does anyone know if this is a known issue, or if I'm just completely missing how to enter links, or have any light to shed on this? Thanks.
UPDATE:
The problem seems to be that the popup's tabs are not un-hideing the relevant divs. When I use Firebug to switch div external_panel from class="hide" to class="show" the missing material appears; I also have to use Firebug to remove a disabled="disable" from the OK button in order to press it. A screenshot showing the segments is below. I've used the tgz file of the unified installer; is it possible that there is a variation between that installer's contents and the binary installer for the Mac?
The problem is showing up on a plain vanilla fresh install performed by
- untarring the 4.3b1 unified installer tgz file,
- running the command ./install.sh --target=/home/me/P4.3b1 from the installer's dir
- going to /home/me/P4.3b1/zinstance
- running the command bin/instance fg
- going in the browser to localhost:8080,
- creating a Plone instance and logging into it as admin
- going immediately to edit the front page of the site.
Version overview from site setup page is as follows:Version Overview
- Plone 4.3b1 (4302)
- CMF 2.2.7
- Zope 2.13.19
- Python 2.7.3 (default, Aug 1 2012, 05:16:07) [GCC 4.6.3]
- PIL 1.7.7 (Pillow)
I'm going to say cross browser compatibility issue. It looks like this in Firefox and works as expected:
I've been using Eclipse on Windows a lot, and recently started using it on Ubuntu for work.
My problem is, that the Javadoc tool til mostly is unformatted, E.g. <code> tags, links, etc. have no effect. Only line chages by b, br or ,pre tags plus bold seems to be rendered. (pre don't change font.). See the first example below.
Are there any tweaks I can do, to get something like the second image?
Extra: A fix to the colors, would be also be awesome, but not as important.
Thanks.
What I see now:
What I'll like to see
Soruce: http://codeblessyou.com/wp-content/uploads/2011/07/2011-07-01_115631.jpg
Got the same problem with the rendering of HTML inside the tooltips. After some fiddling around I got the solution:
Install libwebkitgtk-1.0-0 from the official Ubuntu repositories. It'S used by eclipse (and most likely other GTK applications) to render the HTML, but neither pre-installed on Kubuntu nor listed as a dependency in the eclipse packages.
It turns out this is caused by two problems:
Eclipse needs webkitgtk
Eclipse color scheme is messed up on ubuntu.
The solution is thus two-fold.
Part 1: Install webkitgtk
Just run this command in the terminal
sudo apt-get -y install libwebkitgtk-1.0-0 libwebkitgtk-3.0-0
Thanks to Johannes H. for this bit
Part 2: Update the color scheme
First create a new configuration in your home directory.
gedit ~/.gtkrc-eclipse
And paste this content:
# Customs color settings for Eclipse.
# Load Eclipse as follows:
# GTK2_RC_FILES=~/.gtkrc-eclipse eclipse
#
# Sources:
# http://stackoverflow.com/a/24043778/722929
# http://askubuntu.com/a/131348/18533
# http://weblog.avp-ptr.de/20120728/how-to-fix-eclipse-colors-for-autocompletion-and-tooltips/
# Tooltip background color.
style "eclipse-tooltips" {
bg[NORMAL] = "#f5f5b5"
fg[NORMAL] = "#000000"
}
# Load settings.
widget "gtk-tooltip*" style "eclipse-tooltips"
Find the eclipse43.desktop file and edit it (If you are using another version of Eclipse than 4.3 update the commands accordingly):
locate eclipse43.desktop
# Use the location from above
sudo gedit /usr/share/applications/eclipse43.desktop
Find the line that starts with Exec=... and change it from something like this:
Exec=/usr/bin/eclipse43
to something like this
Exec=/bin/bash -c "GTK2_RC_FILES=~/.gtkrc-eclipse /usr/bin/eclipse43"
Voila, beautiful colors. (or as beautiful as Eclipse gets)
For the question of background color, the problem certainly comes from the GTK settings.
You should get a solution here https://askubuntu.com/questions/70599/how-to-change-tooltip-background-color-in-unity
For Eclipse Mars methods with GTK2 don't work anymore. You should only edit usr/share/themes/Ambiance/gtk-3.0/gtk-main.css section with name /*default color scheme */. Change #define-color tooltip_bg_color and #define-color tooltip_fg_color for your favorite color.