Get XOOPS XOOPSXOOPS FAQFAQ ForumsForums NewsNews ThemesThemes ModulesModules
News World of XOOPS Developers Hacks Modules Themes YAXS Archive Submit News

Search

Donat-O-Meter

Make donations with PayPal!
Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $65.00
Net Balance: $61.80
Left to go: $38.20

Donations
studioC  ($25)May-17
Anonymous ($15)May-16
Anonymous ($25)May-4

Learn XOOPS Core

Local Support

Advertisement

XOOPS Code hosted on SourceForge

Cumulus Tag Cloud

2 2.5 2.6 3.0 90 2013 Abuse admin AntiHarvesting AntiMalUser AntiSpam API Beats billige black Blocks blue Captcha cell Checksum Christmas chronolabs content Conversion demo docek download Dresses EC2 editor ELB evden eve facebook floor free games herre Honeypot Human IP jQuery kantor klubovi lamps log logger Marquee mobile module modules Monster MyAlbum-p newbb news newsletter online oxygen PageRank Payment Permissions pink Plugin portal Prevention profile project Protector Protocols publisher Rights rmcommon Room sale security Server site Smarty Spam stem Studio support tag tags tdmcreate Theme themes txmod Umfrage upgrade User userlog website Whitepaper WSDL xoops XOOPS2 Xortify XPayment ZendFramework

New Users

Registering user

# 136021

dressshop

Welcome to XOOPS!

Archives

News Archives

tinyeditor 1.0 BETA released

Posted by frankblack on 2006/7/8 7:03:14 (12832 reads) | Posted on Modules
We are proud to announce the release of tinyeditor 1.0 BETA.

As always it is NOT recommended to install a BETA on production sites.

The changes since the ALPHA-version are legion. So here a short summary of the most interesting changes:



1) The whole module re-packed: tinyeditor wasn't tiny anymore, so I repacked the whole thing. The main module has the most used plugins included. All the other plugins can be installed separately.

2) xrmanager nearly finished: besides some minor parts, xrmanager is ready for use. xrmanager is a resource-manager for files and images. You can copy, move, edit etc. files and images as you like. This plugin plugs into other plugins like links, images and flash. There you have a browse-button where you can almost do what you want.

3) Plugin and lang-file upload: if your system allows it - most systems should do - you can upload plugins or langfiles as zip. The zip will be extracted and the content put at the right place.

4) Chmod your folders with FTP. If your server understand chmod, you can apply chmods to any directory or file within your XOOPS system. Funny sidenote: I am a developer of web tools without web space, so this function is pure theory. I would be really excited it this works!

5) An extra parameter is added to the tinyeditor-class. With this extra parameter you can turn any dhtml editor area into WYSIWYG with just a few lines. This WYSIWYG tries to imitate the functionality of the dhtml editor. The module developers do not have to re-write their implementation of tinyeditor - it is just a tiny add-on.


What happens next? The RC versions will only contain bug fixes, performance improvements and some tiny additions regarding permissions and disk quota. Perhaps xrmanager will have a new context menu


Some documentation, incomplete inside the module's administration and more complete on dev.xoops.org, might help you with tinyeditor. I am currently working on the new documentation for tinyeditor 1.x, but all plugins covered this is gonna be a huge task for and will take some time. Sorry for this!

All files can be downloaded here

Documentation can be downloaded here

Bug tracker here

Feature tracker here

Support forum here


A final remark from me: we need your feedback for this module and we need translations for this module or the plugins. So support us!

XOOPS on!
ralf57 / frankblack


Printer Friendly Page Send this Story to a Friend Create a PDF from the article
Bookmark Me
Bookmark to Google Plus
The comments are owned by the author. We aren't responsible for their content.

Hi
Nice job! Does this new version work with tables?
Published: 2006/7/8 7:56 • Updated: 2006/7/8 7:56
I was waiting for that one impatiently

GREAT JOB !

I'll re-contact you soon once I looked at it precisely and have enough feedback to give you.
Published: 2006/7/8 7:57 • Updated: 2006/7/8 7:57
Realy great news.
And nice to have the size down to a more sensible level.
The documentation is really nice looking and a good read, too. Looking forward to seeing the final documentation.

It appears wiwimod (0.86) does not like tinyeditor beta (nor did it like the aplha).
Did anybody already make a fix for this problem?

Regards
--
Daigoro
Published: 2006/7/8 10:05 • Updated: 2006/7/8 10:05
Quote:
Nice job! Does this new version work with tables?


According to page 9 of the manual it does work with tables.

It's good to see a XOOPS module coming with a good manual!

Great job, I will test it.
Published: 2006/7/8 10:07 • Updated: 2006/7/8 10:07
I have a patch for wiwimod. I only have to pack and submit to d.x.o so please wait a little while.
Published: 2006/7/8 11:02 • Updated: 2006/7/8 11:02
Thanks Frank.

I'm looking forward to see the patch.

Great work!
Published: 2006/7/8 12:29 • Updated: 2006/7/8 12:29
THIS is the patch for wiwimod 0.8.6 Beta. I did not found a newer one and I hope it works.

Just copy the files over (backup before) and to be sure, update the module.
Published: 2006/7/8 13:20 • Updated: 2006/7/8 13:20
Hi Frank,

Thanks for your quick responce!

I just installed the patch (and remembered to update)... but it still failed.

Looking thrugh the code, I found the culpit and did something about it... but I'm quiet sure it's not the best fix. Perhaps you can help?

The problem is the dreaded blank page from hell.
I located the error in modules/wiwimod/include/functions.php, where I commeted out the following code:
if (file_exists(XOOPS_ROOT_PATH '/class/xoopseditor')) {
 include_once(
XOOPS_ROOT_PATH."/class/xoopslists.php");
 include_once(
XOOPS_ROOT_PATH."/class/xoopseditor/xoopseditor.php");
 
$editorhandler = new XoopsEditorHandler();
 
$xedArr array_flip($editorhandler->getList());
 foreach (
$xedArr as $xedTitle => $xedName) {
  
$arr[] = Array("XE - $xedTitle"$xedName );
 }
}


And why did it fail?
Xoops 2.0.14 does not have the /class/xoopseditor/xoopseditor.php file, and thus the script breaks.

I guess the best fix would be to get hold on the xoopseditor.php file... but where is it?

Do you have other idears?
Published: 2006/7/8 14:56 • Updated: 2006/7/8 14:56
My site was recently build using the latest 2.0.14.rc1 and then updated to 2.0.14.

When using tinyeditor 1.0 beta from wiwimod (thanks for the patch), and trying to insert an image, FireBug catches no less then 150 exceptions before the popup windows is finally opened.

