XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk


« 1 ... 8 9 10 (11) 12 13 14 »


101
maxima
Re: Big Firefox problem!!

  • 2006/9/1 16:09

  • maxima

  • Not too shy to talk

  • Posts: 152

  • Since: 2006/3/4 4


Quote:
Wait till you have to do serious CSS based development
Are you saying that my CSS file is a joke? You might have missed the first message I post which stated that FF displayed fine until yesterday and no changes were made to the CSS to make it a 'bad' CSS. Anyway... it works fine now.
Topic | Forum


102
maxima
Re: Experimental WYSIWYG implementation problems v2.0.15

  • 2006/9/1 3:45

  • maxima

  • Not too shy to talk

  • Posts: 152

  • Since: 2006/3/4 4


That finally worked McDonald, thanks. A note should be made about this. I guess later I might run into problems since I've switched to an earlier file. Right now I'm just happy to have a WYSIWYG editor :)

The image upload tool still does not display though. I put in all the plugins I found and none has that. However I am able to get files from the ImageManager. If you find out where that plugin is (the one you placed the example link) then please let me know.

Thanks again!
Topic | Forum


103
maxima
Re: Big Firefox problem!!

  • 2006/9/1 2:46

  • maxima

  • Not too shy to talk

  • Posts: 152

  • Since: 2006/3/4 4


I've managed to fix the CSS by re-writing the entire thing. Evidently it was corrupt though IE could read it. Makes you wonder why FireFox users beatup on IE when it (FF) can't interpret a file which visually appears perfect.

It looks the same now that I have re-written it and now FF obeys. Has anyone had this problem? What causes this?
Topic | Forum


104
maxima
Big Firefox problem!!

  • 2006/8/31 23:52

  • maxima

  • Not too shy to talk

  • Posts: 152

  • Since: 2006/3/4 4


Sometimes FireFox is a really dumb browser!

All was well and then today FireFox is not reading all of the CSS file. It won't display styles forl;

blockTitle
blockContent
#mainmenu
#usermenu
ul
li
item
odd
even
outer

yet it displays styles for;
body
td
a
a:hover

Does anyone know what causes this? It was working before and still works in IE. I don't know what it's doing in Safari but I am now concerned.
Topic | Forum


105
maxima
Re: Experimental WYSIWYG implementation problems v2.0.15

  • 2006/8/31 23:00

  • maxima

  • Not too shy to talk

  • Posts: 152

  • Since: 2006/3/4 4


Talk about frustrating!! I have spent so many hours on this and still nothing!!

I have installed every patch and every plugin and pretty much everthing available for TinyEditor and still can't get the #OOPS# image manager to display!

The patch for imanager, ibrowser says it fixes a bug that creates 'weird' directories in uploads.
Quote:
This patch fixes a bug within ibrowser, imanager and xrmanager which generated weird user-directories. If there are already those weird directories in your uploads directory, simply delete them. These directories will be created anew if you use the plugins.

I am not getting 'weird' directories. I just don't see anything when I try to use toolset. I see nothing to enable or disable plugins.

Does this have to do with my version of PHP (4.3)?

Do I need to run XOOPS 2.2.4 to be able to use this?
Am I the only one having this problem?
Topic | Forum


106
maxima
Re: Experimental WYSIWYG implementation problems v2.0.15

  • 2006/8/31 21:08

  • maxima

  • Not too shy to talk

  • Posts: 152

  • Since: 2006/3/4 4


McDonald thanks for the guide, however, I just spent 3hrs trying to get the plugins to do something and it's just not happening.

I have uploaded the imanager to tinyeditor/editor/plugins and I still don't see any connections to the XOOPS image manager nor do I see an upload button. I don't see anything like the demo you linked. I don't see any button to enable it.

When I try to execute the Toolsets during configuration nothing happens. For the Inbetween editor I see a list of plugins that I can choose from and when I click the toolset I see an array of check boxes but nothing of that for tinyeditor. What's wrong with this? Are you using XOOPS 2.0.15?
Topic | Forum


107
maxima
Re: Experimental WYSIWYG implementation problems v2.0.15

  • 2006/8/31 17:58

  • maxima

  • Not too shy to talk

  • Posts: 152

  • Since: 2006/3/4 4


Ok. It seems to work only with the TinyEditor 1.00beta but I have been using Spaw with News1.44 so I figured it was compatible with Xoops. Likewise FCK editor and Koivi works with NewBB2.02. So the line in the Readme file is invalid?
Quote:
To enable it:
- Edit the file class/xoopsform/formdhtmltextarea.php
- Change the "htmlEditor" line, specifying the location of the editor you want to use.

I prefer Spaw to TinyEditor for it's ability to visually display the images in the uploads folder and also supports image upload. Is there a plugin for TinyEditor to support image upload?
Topic | Forum


108
maxima
Re: Experimental WYSIWYG implementation problems v2.0.15

  • 2006/8/31 14:38

  • maxima

  • Not too shy to talk

  • Posts: 152

  • Since: 2006/3/4 4


Still seeking help on this issue
Topic | Forum


109
maxima
Re: Experimental WYSIWYG implementation problems v2.0.15

  • 2006/8/30 15:35

  • maxima

  • Not too shy to talk

  • Posts: 152

  • Since: 2006/3/4 4


So is there anything I can do to get this to work??
Topic | Forum


110
maxima
Experimental WYSIWYG implementation problems v2.0.15

  • 2006/8/30 0:41

  • maxima

  • Not too shy to talk

  • Posts: 152

  • Since: 2006/3/4 4


I have followed the instructions of the readme in the latest release which has an 'experimental WYSIWYG', and yet nothing happens.
Quote:
Experimental WYSIWYG support

This version contains an experimental patch that allows the use of 3rd party WYSIWYG editors to replace the old
"DHTML" one. Due to a lack of extended testing, this functionality has been disabled by default and requires that
you modify one file manually to configure it.

To enable it:
- Edit the file class/xoopsform/formdhtmltextarea.php
- Change the "htmlEditor" line, specifying the location of the editor you want to use.
An example would be: var $htmlEditor = array( 'XoopsFormTinyeditorTextArea', '/class/xoopseditor/tinyeditor/formtinyeditortextarea.php' );

To disable it:
- Change the "htmlEditor" line back to its default value:
var $htmlEditor = array();

There must be something missing from this instruction! I uploaded Spaw, FCKEditor and TinyMCE and pointed to their executable file and I still see the DHTML editor. This is what I have:
Quote:
var $htmlEditor = array('XoopsFormSpawTextArea', '/class/spaw/formspaw.php');

I also see this in the file to be edited:

Quote:
* array( 'className', 'classPath' ): To create an instance of "className", declared in the file XOOPS_ROOT_PATH . $classPath

Where do I create the className?
What else is required to make this work?
Topic | Forum



TopTop
« 1 ... 8 9 10 (11) 12 13 14 »



[Advanced Search]

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Oct 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!