Bugs :  K-Meleon Forum
You can talk about issues with k-meleon here.  
search engine bug
Posted by: martinw2
Date: May 25, 2014 06:00PM

I am not sure what is causing this problem. When I try to add a different seach engine in the preferences 'web search' page, a box appears but it will not let me type anything in it. Same happens if i go to the 'search engines' tab, it refuses to add anything. Just using the latest V74.B3. Not sure if it is something to do with a macro.

OK, after a lot of messing around trying different things I found that the reason the search engines were missing was because the K-Melon main program was taking its seach engine settings from the folder in 'documents and settings\....name...\application data\k-melon. I then took the search.xml from the main program folder and copied it in there and now all the search engines show again. You still can't add a new one using the last tab though.

Martin



Edited 1 time(s). Last edit at 05/25/2014 07:59PM by martinw2.

Options: ReplyQuote
Re: search engine bug
Posted by: SoerenB
Date: May 26, 2014 10:03PM

Hi, Martin,

just trying - did you happen to transport that .xml via cdrom at any time during the process? That would have made it writeOnly even after copying to and fro.
You should be able to correct that in the "Properties" of the file.
If not: close k-m, move (!) the file to your desktop,
start k-m (creating a new file, now ReadWrite, hopefully),
close k-m.
Now just replace the contents (!) of the new file
with those of the old one.

PS: concerning the whereabouts of your profile:

a) an existing profile.ini (empty file) makes that the "profiles"
folder inside the program install folder is used (portable install)
- issues concerning writing rights may arise.
b) the file "profiles.ini" (plural!) inside the "profiles"
folder holds info about your profiles. You can edit that.
(k-m closed, of course). How-tos can be found in this forum,
or mozillas, firefox' ...

Cheers
SoerenB

KM 1.74b4u1 in Wine 1.6 on Linux Mint 17 (XFCE)
- and still being surprised every day
how easily all of this works ...



Edited 1 time(s). Last edit at 05/26/2014 10:21PM by SoerenB.

Options: ReplyQuote
Re: search engine bug
Posted by: guenter
Date: May 27, 2014 02:18AM

Quote
martinw2
I am not sure what is causing this problem. When I try to add a different seach engine in the preferences 'web search' page, a box appears but it will not let me type anything in it. Same happens if i go to the 'search engines' tab, it refuses to add anything. Just using the latest V74.B3. Not sure if it is something to do with a macro.

OK, after a lot of messing around trying different things I found that the reason the search engines were missing was because the K-Melon main program was taking its seach engine settings from the folder in 'documents and settings\....name...\application data\k-melon. I then took the search.xml from the main program folder and copied it in there and now all the search engines show again. You still can't add a new one using the last tab though.

Martin



1.) Means that You had a corupted search.xml in the profile. When You replaced it by a default one it was ok again.

2.) That You still cannot write the file indicates a new problem.

Look into error console and check whether it throws an error.

Also I attached my search.xml. I just tested that it can be written with my 74.

It is German but should be good enough to test on any new km.

BTW. There was a problem so code for writting search.xml was changed.
But now it should write search files that are healthy.

p.s. Hallo Soeren. Schön, dass du da bist.



Edited 1 time(s). Last edit at 05/27/2014 02:20AM by guenter.

Attachments: search.xml (14.2 KB)  
Options: ReplyQuote
Re: search engine bug
Posted by: martinw2
Date: May 28, 2014 05:15PM

Thank you for the advice. It seems the search.xml is now working fine. However, the last tab where you can add a search URL is still not working. I guess this is a separate issue. As to the error consol, yes there are several errors in that and below are the regular ones.
--------------------------
While creating services from category 'profile-after-change', could not create service for entry 'Disk Space Watcher Service', contract ID '@mozilla.org/toolkit/disk-space-watcher;1'

Wed May 28 2014 11:11:12
Warning: Unknown property '-moz-outline-offset'. Declaration dropped.
Source file: chrome://console2/skin/c2version.css
Line: 14, Column: 20
Source code:
-moz-outline-offset: -2px;

Wed May 28 2014 11:10:48
Warning: Use of getPreventDefault() is deprecated. Use defaultPrevented instead.
Source file: chrome://flashblock/content/flashblock.xml
Line: 429

Options: ReplyQuote
Re: search engine bug
Posted by: martinw2
Date: May 28, 2014 06:07PM

Problem solved.

A total unistal including all profiles in 'docs & settings'. I suspect the unistal did not remove that profile when removing the old version. Now I can even add search engines in the last tab. I did though have to add the new search.xml to the docs/settings profile file. That may help others with the same glitch.

Martin

Options: ReplyQuote
Re: search engine bug-NEW
Posted by: martinw2
Date: June 04, 2014 06:48PM