The exceptions are all simmilar to the one shown below:

[Exception... "'Permission denied to get property XULElement.accessKey' when calling method: [nsIDOMXULLabelElement::accessKey]" nsresult"0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)" location"JS frame :: http://tegneserielogen.dk/logen/modul ...  :: line 1datano]



When the popup finaly appear, it's width is only about 100 pixels wide... too small to see all the contents. And it's locked in size.

This is with Firefox 1.5.0.4. I've disabled my extensions to make sure none of them is messing up things.

I'm not sure if this is a XOOPS 2.0.14 problem, or a tinyeditor problem, so I'm both posting this on the XOOPS site and erporting it to the tinyeditor buglist.

--
Daigoro
Published: 2006/7/8 16:09 • Updated: 2006/7/8 16:09
I will add xoopseditor.php shortly in the BETA-package. <- added

Daigoro, is the editor behaving the same, when gzip is turned off. Recently I had a problem with the Adblock Plus extension for Firefox blocking nearly ALL javascript, but you turned off already the extensions so gzip must be to blame?!?
Published: 2006/7/8 17:54 • Updated: 2006/7/8 18:07
I also fixed a problem with the ximagemanager plugin resulting from bad compressing (removing linefeeds, blanks, comments from the js-code).

I do fear, that this happened maybe in other plugins as well.

Does anyone know a FREE javascript-compressor (I can't afford to buy one - poor sott ?
Published: 2006/7/8 18:16 • Updated: 2006/7/8 18:16
Honestly, I was having better luck with the alpha release.

Now when I go to edit a post all the linefeeds andformatting are removed.

Also, when trying to link an image to a url I can't seem to save the link. No matter what I try I can't insert or cancel the link creating popup window.
Published: 2006/7/10 5:53 • Updated: 2006/7/10 5:53
Quote:
Now when I go to edit a post all the linefeeds andformatting are removed.


What is your XOOPS version and the module (version) where the formatting is lost?

Do you want to link to the image with the "normal" image tool of tinyeditor? I will test this again and let you know.
Published: 2006/7/10 7:26 • Updated: 2006/7/10 7:26
The XOOPS version is 2.2.4.

The image appears in the edit buffer just fine, but when I click the link icon to link the image to a URL is the problem. I can put in the link informatin, select to open in same or new window, put the alt text in, but when I try to insert the link it will not let me do it, and the cancel button doesn't work either.

As for the formatting disappearing, I was using news 1.44 with the patch provided on the dev site.
Published: 2006/7/10 8:07 • Updated: 2006/7/10 8:09
I will come back later to this terrion.

Came back start: I was trying this myself and did what you did, but I had no problem. So we can narrow down the problem to the browser. Since the ALPHA release some core files of tinyMCE have changed, so I need to know what browser you are using (version) and if Firefox/Mozilla what extensions are you using? Lately I had severe problems with the Adblock Plus extension breaking nearly EVERY javascript.
Came back end

In the meantime I released a PATCH for ximagemanager-plugin. Unzip it and copy/overwrite the files on your server.

Solved the problem with ximagemanager and XOOPS 2.2.4, but I don't understand it. Nearly everything is working fine, but the templates are NOT understanding <{$xoops_url}> anymore. If I explicitly assign XOOPS_URL AGAIN it works. So wth...
Published: 2006/7/10 9:45 • Updated: 2006/7/10 20:17
Hi Frank,

Sorry I couldn't respond to you allready yesterday.

Thanks for the xoopseditor.php.
Now it's possible to select TinyEditor as a xoopseditor from within wiwimod. However, it's not really working - the result is hard to explain, but the page becomes a mix of teh normal wiwimod output and the html-text that's briefly shown when loading TinyEditor.

You were correct that the problem with all those firebug hits were related to the gzip compression. And your latest update seems to fix those errors, too.

But I'm still having problems with the insert-picture popup. When clicking on the insert picture icon, the popup shows briefly at correct size - only to resize to a width of aprox. 100 pixels when all the window contents has been loaded/rendered.
Since the popup is not scrollable, it's impossible to insert pictures.

Everything else I've tried within the last 30 minutes, seems to work like a charm. Good work!
Published: 2006/7/10 12:42 • Updated: 2006/7/10 12:42
Quote:
Solved the problem with ximagemanager and XOOPS 2.2.4, but I don't understand it. Nearly everything is working fine, but the templates are NOT understanding <{$xoops_url}> anymore. If I explicitly assign XOOPS_URL AGAIN it works. So wth...


A few months ago I tried to replace the standard XOOPS ImageManager by myAlbum-P. Never worked with XOOPS 2.2.4.

I guess the developers of XOOPS ImageManager had the same problem with <{$xoops_url}> and decided to place the php-file in the root to solve the problem. Ever wondered why the html-files were placed in ../modules/system/templates/.. ... Click to see original Image in a new window
Published: 2006/7/10 13:17 • Updated: 2006/7/10 13:17
Hmm..

Did I turn blind - or did you forget to upload that patch?
Published: 2006/7/10 13:46 • Updated: 2006/7/10 13:46
Hi Frank! Thanks for the module. Unfortunately many features didn't work for me at XOOPS 2.0.14. 1. Check the emoticons plugin. It didn't work for me (there was a blank page opening) until I cleared up this code in emoticons.php:
if (file_exists('../../../../mainfile.php')) include_once '../../../../mainfile.php';

    if (
file_exists('../../../../../mainfile.php')) include_once '../../../../../mainfile.php';

    if (
file_exists('../../../../../../mainfile.php')) include_once '../../../../../../mainfile.php';

    if (
file_exists('../../../../../../../mainfile.php')) include_once '../../../../../../../mainfile.php';

    if (
file_exists('../../../mainfile.php')) include_once '../../../mainfile.php';

    if (
file_exists('../../mainfile.php')) include_once '../../mainfile.php';

    if (
file_exists('../mainfile.php')) include_once '../mainfile.php';

    if (!
defined('XOOPS_ROOT_PATH')) {
        exit();
    }
2. imanager and ibrowser didn't work for me, I added them to my toolbar and when I click on them a blank window opens. 3. And another bug: image editor browsing feature don't work. When I press "Browse" button blank page opens. Hope you'll fix it. Thanks anyway.
Published: 2006/7/10 13:51 • Updated: 2006/7/10 13:52
Hi, frankblack!

Great work, as always! :)

2 quick things (well, 3):

1) I've been unable to download the patch you mention. I can't even see the file!

2) I can't get xrmanager to show me the thumbnails. I installed image magick via apt-get, restarted the apache server, and changed the configuration to input the path to imagick.so.

