Do not use Opsed with the latest weekly
Saturday, 17. March 2007, 00:15:10
Do not use Opsed with the latest weekly, that is Opera 9.20 Build 8746. It will simply not work. So, it seems that Opera 9.10 was the last version ever that was supported by Opsed. 
BTW, I do really hope that all of the bugs related to the freshly modified search.ini handling will be fixed before Opera 9.20 final is launched. Otherwise the concept of making selected search engines hardcoded (
) and performing search engine merging should be dropped out of 9.20.
BTW, I do really hope that all of the bugs related to the freshly modified search.ini handling will be fixed before Opera 9.20 final is launched. Otherwise the concept of making selected search engines hardcoded (
) and performing search engine merging should be dropped out of 9.20.
WIDGETIZE
larskl # 17. March 2007, 12:44
andol # 17. March 2007, 21:20
After introducing the basic search engine manager in Opera 9, usefulness of Opsed has dramatically decreased. Supporting Opera 9.20 would mean too much work, which would be disproportionate to any benefits offered by Opsed over the Opera's own manager.
This post was meant to warn Opsed users not to use Opsed with Opera 9.20 and later. Fortunately Opsed will not harm Opera, but it will also not be able to modify the set of search engines efficiently.
yadavankur # 21. March 2007, 09:29
andol # 21. March 2007, 21:25
Flexman # 23. March 2007, 10:56
One reason why I still use Opsed is that you can download things from the Opera Search Plugin Manager and don't have to to them yourself if you are lazy!
Flexman # 23. March 2007, 11:02
andol # 23. March 2007, 20:45
Originally posted by Flexman:
Build 8746 was the first public one with the modified search.ini handling.
Originally posted by Flexman:
Are you sure you have entered a valid data into the submit form?
grogge # 24. March 2007, 16:38
At first I thought, "oh shit, now they hardcoded some default search engines into Opera". But actually these default searches are only present in the above mentioned "search.ini" that resides in the program folder.
After deleting it, my personal search.ini in my profile folder works like before. No annoying default searches pop up after restart and so on... and the good thing is that it won't get re-created once it was deleted from "Program Files\Opera", just make sure to not "Start Opera when I press Finish" after Upgrading to a new built, because the Installer will place a new copy into the program folder, of course, which must be deleted once again or else your personal "search.ini" will get messed up again.
andol # 24. March 2007, 21:11
BTW, deleting the default search.ini located in the Opera directory may not work this way in the future.
jite # 2. May 2007, 14:00
Well I do not know... Simply, maybe, not so often it was necessary to edit in this search.ini? But I did not use OPSED. And here it became suddenly interesting, because of what it is people worry. Can try at last?
andol # 2. May 2007, 19:31
Try this: http://help.opera.com/Windows/9.20/en/search.html
jite # 3. May 2007, 16:09
In it also there was a humour: the some people before to esteem the author, think out the theories...
About "access to the linked content" not understood. :\ Well no matter...
andol # 3. May 2007, 19:07
After clicking the link provided by you, I get a message saying: "You are not authorized to view this protected entry." So I'm not able to read the entry, and I have no idea of what you are talking about.
jite # 4. May 2007, 11:05
I am corrected, as 1-st beginnings. Actually anything serious.
The following citation on your site has been misinterpreted.
<< Opsed development is discontinued. Opera 9 TP2 introduces a nice and easy to use built-in search engine manager, so Opsed will not be needed anymore soon. Opsed does not support Opera 9.20 and later. >>
Wrong treatment: in Opera 9.20 so all became good with editing, that OPSED simply is not necessary. There was a question on this new wonderful editor which is built in 9.20...
How much I have understood, in version 9.20 syntax was just changed. And OPSED which is not planned to update (2 years as the project is completed), it will be incorrect to work with new search.ini.
The wrong understanding of the mentioned phrase has soon been successfully explained.
The author of a question has complained about unwillingness to climb in a file and to edit it manually (to insert dividers to change the order of services). I have objected it, that it is not too complex. On that have calmed down...
I apologize for anxiety, probably here already it is more than there has written...
andol # 4. May 2007, 21:37
jite # 5. May 2007, 11:54
By the way, whether came to to you mind to simplify/visualize editing of Opera menu (profile\menu\bla-bla-menu.ini) in the same way?
How much I know, such product still is not present, but the need for him is.
Or simply you had a necessity of editing of the search interface and it was the reason of the program?
I know, that it is bad to do in advance such declarations, but, probably, I shall try to make something in this direction - to visualize editing the menu.
(As already had experience of editing of the menu manually. Successfully, of course. But has been spent many time! It was not pleasant.)
andol # 5. May 2007, 22:26
http://my.opera.com/andol/blog/so-called-opera-search-engine-manager
Yes, but then I've heard from someone that such feature was planned for Opera itself, so I gave up. Some years have passed and we still do not have the visual menu editor. And I don't think we'll see it in near future. Such things are rather not prioritized.
Well, I do not edit my search.ini too often lately, since it's quite established. And when Opera tried to force me to use some unwanted search engines I've just used my text editor. But I have friends who sometimes ask me to help them with Opera configuration.
Good luck.