In the latest beta 4 the same problem of search engines has cropped up again. Tried the fix I found worked in beta 3 but no luck. If the search.xml is replaced with the one that worked previously, it is not being picked up by the 'find websites tab'. Also, the same old problem of not being able to manually add search engines.

Puzzled.

Martin

Options: ReplyQuote
Re: search engine bug-NEW
Posted by: guenter
Date: June 08, 2014 03:51PM

Works here. XP SP3. Portable install on e:/ full writing rights granted.

Please consult the Error Console. Whether it throws an error from a damaged search.xml or ./browser/.../pref-webfind.xul.

If not check whether You have writing privileges in the used profile folder.
Either by Windows means else use the tool below.

Copy code into file name: troubleshooting.kmm, drop file into macros restart the browser and run. I think from tools menue.

#  K-Meleon Macros (http://kmeleon.sourceforge.net/wiki/index.php?id=MacroLanguage)
#
# File name: troubleshooting.kmm
#
# ---------- To check for user write priviledge on current profile -----
#
# Dependencies	: main.kmm
# Resources		: priviledge.ini, priviledge.htm, large-alert.png
# Version		: 0.3  10/30/10
# Author		: JamesD & desga2 modifications
# ----------------------------------------------------------------------

_Priviledge_RunCode {
macroinfo=_("Check KM profile write priviledge");
$_Priviledge_Path = getfolder(ProfileFolder);
$_Priviledge_Section = "Profile";
$_Priviledge_Key = "Current" ;
$_Priviledge_End = index($_Priviledge_Path,".");
$_Priviledge_Start = $_Priviledge_End - 1;
while($_Priviledge_Start < $_Priviledge_End) {
	$_Priviledge_Char = substr($_Priviledge_Path,$_Priviledge_Start,1);
	if ($_Priviledge_Char != "\\") {
		$_Priviledge_Start=$_Priviledge_Start-1;
		} else {
		$_Priviledge_Value = substr($_Priviledge_Path,$_Priviledge_Start + 1, 8);
		$_Priviledge_Start = $_Priviledge_End +1;
	}
}
$_Priviledge_Path = $_Priviledge_Path . "\\Priviledge.ini";
iniwrite($_Priviledge_Section, $_Priviledge_Key, $_Priviledge_Value, $_Priviledge_Path);
macros(_Priviledge_Validate);
}

_Priviledge_Validate {
# Value remains after delete because iniread is reading cached info in registry
$_Priviledge_Value2 = iniread("","","","");
$_Priviledge_Value2 = iniread($_Priviledge_Section, $_Priviledge_Key, $_Priviledge_Value2, $_Priviledge_Path);
if ($_Priviledge_Value != $_Priviledge_Value2) {
	$_Priviledge_WarnPath="about:mozilla";
	opennew($_Priviledge_WarnPath);
	} else {
	exec("cmd /c ERASE \"".$_Priviledge_Path."\"");
	exec("command /c ERASE \"".$_Priviledge_Path."\"");
	statusbar(_("KM profile priviledge checked successfully"));
	alert(_("KM profile priviledge checked successfully."), _("Check Priviledge"), INFO);
}
}

_Troubleshooting_BuildMenu {
setmenu(KMDocs, popup, _("Troubleshooting"), -1);
setmenu(_("Troubleshooting"), macro, _("Check Priviledge"), _Priviledge_RunCode);
}

# - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
$OnInit=$OnInit."_Troubleshooting_BuildMenu;";
$macroModules=$macroModules."Troubleshooting;";



Edited 1 time(s). Last edit at 06/08/2014 03:53PM by guenter.

Options: ReplyQuote
Re: search engine bug-NEW
Posted by: JamesD
Date: June 08, 2014 06:25PM

Just to let you know, Beta 4 has an upgraded Troubleshooting included. Look under HELP menu.

Options: ReplyQuote
Re: search engine bug-NEW
Posted by: martinw2
Date: June 08, 2014 09:50PM

Guenther,

Thanks for the advice but I still can't get it to work. I give up as this is so time consuming and has driven me nuts trying to get the search engines to work in both beta3 and now 4. I will just use bookmarks instead for the search facility. I see others are suffering from the same bug. I looked for an alternative to K-Melon but it is still one of the best in my view.

Martin

Options: ReplyQuote
Re: search engine bug-NEW
Posted by: Dorian
Date: June 09, 2014 10:51PM

To get meaningful info in the console add the pref kmeleon.search.log with the value true.

If you have an error in kmSearchService around line 729, I've fixed it for next release. For a possible workaround, change the value of general.useragent.locale at least once.


Edit: search.xml is in defaults and in the profile folder. The one in profile work as an "override" (like cfg file) since one of b3 update.



Edited 1 time(s). Last edit at 06/09/2014 10:53PM by Dorian.

Options: ReplyQuote


K-Meleon forum is powered by Phorum.