3) I activate the Adv Link plugin, and I have a tab to link to XOOPS contents, but... it's empty!. I can't link anything!.

What am I doing wrong?.

Thanks!
Published: 2006/7/10 18:09 • Updated: 2006/7/10 18:09
You have to re-download the whole zip-file of TinyEditor 1.0 beta.
xrmanager is part of the module and not a separate plugin.
Published: 2006/7/10 18:42 • Updated: 2006/7/10 18:42
The patches for tinyeditor 1.0 BETA (CRAP-Version) you will find BETA-Patches

Some of the reported bugs I cannot confirm. The plugins emotions, imanager, ibrowser and the image-browse function (xrmanager) are behaving well on my dev-machine.

This has been tested on 2.0.13.2, 2.0.14 and 2.2.4 with PHP 5.14, MySQL 5.0.21, safe_mode on, register_globals off and allow_url_fopen off.

To make bughunting "easier" for me, send in the bugs to the bugtracker HERE. Please also provide information about your XOOPS-version, PHP-version and the browser-version you are using. And don't forget to turn PHP-Debug on and report the error messages when you experience blank pages.
Published: 2006/7/10 19:35 • Updated: 2006/7/10 20:32
Quote:
The patches for tinyeditor 1.0 BETA (CRAP-Version) you will find HERE


There are no files attached to the patches, I only see a short description.

I asume you mean you have patched it yourself and we have to download tinyeditor 1 beta only?
Published: 2006/7/10 19:57 • Updated: 2006/7/10 19:57
No I was trusting the xoopsforge-module on d.x.o. too much, that the uploaded files will be attached, but this wasn't the case.

Therefore you will find the patches HERE right beneath BETA-Patches.

Sorry for the inconvenience.
Published: 2006/7/10 20:12 • Updated: 2006/7/10 20:12
Quote:
the result is hard to explain, but the page becomes a mix of teh normal wiwimod output and the html-text that's briefly shown when loading TinyEditor.


A screenshot for me or access to the site to see myself?
Published: 2006/7/10 20:20 • Updated: 2006/7/10 20:20
Quote:

I was trusting the xoopsforge-module on d.x.o. too much, that the uploaded files will be attached, but this wasn't the case.


The d.x.o is too much messy with deprecated scripts.
Hopefully it can be worked on once the xoops.org re-organization is done.
Published: 2006/7/10 21:23 • Updated: 2006/7/10 21:23
Hi!

Quote:
You have to re-download the whole zip-file of TinyEditor 1.0 beta.
xrmanager is part of the module and not a separate plugin.


I did, I reinstalled the plugin from scratch.

Frankblack, thanks for the patches. I can use AdvLinks now (although the 3 combos appear on top of the labels, instead of at their right), but the thumbs are still not showing. I guess it's a problem with my imagemagick install or the link to the lib. Can't I just use GD?. Only a couple of admins are going to post news, so I don't mind if that part of the app is a bit loaded.

I'll set the debug mode and try to find where the error/bad configuration is. In the meantime, my config is: XOOPS 2.2.4, Apache 1.3, PHP 4.4.2, imagick 6.0.0.

BTW, is still necessary to indicate a correct path to the imagick lib if it's already loaded as a PHP module?. And I have to link the full path to imagick.so, right?.

Thx!
Published: 2006/7/11 3:46 • Updated: 2006/7/11 3:46
Of course you can use GD and the correct path is needed for thumbnail-creation.

And I will again look into the advlink-plugin and imagemagick.
Published: 2006/7/11 4:16 • Updated: 2006/7/11 4:16
I SWEAR THAT I WILL NEVER RELEASE SOMETHING WITHOUT TESTING ON DIFFERENT SERVERS ON THE WEB!

Another!!! patch can be found HERE

This is for patching xrmanager. Have a look at the readme inside.

Feeling sad and bad now...
Published: 2006/7/11 5:33 • Updated: 2006/7/11 5:33
Ok, spotted the error with the AdvLinks combos. Somehow, in my server, calling the functions lastLinks, openForums and so on in the middle of an echo, when they do echo's themselves resulted in their contents being echoed BEFORE the table code, and thus being painted outside.

I changed every echo inside the function to accumulate the results to a variable. For example, in lastLinks():

echo "<select name="links$javascript style="width:300px"><option value="" selected="selected">{$lang_advlink_link_sellink}</option>";
while (
$published $xoopsDB->fetchArray($published_array)) {
    
$url $published['url'];
    
$title $published['title'];
    echo 
"<option value="".$url."">"$title ."</option>";
}
echo 
"</select>"


to

$html "<select name="links$javascript style="width:300px"><option value="" selected="selected">{$lang_advlink_link_sellink}</option>";
while (
$published $xoopsDB->fetchArray($published_array)) {
    
$url $published['url'];
    
$title $published['title'];
    
$html .= "<option value="".$url."">"$title ."</option>";
}
$html .= "</select>"



returned the contents of $html, and now everything works OK . I can send you the changed files if you want, although it's a 5 minute thing.

I also commented the anythingthere check, no harm in having an empty combo in my case, they'll be full soon anyway ;)

About the thumbs: I thought that you could only use GD if you were in safe mode, and assumed that that was the reason why I wasn't getting the thumbs using it. Guess it's other reason. Next task for me, then
Published: 2006/7/11 6:06 • Updated: 2006/7/11 6:06
Argh!

Looks like it's not my day. I managed to fix the thumbs in my Windows installation by commenting the safe_mode comprobation for tinyedmgrthudir in xoops_version.php:

//if (ini_get('safe_mode') == true) {
    
$modversion['config'][20]['name'] = 'tinyedmgrthudir';
    
$modversion['config'][20]['title'] = '_MI_TINYEDMGRTHUDIR';
    
$modversion['config'][20]['description'] = '_MI_TINYEDMGRTHUDIRDESC';
    
$modversion['config'][20]['formtype'] = 'texbox';
    
$modversion['config'][20]['valuetype'] = 'text';
    
$modversion['config'][20]['default'] = ".thumbs";
    
$modversion['config'][20]['category'] = 'tinyed_manager';
//}


but Linux is having nothing of it, GD or magick. I only get "No Thumbnail Available" (which is better than no image as before).

Also, when I use AdvLinks to link something, in the Windows machine works perfectly, but in Linux if I post or preview the text, I lose the complete link. Weird.

I think I'm going for lunch and see if I can thing of something afterwards
Published: 2006/7/11 6:46 • Updated: 2006/7/11 6:46
I've put three schreenshots online here.

