WYSIWYG Editor
  • RickRick
    Hello,

    Firstly - great app. It's running wonderfully on our server. Apologies if I am missing something really basic though - how do I install/enable a WYSIWYG editor for articles/pages?

    I'm ok doing it in HTML, but some of the other people who will be able to edit pages are not familiar with HTML. Also - with the tags I'm using it doesn't seem work so well in different browsers (no bold in firefox for example).

    I'm sure I've read you can use WYSIWYG - just not sure how to!

    Rick.
  • AlexCAlexC
    Hey there,

    The editor should be enabled by default. Are you just getting a standard textarea instead? Do you have a url that I can view, or are you getting any JavaScript errors?

    2.5.1 which will be released on Tuesday upgrades to the latest version of the editor we use, so that may also did the issue. But a url with access to add a page would be good for me to debug. Pm me details if you want to so that.

    Regards
  • RickRick
    Hi Alex,

    I've PMed you :-)

    Rick.
  • AlexCAlexC
    Thanks,

    I see what the issue is, I've reported it as bug #241. I will attempt to fix it for 2.5.1, but as I was hoping to release today I am not entirely sure. For a workaround, have you tried the guide on http://manual.tangocms.org/troubleshooting/sef-urls to enable SEF URLs?

    Btw, you can delete the user you created for me now :)

    Regards,
  • RickRick
    Thanks Alex - much appreciated. I can wait for the bugfix or attempt to sort it!

    This is the documentation that my host offers regarding mod_rewrite;

    http://www.streamlinesupport.net/index.php?page=show&id=130

    It makes no sense to me whatsoever! :geek:

    Rick.
  • AlexCAlexC
    We already prepare the rewrite rules needed, and they are in the provided '.htaccess' file in the archive you downloaded. Now, it may be a simple case of you didn't upload that file (it is a hidden file in majority of operating systems). The manual should explain this. Can you double check you have the file '.htaccess' uploaded to your webserver? It will be in the same location as 'index.php'.
  • RickRick
    Hi Alex,

    It's definitely there. Not to worry - will wait for the fix =)

    Ta.
    Rick.
  • AlexCAlexC
    Hi Rick,

    Just to let you know, I tried working on this issue on Tuesday but it's quite tricky to solve right now. I'm home over the next few days so I can try and work something out, and then release 2.5.1 with the fix.
  • RickRick
    Hi Alex,

    That's great - thanks for your efforts. I have tried again to enable Sef -- but with no joy. I have contacted my host again with the troubleshooting page you supplied.

    Thanks for your help! =)

    Rick.
  • RickRick
    My web host advised me that it should now work. It doesn't.

    However, I now get a Internal Server 500 error if the .htaccess file is present. If I remove the .htaccess file via FTP - I don't get the error and everything works as normal.

    I'm confused :?

    Edit: the site isn't running in a subdirectory (as noted in .htaccess)

    Rick.
  • baggachipzbaggachipz
    I've gotten the WYSIWYG editor showing up, thanks for pointing out that .htaccess needs to be present. A couple things to note:
    My site is being hosted on GoDaddy (not my choice) and they run Apache 1.3. A consequence of that is that I had to comment out the line in .htaccess:
    RedirectMatch 403 (?:/application/logs(?:/.*?\.log)?|/tmp/cache/.*?|/config/.*?/(?:layouts/.*\.xml|config\.ini\.php)|/application/modules/.*?/install\.(?:xml|sql)|/assets/uploads/media/.*?)(?:/|$)

    because when that line is present, it results in a 500 error. I don't have the time right now to figure out why.

    I know this presents a big security hole but for now I'm not going to worry too much about it as I see there are empty index.html files in all of the "forbidden" directories.

    Also, I do see that currently the default "add an image" piece of TinyMCE is in use, which makes it tough to utilize the uploaded assets unless one knows what they're doing with urls and such. Is there a plan to have a custom plugin that integrates well with the media controller?

    Thanks!
  • AlexCAlexC
    Apache 1.3 is not supported since it doesn't use PCRE, which that regex uses. You can comment it out, it should be ok.

    Yeah we hopefully plan to have an image uploader in the editor used. I don't like the official one you can get for TinyMCE, so if we stick with TinyMCE (we may be moving to CKEditor 3) then I shall make a custom plugin for it.
  • AlexCAlexC
    Just to let you know, I've fixed bug #241 and I should be able to release 2.5.1 tomorrow morning. Had to patch TinyMCE to fix this, which has been sent upstream to them to accept.
  • RickRick
    Wonderful news Alex, thank you =)

    Rick.
  • AlexCAlexC
    2.5.1 released, this will fix your issue. Let me know if the upgrade goes ok :)
  • RickRick
    http://img694.imageshack.us/img694/5922/syscg.th.jpg
    Went up fine =)

    But more importantly.....
    http://img185.imageshack.us/img185/8037/wysiwyg.th.jpg

    Cheers for the prompt fix =)

    Rick.
  • AlexCAlexC
    Yep, they use Apache 1.3 which really should never be used in a production environment any more - and it doesn't support the regex we use in the .htaccess file. As stated on http://tangocms.org/requirements if using Apache you need version >= 2. You can simply remove the entire bottom section (starting with mod_alias) and that should fix it.

    Glad the editor is now working though :) Upgraded OK I see
  • RickRick
    Yeah, I had to comment the .htaccess thing out!

    Rick.
Add a Comment

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Apply for Membership

Categories

In this Discussion