By Luca-dupe on

I do not know if I'm in the right thread, if not I beg your pardon.

Dear ladies and gentlemen,
I've a problem to get the FCK module running.
Point of departure: 1.) Module FCK is enabled. 2. Two (three) roles (anonymous, authenticated, (and implicitely admin)) in roles: authenticated user all facilities (access, administer, upload) anabled. 3.) Edit FCKeditor profile: Here, I fear I've changed this and did not save the default settings. I hoped it would work. However, FCK-Editor does not run. :-(
What I've done wrong? What could be done?
Best regards

Luca, Leipzig, GE

⋅ Categories: Drupal 6.x

Comments

echopx’s picture

echopx commented

If you feel you have made a wrong move, disable the module. Follow it up with a uninstall (if applicable). Go back to your module page and enable it again. All the default settings should get set again.

Luca-dupe’s picture

Luca-dupe commented

Thank you, Sir.
Best regards
Luca

wmike’s picture

wmike commented

I have a number of Drupal sites - all frequently have difficulties with FCK - my current site had FCK working - no problem. Nothing has been installed or changed - no longer works. Despite uninstalls, reinstalls etc.

Actively looking to move away from Drupal - breaks far too often - pity.

domineaux’s picture

domineaux commented

Actively looking to move away from Drupal - breaks far too often - pity.

I'm curious what you're going to use that is better?

I changed things abit over time to compensate for problems I had like you mentioned:

Use filtered html as editor for authenticated users postings.

HTML editor for admin to copy and paste into site

CCK for any embeds for the most part

The CCK, VIEWS, taxonomy make this the best CMS, IMO.

Problems are negligible with those tools.

We all find problems with other modules on occasion.

I have found it is best to use only those modules you carefully study before applying to your sites.

I recently built an Ubercart site. The taxonomy was critical to this site, yet the SSL has been a problem from what I read.

The solution, use only PAYPAL or other payment system that is secure and returns buyer information to my site.

What I'm saying is there are always workarounds, if you just apply some commonsense to your solutions.

It is hard to get just what you want in a module that addresses most of your need, but not all of it.

I try never to code in any modules.

Module updates come out daily and the cross-connectivity with Drupal and other modules can cause "REAL ISSUES".

If you don't think so read the issues with module releases.

Lots of problems can be created that you aren't aware of when you start coding.

One thing that will help. Don't install modules until you have read the issues on the project.

If the developer isn't fixing things you can pretty well expect problems.

The way I look at is this. If the developer isn't or can't fix it, I remind myself that developer already has the best understanding of what he was doing. The developer took the time and effort to build the module.

Many of the modules are beta, alpha RC etc. That pretty well means they may or may not be OK on a production site.

Module problems may not show up for months, and then they can take days to locate and fix.

You may not get super support from these forums, but usually you can get good responses from module and theme developers.

Reading the issues can also answer and lot of questions. Then of course you can always Google for help.