It's before pressing the "insert image".
Emidiate after pressing the "insert image".
And finaly, when all the contents of the popup has been loaded - and the popup has been resized.

I tried to disable my extensions, but found no difference.I've also tested with other firefox instalations, that does not have the same (if any) extentions installed.
There's no problem from IE.

I really appriciate you looking into it - and all the other small things you are looking into.

Regards!
Published: 2006/7/11 13:01 • Updated: 2006/7/11 13:01
@Diagoro

On my test server with XOOPS 2.0.14 the ximagemanager plugin works fine, except the Add Image function, with the browsers IE and FireFox (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4).

See for screenshot here.

Also the imanager plugin works fine.

On another test server with XOOPS 2.2.4 the Add Image option of the ximagemanager plugin works correctly.
Published: 2006/7/11 14:56 • Updated: 2006/7/11 20:30
Thank you McDonald, Saying you had no problems like mine, made me wonder if there was someting fishy with my firefox, so I decided to search for a fix to firefox.
And What did I find?
I found my problem described in the
TinyMCE Forum. Complete with a fix and all.

Fastfc wrote:
I encoutered the same trouble especially on ColorPicker popup.
I have just found the following workaround.
In resizeToInnerSize function in tiny_popup.js file,
replace
 
// Netscape 7.1 workaround
 
if (this.isWindow && tinyMCE.isNS71) {
 
window.resizeBy(010);
 return;
 }
with
 
// Gecko workaround
 
if (this.isWindow && tinyMCE.isGecko) {
 
window.resizeBy(2010);
 return;
 }
It runs well on FF 1.5Netspace 7.1 and Mozilla 1.7.2 on Win XP


I've added the fix to my setup, and it seems to work wonders.
Published: 2006/7/11 15:49 • Updated: 2006/7/11 15:49
I found a problem with emoticons, ibrowser, imanager and etc. - they don't work if XOOPS is located in a subdirectory, even if I set the subdirectory value in tinyeditor settings. Once I uploaded XOOPS in my website root all the plugins worked fine.
Emoticons works 100% (Firefox 1.5.0.4 & Internet Explorer 6)
ibrowser and imanager works 100% (Firefox 1.5.0.4 & Internet Explorer 6)
xrmanager (advanced image manager) - there are some bugs.
1. upload and browsing function - in Internet Explorer 6 it shows some javascript errors:

Line86
Char
21
Error
Expected identifier
Code
0
URL
http://www.flstudio.ru/modules/tinyeditor/xrmanager/files.php


Line86
Char
23
Error
Expected identifier
Code
0
URL
http://www.flstudio.ru/modules/tinyeditor/xrmanager/files.php


2. when I insert an image in xrmanager via IE 6 it doesn't work correctly- it minimizes the window with image description and settings.

3. the upload feature in xrmanager isn't properly working via IE 6. When I create a new folder, enter it and upload an image into it - the image is still uploading in the root directory.

All these bugs were occured when using IE 6, in Mozilla Firefox EVERYTHING is working fine!
Published: 2006/7/11 15:59 • Updated: 2006/7/11 15:59
First of all: great job this module!

I want to make it the default editor for a new site. Some modules have the option to select an editor and together with the patches this work fine.

But how can I use the TinyEditor for the Xoops-custom blocks in XOOPS 2.0.14?
Published: 2006/7/16 0:34 • Updated: 2006/7/16 0:35
First of all: Excellent module. Many thanks! Works great, on two installs, one Win one Unix, both 2.2.4. I've filed a little bug on dev.xoops. Also:

Am I missing something, or has xrmanager/connectors/php/config.php slipped out of the beta pack? It's mentioned in the Online help, I cannot find it anywhere, and I also cannot get into the xrmanager.

Then (that's a rant more than anything else, but perhaps someone has a solution): The language file for the iBrowser translates only some of the interface. Notably, the intro page seems to remain in English. That's a problem. My folks are a) not particularly computer savvy, and b) not going to be able to identify that all of that--written in a foreign language--does not matter for them. Seems to be hidden somewhere in the files, didn't find it.
Published: 2006/7/16 23:14 • Updated: 2006/7/16 23:14
Quote:
But how can I use the TinyEditor for the Xoops-custom blocks in XOOPS 2.0.14?


For this XOOPS needs to be hacked. Just wait a little while and I will supply a solution for using the editor using XOOPS-wide including a solution for the custom blocks.

Since tinyeditor is not ready for PHP to be inserted, I need to write a switch for the custom blocks, so that you can choose between DHTML and WYSIWG.
Published: 2006/7/17 0:22 • Updated: 2006/7/17 0:22
Quote:
Am I missing something, or has xrmanager/connectors/php/config.php slipped out of the beta pack? It's mentioned in the Online help, I cannot find it anywhere, and I also cannot get into the xrmanager.


Yes, the connectors have been removed and YES I have to re-write the whole documentation - I guess I have to copy and paste myself to get all the parts done.

Thx for your bug report, a patch for this weird bug - weird because this happened all of a sudden - will be released shortly on d.x.o. <- done!

