Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
But it can be activated, when the visibilty of the TinyMCE Modul is adjusted.
I see it for the PostText textarea. But the HTML Code isn't displayed correctly.
Are you stripping HTML Text or something like that?
The problem seems to be the filter_xss().
TinyMCE works for the field. The data is saved correctly in the database.
If you disable all filters in uieforum_filter it works. But that can't be a solution.
I then added a field to the administrative form for UIEForum, that sets a variable uieforum_use_tinymce and tried to exclude the check_plain filter. That didn't work so i tried to disable filter_xss() and that worked. But that can't be a solution either.
The question is, why does this filter remove every tag. Even if it's an allowed tag.
But that's another story and not a UIEForum problem. Or did i miss something?
Yeah I'm aware of what's causing the problems, and they all filter down to the fact that I'm not using the node system.
I'll have to find a way around this particular problem though :)
Just change the name of the variable (This variable is only to switch of check_plain() ) or leave it away and comment out check_plain().
Install the Editor Module you want for drupal, make it available for the forum, and set the allowed HTML Tags in the new Text field.
It doesn't depend on tinyMCE. In fact, another editor isn't needed at all.
The textfield for allowed HTML stands for itself. It just tells filter_xss() wich HTML tags are allowed, and wich are not. No matter how they've been entered in the textfield.
The Editor only adds the possibility, to add the tags automaticly and in a nice WYISWYIG-Style.
any updates on this issue? We've just installed UIEForum in the hopes that it will provide some better access control, but one of the things people are used to is the TinyMCE editor, so it's kind of a dealbreaker.
Are there any plans to submit a formal patch using the combined code above or is the author planning on a different approach?
I tried it and it kind of works.... For some reason the "Enable TinyMCE" checkbox doesn't want to remain checked. When I go in and check it and then leave it TinyMCE works; however, when I go back to check the option it is unchecked and TinyMCE doesn't work anymore (and all my text is converted in plain_text).
Also, I am only able to use the BBCode that was originally installed with this forum (i.e., bold, italic, link, left, right, center). I can't use other TinyMCE options because it won't let me (just shows as plaintext).
Could someone offer some help, please? Perhaps the above code is flawed? I don't know enough to say if that is the case.
LasseP - thanks for your code suggestion. I don't know what the hell was going through my mind before, but its actually not a bad solution at all at all. Sorry about that!
I'll have a gander at the code when I get home and look into adding this solution to the real code-base
Cronin - so long as you applied the original suggested code, along with the updated bug-fix it looks like it should work!
Hi, in the latest version TinyMCE does work. Perhaps, this is because you've switched to using drupal theme() function and drupal form mecahnis.
UUUPS... I forgot that I have hacked the code so as it uses the standard Drupal filter functions.
I have done the following. Please, note, that this disables BB code. A couple of nuances:
1) it enables the default format
2) however, you should manually check all filters on the settings page that are used in the default format. this could be hacked better, but I am lazy to fix it properly (good enough for me now)
Hi,
And how about using the node system in the next release. The Drupal nodesystem has so much advantages :)
Subscribing..still not knowing which forum system to choose. Working myself on nodeforum, but it needs more functionality then the regular Drupal forum system.
Yeah I'm tempted to move over to nodes in this release too - believe me.
I've literally only just finished an absolutely massive code overhaul to use drupal's form api to its full extent, but I'm wondering if it would be easier to start from scratch again :)
I made a seperate issue on this node-system integration: http://drupal.org/node/236679
I am trying to get nodeforum working, which is as uieforum a seperate forum solution as replacement of the forum module.
The good thing is, it has fully node-system integration.
The bad thing is, it is not on drupal projects yet. I found it on cvs and somebody referred to it, because nodecomment and nodeforum are integrated solutions :)
At first, i thought having everything in nodes would be fine.
But you have to think about if you want a complete different solution or a solution the drupal-way.
zoro: i appreciate your work, but maybe you should take a look at "advanced forum".
There is still a lot of work to do, and maybe you can enhance the development process with your experience from your own development on UIEForum.
Hi Lasse,
Yes node and comments are two different things, but when you use the nodecomment an nodeforum module (and enhance them), then you have best of both!! Comments as nodes and forumtopics as nodes!
This version of UIE Forum is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.
Comments
Comment #1
daniel.hunt commentedYou're not blind - nope, you can't use anything other than the default entry fields that come with UIEForum :)
In order to use TinyMCE the module will have to be ported over to use the node system for data storage, whereas at the moment its completely separate
Comment #2
LasseP commentedAh, ok.
But it can be activated, when the visibilty of the TinyMCE Modul is adjusted.
I see it for the PostText textarea. But the HTML Code isn't displayed correctly.
Are you stripping HTML Text or something like that?
Comment #3
daniel.hunt commentedThe UIEForum module uses its own input text handler - it parses its own text its own way :)
It's completely separate at the moment I'm afraid :(
Comment #4
LasseP commentedThe problem seems to be the filter_xss().
TinyMCE works for the field. The data is saved correctly in the database.
If you disable all filters in uieforum_filter it works. But that can't be a solution.
I then added a field to the administrative form for UIEForum, that sets a variable uieforum_use_tinymce and tried to exclude the check_plain filter. That didn't work so i tried to disable filter_xss() and that worked. But that can't be a solution either.
The question is, why does this filter remove every tag. Even if it's an allowed tag.
But that's another story and not a UIEForum problem. Or did i miss something?
Comment #5
daniel.hunt commentedYeah I'm aware of what's causing the problems, and they all filter down to the fact that I'm not using the node system.
I'll have to find a way around this particular problem though :)
Comment #6
LasseP commentedOk, I found a solution that fits my needs (just for testing purpose ;) )
I did the following:
uieforum.module
I added 2 form elements
And changed this line:
$text = filter_xss($text);to
$text = filter_xss($text, explode(", ", variable_get('uieforum_allowHTML', 'a, em, strong, cite, code, ul, ol, li, dl, dt, dd, u, i')));Now i can edit the allowed HTML tags in the forum configuration so that all of the possible tinyMCE tags that are allowed are displayed in the forum.
It works for me. Maybe for a few other too.
Comment #7
LasseP commentedOh, sorry. Forgot a line.
Also comment out:
$text = check_plain($text);or check if tinyMCE is enabled like I do
Comment #8
daniel.hunt commentedNice fix - but its completely specific to TinyMCE - what about any of the other editors out there? ;)
Comment #9
LasseP commentedNo it isn't.
Just change the name of the variable (This variable is only to switch of check_plain() ) or leave it away and comment out check_plain().
Install the Editor Module you want for drupal, make it available for the forum, and set the allowed HTML Tags in the new Text field.
It doesn't depend on tinyMCE. In fact, another editor isn't needed at all.
The textfield for allowed HTML stands for itself. It just tells filter_xss() wich HTML tags are allowed, and wich are not. No matter how they've been entered in the textfield.
The Editor only adds the possibility, to add the tags automaticly and in a nice WYISWYIG-Style.
Comment #10
Zizan commentedFirst - thanks for writing such an excellent forum module
Second - thanks for posting this modification to allow TinyMCE to be used
I did uncover one issue with this solution - on the modification
the variable_get function was throwing errors for me since it requires a second argument, $default. I edited mine to say:
to default the TinyMCE support to off if no value for that variable is set. Hope this helps someone.
Comment #11
btully commentedany updates on this issue? We've just installed UIEForum in the hopes that it will provide some better access control, but one of the things people are used to is the TinyMCE editor, so it's kind of a dealbreaker.
Are there any plans to submit a formal patch using the combined code above or is the author planning on a different approach?
Thanks!
brian
Comment #12
palmergroup commenteddouble post, sorry.
Comment #13
palmergroup commentedI tried it and it kind of works.... For some reason the "Enable TinyMCE" checkbox doesn't want to remain checked. When I go in and check it and then leave it TinyMCE works; however, when I go back to check the option it is unchecked and TinyMCE doesn't work anymore (and all my text is converted in plain_text).
Also, I am only able to use the BBCode that was originally installed with this forum (i.e., bold, italic, link, left, right, center). I can't use other TinyMCE options because it won't let me (just shows as plaintext).
Could someone offer some help, please? Perhaps the above code is flawed? I don't know enough to say if that is the case.
Comment #14
daniel.hunt commentedWell, this sort of fell by the wayside ....
LasseP - thanks for your code suggestion. I don't know what the hell was going through my mind before, but its actually not a bad solution at all at all. Sorry about that!
I'll have a gander at the code when I get home and look into adding this solution to the real code-base
Cronin - so long as you applied the original suggested code, along with the updated bug-fix it looks like it should work!
Comment #15
jdeg commentedI think the textarea is ok without TinyMCE but the javascript popup doesn't looks friendly.
Banana Tools
Comment #16
itman commentedHi, in the latest version TinyMCE does work. Perhaps, this is because you've switched to using drupal theme() function and drupal form mecahnis.
UUUPS... I forgot that I have hacked the code so as it uses the standard Drupal filter functions.
Comment #17
daniel.hunt commentedWhat did you "hack"? It may be useful for others to know!
Comment #18
itman commentedI have done the following. Please, note, that this disables BB code. A couple of nuances:
1) it enables the default format
2) however, you should manually check all filters on the settings page that are used in the default format. this could be hacked better, but I am lazy to fix it properly (good enough for me now)
Comment #19
daniel.hunt commentedIt be helpful to know that I'm rewriting how the module uses the form api, so that it uses it correctly :)
Hopefully this won't be a problem with the next release!
Comment #20
summit commentedHi,
And how about using the node system in the next release. The Drupal nodesystem has so much advantages :)
Subscribing..still not knowing which forum system to choose. Working myself on nodeforum, but it needs more functionality then the regular Drupal forum system.
greetings,
Martijn
Comment #21
daniel.hunt commentedYeah I'm tempted to move over to nodes in this release too - believe me.
I've literally only just finished an absolutely massive code overhaul to use drupal's form api to its full extent, but I'm wondering if it would be easier to start from scratch again :)
Comment #22
summit commentedHi zoro,
I made a seperate issue on this node-system integration: http://drupal.org/node/236679
I am trying to get nodeforum working, which is as uieforum a seperate forum solution as replacement of the forum module.
The good thing is, it has fully node-system integration.
The bad thing is, it is not on drupal projects yet. I found it on cvs and somebody referred to it, because nodecomment and nodeforum are integrated solutions :)
greetings,
Martijn
Comment #23
LasseP commentedNode and comments are two different things.
At first, i thought having everything in nodes would be fine.
But you have to think about if you want a complete different solution or a solution the drupal-way.
zoro: i appreciate your work, but maybe you should take a look at "advanced forum".
There is still a lot of work to do, and maybe you can enhance the development process with your experience from your own development on UIEForum.
Comment #24
summit commentedHi Lasse,
Yes node and comments are two different things, but when you use the nodecomment an nodeforum module (and enhance them), then you have best of both!! Comments as nodes and forumtopics as nodes!
greetings,
Martijn
Comment #25
daniel.hunt commentedPostponing this, as it has to do with the eventual move over to nodes for this module
Daniel
Comment #26
pomliane commentedThis version of UIE Forum is not supported anymore. The issue is closed for this reason.
Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.
This issue has been automagically closed by a script.