Andrew, et al:

I used the following procedure ..........

Adding User-specific Preferences

The following steps outline the process to add a user-specific preference.

1. Select Edit - Preferences - Configs.

2. Select the tab labeled Prefs. Add your preference and setting to this file. Settings follow one of the following formats:

Preference
user_pref("Preference Name","string value");
user_pref("Preference Name", numerical value);
user_pref("Preference Name", boolean value);

3. Click on OK to save your change.

4. Start K-Meleon. The preferences that added or modified should now be reflected in K-Meleon

.......... but in the process made a typing error for an entry -- now I cannot delete it -- after I attempt to do so and click OK it is still there.

Help!

JP

right now, the prefs.js file sometimes doesn't save properly from the preferences dialog... you might need to open it in notepad, make the changes, then save it... do this while k-meleon is NOT open.

--- po

JP,

Sorry about that. Yes, the prefs are acting a bit wacky right now. If you are using the loader, exit all the way out. If you are not using the loader and still having the problem, do as Po suggests and open up prefs.js in Notepad and make the edits you need to do.

Andrew

Thanks for the quick response gentlemen

Which folder do I find prefs.js in?

The Mozilla user Prefs in the Profiles/Prefs folder do not look anything like the ones I see from the K-Meleon drop-down menu (Edit/Preferences/Config).

Thanks

JP

the prefs.js file you want to edit will be in the user profile folder, the path to which is something like:

C:\Program Files\K-Meleon\Profiles\default\XXXXXXXX.slt

where 'XXXXXXXXX' will be a random string of characters.

DON'T edit the prefs.js file in

C:\Program Files\K-Meleon\defaults\profile

since this one is used to generate a new user profile... i'm sorry, i probably should have made that distinction in my earlier post.

--- po

Thanks, Po

That did it -- worked great -- now if only I could get my visited links (history) color function to work! :-(

I do believe I did everything by the letter per instructions, but unfortunately -- no go!

Many thanks for the help, though -- Po & Andrew.

JP

JP,

Post the pref that you added for the visited links.

Andrew

Andrew:

Here 'tis:

user_pref("browser.visited_color", "#990099");

JP

JP,

Did you follow the steps on this page?

http://tln.lib.mi.us/~amutch/pro/kmeleon/khistfiles.htm

Andrew

Andrew:

Yup! -- twice.

JP

JP,

What pages are you testing it on? It won't show links visited if the page uses a stylesheet to override the preference. Check it at Yahoo as I know it works there.

Andrew

Andrew:

Ah, that must be it!

Check the following (one of my) page ..........

http://www.brazilcacticult.org/wf.htm

.......... as you can see, I do use CSS 2 etc.

Pity -- my visitors use visited link differentation extensively when browsing the Photo Galleries (five, encompassing 1200 images) of my Brazilian Cacti site in order to keep track of their viewing session.

Many thanks anyway, Andrew.

JP

well, if i understand you correctly, you would rather have the default 'visited link' color specified in the browser preferences show up when viewing your page? if that's the case, you just have to NOT specify a color for that element in your CSS... when i visit the page you refer to, the visited links show up as magenta, so you must have that specified somewhere... or maybe i'm confused about the issue at hand.

--- po

Well, I'll be danged, Po -- they are SUPPOSED to be magenta!

What am I doing wrong with my K-meleon configuration for me not to be able to obtain the samet result as you?

JP

it's hard to say what might be wrong... the history function that the visited links color depends on is kinda touch-and-go right now... check for the presence of a 'history.dat' file in the same folder as your prefs.js file... if it's not there, the files (particularly appcomps.dll) on the page andrew mentioned above didn't get recognized correctly. if it's been several days since you downloaded them, you might want to delete the ones you have and get the newest versions... that seems to be making it work for most people.

Did that .......... didn't work :-(

JP,

Did you find the history.dat file that Po mentioned?

Andrew

Andrew:

Did not find it.

JP

JP,

OK, that's the problem right there. With no history.dat file, the visited links can't be recorded. That means that your appcomps.dll file isn't being registered. It's easy to check that. Go to an FTP site and if you can't view the site and instead get prompted for a download, appcomps.dll isn't registered.

To get it registered, you may have to delete additional files. Try this:

Close K-Meleon
Delete component.reg, in the components directory, the tro .DAT files, in chrome, all of the .rdf files. Now, restart K-Meleon and test everything again.

Let me know how that goes.

Andrew

Andrew:

On restart component.reg and .rdf files were rebuilt -- but still no history.dat file

JP