Quote:
Then (that's a rant more than anything else, but perhaps someone has a solution): The language file for the iBrowser translates only some of the interface...


What is the language you want to use? Something different than English? If this is the case you have to download the langfiles for the module or for the plugins that come with the standard package.

Beside English there are lang-files for German and French.

If this is not your language you have to translate into your own language. I think I will release a package that includes all english files as a basis for translation.
Published: 2006/7/17 0:29 • Updated: 2006/7/17 0:39
Thanks for the patch! Checking it out.

*Edit* If there's no connector to the xrmanager, it should connect without it? I get the icon in the toolset, but if I drop it into one of the toolbars, it doesn't seem to be showing in the editor interface. Sorry, I hadn't read that part of the documentation. "Plugs into advlink, advimage, flash plugins."

The language thing is just in iBrowser and, I guess, iManager as well. It's just about the welcome screen, which seems to be hardcoded somewhere in files other than the little language.php. I've checked out the German translation, and it's also just the few prompts, so you should also get the Welcome Screen in English, don't you? With information on the original author and such. Fair enough, they want to leave their mark. But not only not so interesting for my people, but also a little distracting I believe. So I would actually prefer to have it at least costumizable. Didn't take the time, though, to go through the entire plugin and track it down.

Other than that, the language files are pretty straight forward, throughout your module. I've translated much of it into Spanish, but it's heavily local, down south in the Andes, so I don't think I should offer it to the public. Also, it's pretty faulty. A collection of them might help, to track all of them down.

Should the XHTML command set in Valid Elements not be pretty permissive? It seems to be throwing out pretty much all of my code, most of which should be pretty flawless and unspicious. If I leave Valid Elements blank, it seems to accept much more, but when hitting on "Edit Html", some of it nevertheless goes. Particularly form elements.

Thanks again, fantastic module
Published: 2006/7/17 10:56 • Updated: 2006/7/17 12:00
The english text of the opening screen of iManager is defined in the file imanager/imanager.php. Probably it's the same for iBrowser.

At the moment I am working on the dutch translation of tinyeditor and hope to have it finished soon. Only have the plugins to do. I will leave a message here and on the dutch support site.
Published: 2006/7/17 12:05 • Updated: 2006/7/17 12:05
Quote:
The english text of the opening screen of iManager is defined in the file imanager/imanager.php. Probably it's the same for iBrowser.


Indeed, that's where it is. In ibrowser/ibrowser.php, around line 1070. There also that "Please wait while loading..." message that didn't make it into the language file. It's in ibrowser/scripts/loadmsg.php

Thanks!
Published: 2006/7/17 15:45 • Updated: 2006/7/17 15:45
Quote:
If I leave Valid Elements blank, it seems to accept much more, but when hitting on "Edit Html", some of it nevertheless goes. Particularly form elements.


In the administration of the toolsets you can select the standard commandset. This is the same as leaving it blank, but there you can add elements. There were some discussions on the tinyMCE-forum concerning pros and cons of forms inside WYSIWYG and the developers decided that this would not be in core. BUT there is an OLD form-plugin for tinyMCE. If you give some good reasons I will maybe reanimate this plugin.

A litte sidenote for those having problems with the editor. If PHP is running with safe_mode = ON tinyeditor has some problems especially with creating new directories and copying and uploading files. This leaves me in a dilemma. Should I "castrate" the module, so that these functions are removed or should I add php_ftp-support? The last options means a complete rewrite of big parts of the module. And finally there is the question where to put the information for user, password and so on: database or flat file. Not sure which place is safer at the moment.

EDIT: Finally I decided to re-write all file-actions to ftp, since this safe_mode-plague is a NO-GO. To make this work you only have to edit one file to put the ftp-info in and write-protect it. Once rewriting is done I will release a second BETA. I hope noone is complaining now about switching to FTP?

SECOND EDIT: Aaaaaaaargh, NO I will make FTP safe_mode-dependable. I guess this would be the best solution. To make sure that everyone notices that FTP-info has to be given a warning will be issued if safe_mode is on.
Published: 2006/7/18 1:37 • Updated: 2006/7/18 4:05
Quote:
In the administration of the toolsets you can select the standard commandset. This is the same as leaving it blank, but there you can add elements. There were some discussions on the tinyMCE-forum concerning pros and cons of forms inside WYSIWYG and the developers decided that this would not be in core. BUT there is an OLD form-plugin for tinyMCE. If you give some good reasons I will maybe reanimate this plugin.
Ok, thanks. I don't know whether that's a good reason, but I basically plan to use Tiny in the article module (works great, btw) where, so to speak, associated groups of the umbrella organization my site is for can edit their information. They don't know a thing about HTML, so they need WYSIWYG. Now, since it's a very visual thing and there're lots of photos for each of the groups in a Coppermine gallery which I've bridged to Xoops, each article concludes with two form buttons, one to search for more info in other XOOPS modules, one to search for images in the gallery. I couldn't figure out a different way to send a search request to Coppermine, so it's a form element.

If I can have my form buttons pass the Tiny validation, I don't need a seperate Form plugin. I would hope it's possible to add it to the additional permitted code section and have it validate as is. I'll try it out.

The problem I'm currently having with the validation process is that my articles are ages and ages of coding which haven't ever been closely validated against any of the standards. Tiny seems to be adhering quite closely to XHTML strict, so it throws out quite a bit of what's already there. Some work to be done . Somehow, and as it is now, the validation seems a little over the top in light of the fact people can also just post their dirty code through one of the other editors in the XOOPS editor framework. But I guess that's an issue mainly for people who're deploying Tiny on a module which already contains sizable amounts of pages. Besides, it's certainly not something you would have to worry about. Perhaps just interesting for people to know that Tiny is going to parse their code for dirtiness, and will strip it quite recklessly.
Published: 2006/7/18 11:25 • Updated: 2006/7/18 11:25
Hi!

I applied the latest patches, and it seems that my problems generating the thumbs in linux are gone, don't know why.

Now it seems I only one big problem: I don't get anything in the preview area (in the image manager popup) when I select an image. What could I have done to break this?.

Also, a quick one. Our customer is one of those lazy types that would like the "please include a description" to be disabled by default. Any option in the configuration, or should I just cap it in the code?.

Thanks!
Published: 2006/7/24 6:28 • Updated: 2006/7/24 6:28
Quote:
Now it seems I only one big problem: I don't get anything in the preview area (in the image manager popup) when I select an image. What could I have done to break this?.


There could be various reasons:

a) chmod 777 missing for tinyeditor / editor / plugins / imanager / scripts / phpThumb / cache and tinyeditor / editor / plugins / imanager / temp

b) phpThumb normally tries to auto-detect the root-path for the document root, but sometimes this fails. You can "repair" this, by defining the path yourself in tinyeditor / editor / plugins / imanager / scripts / phpThumb / phpThumb.config.php

For further debugging uncomment lines 12 and 13 in tinyeditor / editor / plugins / imanager / scripts / phpThumb / phpThumb.php - don't forget to comment these lines after successful debugging.

Quote:
Also, a quick one. Our customer is one of those lazy types that would like the "please include a description" to be disabled by default. Any option in the configuration, or should I just cap it in the code?.


Sorry, this is no option. Shame on me, but I don't know YET where this is located.
Published: 2006/7/24 9:41 • Updated: 2006/7/24 9:41
Quote:
Also, a quick one. Our customer is one of those lazy types that would like the "please include a description" to be disabled by default. Any option in the configuration, or should I just cap it in the code?.


If i didn't miss the point the setting should be this one
http://tinymce.moxiecode.com/tinymce/ ... cessibility_warnings.html
Published: 2006/7/24 9:58 • Updated: 2006/7/24 9:58
Maybe I missed the point, because I thought we were talking about the plugin imanager? If not ralf57 is right.
Published: 2006/7/24 10:45 • Updated: 2006/7/24 10:45
Quote:
There could be various reasons:

a) chmod 777 missing for tinyeditor / editor / plugins / imanager / scripts / phpThumb / cache and tinyeditor / editor / plugins / imanager / temp

[...]

For further debugging uncomment lines 12 and 13 in tinyeditor / editor / plugins / imanager / scripts / phpThumb / phpThumb.php - don't forget to comment these lines after successful debugging.


