see for yourself what happened (if you do not see it, use ctrl+a):
http://efg-test.xf1.de
Well, the descrition says the plugin puts code into the head of the blog, so I am not complaining...
![Mr. Green :mrgreen:](./images/smilies/icon_mrgreen.gif)
Bernd
I would assume that you have the NL2BR plugin active (for content areas) using the NL2P option and that the NL2BR plugin is placed before the head nugget plugin in the event plugin list?kybernator wrote:see for yourself what happened
yesyellowled wrote:I would assume that you have the NL2BR plugin active (for content areas)
no, not yetyellowled wrote:using the NL2P option
yesyellowled wrote:and that the NL2BR plugin is placed before the head nugget plugin in the event plugin list?
ok, did so, head nugget is first in the list now, no visible change.yellowled wrote:If so, try moving the head nugget plugin in front of NL2BR in that list.
That is odd. Any other markup plugins (Markdown or Textile) active? Try clearing the cache in the Maintenance section of the backend, please. Also please try setting NL2BR to “inactive” temporarily (don't forget to save after moving plugins in the backend!). Does that change anything?kybernator wrote:ok, did so, head nugget is first in the list now, no visible change.
Favicons and especially touch icons are complicated. It depends on whether you place the files in the root directory of your web space or in a directory. Also, these files and their sizes change all the time, especially for Apple devices. Some of them fallback to others if they're not present, others don't, and it's debatable whether for example the windows tiles are even necessary.kybernator wrote:I am not sure if I need the favicon code, anyway (a favicon showed up right after I uploaded the icons, I was just adding the code to have OSs choose the "best" one), so this is not a pressing matter for me, for now.
Not at all, still investigating.onli wrote:YL, are you sure about that?
You know me so well.yellowled wrote: You can use http://realfavicongenerator.net to generate all those icons plus the code, but I assume you already did use that.![]()
I think I will go this pragmatic route: have all icons in root, do not use the head-code and accept that there is room for failure. A favicon is not such a big deal, anyway.yellowled wrote:If you want to do this easily, though (and maybe risk that some platform don't get the proper favicon, there is a pragmatic alternative.
Yesyellowled wrote:kybernator, for the record – you do use the WYSIWYG editor, right?
Yes, IIRC - I just deleted the plugin, could repeat the procedure tomorrow, not today anymore, must do something else right now.And it is in fact active when you edit the head nugget plugin's content (e.g. the touch icon markup)?
Do we need a GitHub issue for this or is it a quick and easy fix?Timbalu wrote:Proposed patch, change $propbag->add('type', 'html'); to 'text'?
No issue necessary. Its an easy fix converting back to a text textarea or even double it like Garvin did with the other plugin. I don't think we need this actually, but I never use plugins like this!yellowled wrote:Do we need a GitHub issue for this or is it a quick and easy fix?
No, old editors like Xinha were called too. If you put ayellowled wrote:Just out of curiosity – is this an issue because we now use CKE, did we fix something accidentally or why do these instances of WYSIWYG editors where there should not be one keep popping up?
Code: Select all
<meta http-equiv="imagetoolbar" content="no" />
Code: Select all
<meta http-equiv="imagetoolbar" content="no" />