Thank you, I didn't know that blank lines could cause errors. I delete these closing tags anyway that are not needed anyway (Github).Seems there are a few php files in this addon with blank lines after the closing ?> php tag - this is causing server errors etc.
Version 2.2.3 released
- Get rid of unnecessary closing php tags. Some of them were followed by white lines and may create php errors. Thanks to Luke Foreman.
I'm not sure it's possible and if it is, i don't know how to do it. I'm using the data registry to get back the editor configuration, then, and I think the slow part might come from a solution provided by Infis to compile some code in order to manually activate xen tags (see line 209). To be honest, the addon integration would need be redone, especially the template part, but I don't have time to do this.
This query need to include language_id in the where clause in order to use the key properly. At >5ms, it's the slowest query on the page when viewing threads
.markItUpContainer .markItUpEditor{
height:300px !important;
}
I took some time to trace where this extra db request was coming from. Short version: the template compiler was meant to be used in the admin side and stock in a table row (by language) some parsed code ready to use. Now there's a solution to avoid that very long request:
This query need to include language_id in the where clause in order to use the key properly. At >5ms, it's the slowest query on the page when viewing threads
$compiler = new XenForo_Template_Compiler($params['xenSet']);
$segments = $compiler->lexAndParse();
$phrasesUsed = $compiler->identifyPhrasesInParsedTemplate($segments);
$translatedPhrases = array();
foreach($phrasesUsed as $phraseKey)
{
$translatedPhrases[$phraseKey] = new XenForo_Phrase($phraseKey); //require to have globally cached phrases
}
$fakePhraseCache = array($lang_id => $translatedPhrases);
$compiler->mergePhraseCache($fakePhraseCache);
$compiled = $compiler->compileParsed($segments, 'MarkitUpIntegrator', $style_id, $lang_id);
eval($compiled);
$params['xenSet'] = html_entity_decode($__output);
Version 2.2.4 released
- Optimize db request delay - Thanks to Luke Foreman
After update, reimport bulk buttons.
I don't have this bug. Please check your browser console to check any JavaScript error and check with the default XenForo theme.@cclaerhout , thank you for useful addon!
There is some issue while switching to Rich-text Editor.
When I click on the link Use Rich Text Editor, it's loaded with opened Color picker window at bottom-left of editor window:
Can you fix this issue?
I tried to reproduce this bug with default XenForo theme.Please check your browser console to check any JavaScript error and check with the default XenForo theme.
Tested on Chrome (32bits) 49.0.2623.112 m, then 50.0.2661.87 m, everything works fine. I don't think the 64bit version would change anything with a hide/show function. Try to check any error in your browser console.I tried to reproduce this bug with default XenForo theme.
It can be reproduced only in Google Chrome (my version of Chrome is 49.0.2623.87 (64-bit)), but in Firefox all fine.
Version 2.2.5 released
- Fix a bug with invalid smiley image link (with direct url)
?Is the textarea under a span?
You're right, they were in previous versions of XenForo but have been deleted. I will need to update this.I think there are a couple of missing phrases in the insert link popup:
What I meant was, is the <textarea> or <input> inside a <span>? Like:
<span>
<textarea> / <input>
</textarea> / </input>
</span>
Where do you see that? In which part of the code? I will have a look later.What I meant was, is the <textarea> or <input> inside a <span>? Like:
Code:<span> <textarea> / <input> </textarea> / </input> </span>
We use essential cookies to make this site work, and optional cookies to enhance your experience.