Nope, I was refering to the "preview" area below "Image URL", "Description" and "Title" in the image popup. It seems I was too quick to judge. If I just focused on the next input after selecting an image, and the preview worked OK (i.e., the preview tab changes with the ¿onblur? event, can't remember the name right now). Would it be possible to paint the preview immediately after selecting the image and closing the second popup (image selector)?

Quote:
Quote:
If i didn't miss the point the setting should be this one
http://tinymce.moxiecode.com/tinymce/ ... cessibility_warnings.html

Maybe I missed the point, because I thought we were talking about the plugin imanager? If not ralf57 is right.


I was indeed talking about the image manager, but Ralf57's suggestion did the trick. Thanks!

Now, another suggestion to keep harassing both of you

How about being able to upload more than one image at a time?. Or perhaps uploading a .zip file with images that could be uncompressed and deleted in the current directory?. Our customer accesses the images directory via FTP, but he doesn't want to give that access to all collaborators, so it would be a lot less painful for them.

Thanks for the great work!
Published: 2006/7/25 5:31 • Updated: 2006/7/25 5:33
Quote:
How about being able to upload more than one image at a time?. Or perhaps uploading a .zip file with images that could be uncompressed and deleted in the current directory?


Uploading more than one image at a time, could be activated in imanager and ibrowser. Open tinyeditor / editor / plugins / ibrowserORimanager / config / config.inc.php and edit the following value:

$cfg['umax']     = 1;


I must confess I never tested this feature.

In the current BETA there is such a zip-feature implemented, but only for the plugins and their langfiles. It should be possible!! to implement this as well for imanager, ibrowser and xrmanager.

Maybe!! I will introduce this feature in the RCs or in BETA 2. Or if you want to do it yourself in the meantime you will find the zip-class in tinyeditor / class.
Published: 2006/7/25 6:01 • Updated: 2006/7/25 6:01
Tried changing it to:

$cfg['umax']     = 5;


in iBrowser, but still only allows me to upload one image.

I'll give a look to how the plugins use the zip class and see if I can make a quick patch to the xrmanager plugin (which is the only one I'm really using right now). I'll post it here if I do something decent.

Thanks!
Published: 2006/7/26 4:30 • Updated: 2006/7/26 4:30
Ok, here it is. Tell me what you think, but don't be cruel, my PHP is a bit rusty, and I still lack a better knowledge of the XOOPS classes ;)

The end of the _processFiles function in XRManager.php is now:

// if it's an image
if (preg_match("/bimageb/i"$file['type'])) {
    if (!
$this->_validateImage($file['tmp_name'], $groupid)) { return false; }
}

// if it's a zip file
if($file['type'] === 'application/zip') {
    return 
$this->_processZipFile($file['tmp_name'], $groupid$relative);
}

return 
$this->_moveImage($relative$file['tmp_name'], $file['name']);


Obviously, you need to have permission to upload zip files.

And the three helper functions needed:

/**
 * Processes zip files. The file must be an
 * uploaded file. Only images will be extracted.
 * @param string $filepath the path to the zip file
 * @param string $relative the relative path where the file
 * should be copied to.
 * @return boolean true if the file was processed successfully,
 * false otherwise
 */
function _processZipFile($filepath$groupid$relative)
{
    
// Create the zip object
    
include XOOPS_ROOT_PATH.'/modules/tinyeditor/class/pclzip.lib.php';
    
$archive = new PclZip($filepath);
    
    
// Create a temp directory to extract the files
    
$tempdir dirname($filepath).'/zip'.time().'/';

    
    
// Get the filenames from the zip file
    
$files = array();
    foreach(
$archive->listContent() as $data) { 
        if(
$data['folder'] != 1) { $files[] = $data['filename']; }
    }

    if (
$archive->extract(PCLZIP_OPT_PATH$tempdir)) {
        foreach(
$files as $filename) {
            
$f $tempdir.$filename;
            
// Copy only the images
            
if($this->image2MIME($f) && $this->_validateImage($f$groupid)) { 
                
$this->_moveImage($relative$fbasename($f));
            }
        }
    }
    
    
// Remove the temp data
    
Files::delFolder($tempdirtrue);
    
Files::delFile($filepath);
    
    return 
true;
}

/**
 * Validates an image, taking into account the user and its allowed parameters
 * @param string $imgPath the path to the image file
 * @param string $groupid the group of the file that uploaded the image
 * @return boolean true if the image validates ok
 * false otherwise
 */
function _validateImage($imgPath$groupid) {
    global 
$xoopsDB;

    
$size getimagesize($imgPath);
    if(!
is_array($size)) {
        
Files::delFile($imgPath);
        echo 
"<div style='background-color: #ff0000; padding: 5px; color: #ffffff; font-weight: bold; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12px;'>".
                
_TINYMGR_26."</div>";
        return 
false;
    } else {
        
$sql "SELECT imgwidth, imgheight FROM ".$xoopsDB->prefix('tinyeditor_toolset')." WHERE tinyed_gid = ".intval($groupid)."";
        
$result $xoopsDB->query($sql);
        list(
$imgwidth$imgheight) = $xoopsDB->fetchRow($result);    
        if ((
$size[0] > $imgwidth) || ($size[1] > $imgheight)) {
            
Files::delFile($imgPath);
            echo 
"<div style='background-color: #ff0000; padding: 5px; color: #ffffff; font-weight: bold; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12px;'>".
                
_TINYMGR_27.$size[0]."x".$size[1]."px - "._TINYMGR_28.$imgwidth."x".$imgheight."px</div>";
            return 
false;
        }
    }
    
    return 
true;
}

/**
 * Moves an image to its destination directory
 * @param string $relative the path to copy the image file to
 * @param string $from the path to the image file
 * @param string $to the name of the moved file
 * @return boolean true if the image validates ok
 * false otherwise
 */
function _moveImage($relative$from$to) {
    
$path Files::makePath($this->getBaseDir(),$relative);
    
    
$result Files::copyFile($from$path$to);

    
//no copy error
    
if(!is_int($result))
    {
        
Files::delFile($from);
        return 
true;
    }

    
//delete tmp files.
    
Files::delFile($from);
    return 
false;
}


So now, if you upload a zip file, it will unzip all images within the allowed parameters for the user (MIME types, size, etc) and ignore the rest, copy them to the current directory and delete the zip and temp folder.

Probably it can be cleaned a lot more (moving the moveImage within the image if and so on), but I just wanted to upload it quickly so you can all check for glaring errors and all that ;). Hope you like it!
Published: 2006/7/31 4:50 • Updated: 2006/7/31 4:51
BTW, I was doing some testing on our Linux server, and I noticed that when you delete a folder with files in it, it warns you that you must delete the files first, but deletes the folder anyway!.

Bug or something wrong with my config?
Published: 2006/7/31 5:19 • Updated: 2006/7/31 5:19
Hi paketep,

thx for all your work you put into this module. I will look at the code later.

Quote:
Bug or something wrong with my config?


Bug! But this is fixed for the next Beta.
Published: 2006/7/31 5:57 • Updated: 2006/7/31 5:57
Hi again!

I'm trying to modify the editor so i'll be able to put images with special borders (polaroid style, see here) if I select a concrete CSS class for the image. In that case, I add the surrounding div and reuse the align values for it.

Problem is, first that after that I can't change the div values (and also I guess that simple "align" attribs won't do it, I have to use floats or something like that).

Second, and more important: if I put that kind of HTML into the editor, the WYSIWIG result is garbled (the borders collapse and the foot text shows over the image), while the preview is correct.

Anything I can do?.

Thanks again!
Published: 2006/8/6 17:25 • Updated: 2006/8/6 17:25
Try the insertdiv plugin HERE. Unfortunately there was never a bugfree version was released for free, but most things should do.

With this plugin just mark the content you want to be div'ed and click the tool and make your settings.

If this even fails I have one desperate try: go to the toolsets, add the default commandset and change the div-part to:

div[*]


HTH
Published: 2006/8/7 0:25 • Updated: 2006/8/7 0:25
have seem tinyeditor being used to as a bbcode editor for ubbcode and punpbb

has anyone done this already for XOOPS ?

if not has anyone any pointers, clues etc so can give it a try
Published: 2006/8/10 11:33 • Updated: 2006/8/10 11:34
I doubt that there will be so much benefits using bbcode. I HAVE code for a bb-solution, but I don't want to use unless I hear some good arguments.

Unfortunately tinyeditor (tinyMCE) is not so flexible as I want it in the field of pre- and post-processing.

Why not use bbcodes for tinyeditor? I try to answer this shortly.

a) There are two sanitizing mechanisms: one is inside tiny and the other is the textsanitizer from XOOPS. This should be safe enough

b) Why should anyone fiddle with bbcodes when you are using a WYSIWYG-editor? Inside the toolsets page you can insert a reduced commandset which mimics the capabilities of the DHTML XOOPS editor (still have to write the docs on how to use it)

c) I am NOT a javascript pro <- lame excuse!

Looking forward to your (community) comments on this.
Published: 2006/8/10 12:46 • Updated: 2006/8/10 12:46
there is a bbcode wysiwyg version of Koivi editor that samuel works on it. i cant find the news now!
Published: 2006/8/11 2:06 • Updated: 2006/8/11 2:06
When I add the following code to embed a movie:
<EMBED src=../../uploads/my_movie.mp4 width=352 height=288 type=video/quicktime border="1" scale="tofit" AUTOPLAY="false" CONTROLLER="true"></EMBED>


it will be replaced with:
<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,29,0" width="undefined" height="undefined"><param name="movie" value="/modules/wiwimod/undefined" /><param name="quality" value="high" /><param name="menu" value="false" /><param name="wmode" value="" /><embed src="/modules/wiwimod/undefined" wmode="" quality="high" menu="false" pluginspage="http://www.macromedia.com/go/getflashplayer" type="application/x-shockwave-flash" width="undefined" height="undefined"></embed></object>


What am I doing wrong?
Published: 2006/8/11 12:06 • Updated: 2006/8/11 12:07
Hi Frank! Thanks again for your great work!!

There is a Problem with tiniyeditor and XOOPS 2.0.15. The Toolbars-Admin will not work:

Fatal error: Call to a member function on a non-object in /www/htdocs/w0075a3d/class/xoopsform/form.php on line 193

Can anybody help? I it possible to config the toolbars without this toolbar-editor? I need to have the imagemanager...

Thanks!
Humanoid
Published: 2006/8/31 7:21 • Updated: 2006/8/31 7:21
Hello humanoid,

Replace the file form.php with the one from XOOPS 2.0.14 and give it another try.
Published: 2006/8/31 9:05 • Updated: 2006/8/31 9:05
Dutch language files can be downloaded here.

There are 2 files available for download:
1. contains the necessary language files for tinyeditor 1.00 beta and the standard plugins that come with the package.
2. contains language files for the not standard modules.
Published: 2006/8/31 9:19 • Updated: 2006/8/31 9:19
I am using the Tinyeditor 1.0 beta on XOOPS v2.2.4 and it works fine except for when I have XOOPS installed in a subdirectory

e.g. http://www.domainname.com/subfolder/

I have ibrowser and imanager installed as plugins. When I go to insert a photo, the ibrowser window says "Error building image list!"
And I have PHP errors turned on:

"Warning [PHP]: opendir(/home/username/public_html/uploads): failed to open dir: No such file or directory in file modules/tinyeditor/editor/plugins/ibrowser/scripts/rdirs.php line 29"

The error above is somehow building the imagepath incorrectly. It should be /home/username/public_html/subfolder/uploads

In the tinyeditor editor preferences I have set the "Uploads directory" to be "/uploads" by default. If I changed that setting to be "/subfolder/uploads" then ibrowser or imanager can build the file list correctly. However the problem is then when you insert an image into the editor, it shows up with a red X because the path is set as "http://www.domainname.com/subfolder/s ... r/uploads/image.jpg"

I think Ive narrowed the problem down to how this variable - $cfg['root_dir'] - is created in
tinyeditor/editor/plugins/ibrowser/config/config.inc.php

$cfg['root_dir'] = ((@$_SERVER['DOCUMENT_ROOT'] && file_exists(@$_SERVER['DOCUMENT_ROOT'] . $_SERVER['PHP_SELF'])) ? $_SERVER['DOCUMENT_ROOT'] : str_replace(dirname(@$_SERVER['PHP_SELF']), '', str_replace('\\', '/', realpath('.'))));

This variable doesnt seem to include the subfolder where XOOPS is installed.

When I dont use tinyeditor on a XOOPS subfolder install, there are no problems with the image list.

Any help or suggestions on this would be much appreciated.
Published: 2006/9/19 17:24 • Updated: 2006/9/19 17:24
@sceilig:

a) In tinyeditor preferences type in /subfolder where subfolders are mentioned

b) There is no need for subfolder/uploads, just /uploads

c) If tinyeditor is not able to detect the root (could also apply for the thumbnail generation) just rewrite $cfg['root_dir'] = XOOPS_ROOT_PATH;

HTH
Published: 2006/9/20 1:08 • Updated: 2006/9/20 1:08
frankblack,
Thanks for the reply. You were correct - I had forgotten about that preference about the subfolder.

I would like to make my installation of tinyeditor dynamic to work wherever I install it and did set the $cfg['root_path'] = XOOPS_ROOT_PATH

That does display the directory listing of images. However, when you select an image in ibrowser, the preview window to the right doesnt display the image (path doesnt include the subfolder)
This appears to be due to a config setting with phpThumb where it creates the 'root path' itself.

This is the line I need tweaking in
tinyeditor/editor/plugins/ibrowser/scripts/phpThumb.config.php

$PHPTHUMB_CONFIG['document_root'] = realpath((getenv('DOCUMENT_ROOT') && ereg('^'.preg_quote(realpath(getenv('DOCUMENT_ROOT'))), realpath(__FILE__))) ? getenv('DOCUMENT_ROOT') : str_replace(dirname(@$_SERVER['PHP_SELF']), '', str_replace(DIRECTORY_SEPARATOR, '/', dirname(__FILE__))));

I tried setting it to be XOOPS_ROOT_PATH but it didnt understand it.

Any ideas? Also I wonder if there are other config files in some of the plugins that would get impacted by me wanting to abandon the subfolder setting in tinyeditor?
Published: 2006/9/20 13:23 • Updated: 2006/9/20 13:23
You were absolutely right about phpThumb.config.php, BUT this file does NOT know anything about XOOPS at all, so you have to type it in the "normal" way.

Just copy the value from your mainfile.php where your XOOPS_ROOT_PATH is defined and paste it into phpThumb.config.php. I will look about like this:

$PHPTHUMB_CONFIG['document_root'] = 'the/absolute/path/to/xoops/in/your/subfolder';

There is NO other place you have to touch to get ibrowser/imanager running (this is what I hope).

Oh, one thing: don't forget to write-protect phpThumb.config.php after editing.
Published: 2006/9/20 13:35 • Updated: 2006/9/20 13:35
Well I was hoping to set the phpthumb path dynamically since I was going to use tinyeditor in a multisite setup where each website would be in a different subfolder.
I wouldnt mind hacking phpthumb or ibrowser a little bit if it meant I could pass in the xoops_root_path.
Considering that you have the tinyeditor subfolder preference, surely that must be passed to phpthumb at some point - if it doesnt communicate with ibrowser or tinyeditor then I dont understand why my setting of $cfg['root_dir'] to be anything would impact phpthumb?

BTW, you did a great job on this module - it really is top notch. And thanks too for your quick turnaround on questions that I or others have had.
Published: 2006/9/20 14:51 • Updated: 2006/9/20 14:51
Quote:
then I dont understand why my setting of $cfg['root_dir'] to be anything would impact phpthumb?


Automatic detection of the root seems to be not so easy. In the end there are three or more scripts mixed up, so I was looking for an easy way to keep the scripts intact, because when there are updates to the scripts it is not easy for me to maintain them.

Anyway I was hoping that the xrmanager would replace it, but I irreversibly wrecked the code, so I have to go through a few thousand lines again, but in the end it will be worth the work.

Please note, that I will NOT rewrite ibrowser/imanager to be working in a safe_mode: on-environment - this will be exclusive for xrmanager.
Published: 2006/9/22 4:55 • Updated: 2006/9/22 4:55
frankblack,
Thanks for your recent help on the ibrowser/phpthumb settings.

I have another issue with the editor.
When I try and add Javascript or css styles to the HTML Source editor popup, it gets striped out when I return to the main editor window. When I click on the HTML Source editor button again, the javascript/css is removed.

Is there a setting that governs this, or where I could I manually hack the code to prevent this from happening.

I figured it might be in this file?
editor/themes/advanced/jscripts/source_editor.js

thanks!
Published: 2006/10/6 3:09 • Updated: 2006/10/6 3:09
How are you adding css styles to to the source editor?

Like:
<img style="blabla"... or <img class="blabla".. or <style type="text/css">img {border:none;}</style>


The last possibility won't work the others should. Or are you using one of the pre-defined command-sets from the toolsets-page? If yes you can't use this feature right now, because this is buggy.
Published: 2006/10/6 7:05 • Updated: 2006/10/6 7:05
Yes its the latter - something like
<style>.style{font-weight: bold}</style>

But Im not as concerned with the css as with the havascript. Administrators of my zoops websites like to edit their homepage content using the editor and paste in all sorts of stuff and this includes javascript. They aint skilled enough to create a separate javascript file and put their javacript in there.
The javascript could be some external hits tracking they use, or an external live chat service.

Where is tinyeditor stripping out this stuff?
Published: 2006/10/6 13:18 • Updated: 2006/10/6 13:18
I didnt see a response about how to hack tinyeditor to prevent javascript code from being stripped out from the html source window. If I could be pointed in the right direction to the code or files that I need to hack then I might be able to figure it out myself?

Another plugin I had difficulty getting working 100% is "spellchecker". I downloaded it from the dev.xoops.com website - added it as a plugin and to one of the toolsets. I enabled the spellchecker in the config.php file and defaulted it to the googlespell.

Then I had some text in tinyeditor with deliberate misspellings, clicked on the spellchecker icon, my tinyeditor would go a bit grayed out while a message said "Spellchecking please wait." At the end though it returns "No misspellings found"? I tried highlighting the text in tinyeditor and then spellchecking again but with the same result.
I also changed the default spellchecker to be TinyPspellShell as well as TinyPspell - when I used either of those and clicked the spellchecker button, it would quickly display the "Spellchecking please wait." popup and then return to the editor - nothing else happens.
I do have aspell installed and the path to it correct. I also tried adding that line to the initcode.php file (and removing it) but with no change.
---------------------------------------------------
echo 'spellchecker_languages : "+English=en",';
---------------------------------------------------

What might I be doing wrong. It would be great to get the external GoogleSpell working.
Published: 2006/10/12 18:36 • Updated: 2006/10/12 18:36
Xoops 2.0.15.
Tinyeditor 1.0 beta
News 1.44

Installation was successful. News files changed successful.

Some qusetions:

1. In tinyeditor Admin area I try to setting up the toolbars but after choosing Group-list and press "Go" nothing happanes!?

I need to include some options to my editor but I can't access to toolsets.

2. Why imanager and ibrowser not included by default in plugins folder? I'm not shure if I'm "install" them properly. I was download them from Plugins for TinyEditor 1.x (link), unzip and upload by ftp into plugin directory. Is that enough?

Thanks for answers
igor
Published: 2006/10/30 6:04 • Updated: 2006/10/30 6:04