-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First addon install (or reinstall after program update) changes the user home config.ini to default values #5
Comments
i tried some out and they seem to work. |
Where do I get the site.xml file? Feature.xml has the following content:
|
on the release page where u downloaded 2.4.0 is also a download for the updated addons including the offline mode one: https://github.com/Xyrio/RSSOwl/releases then just follow the steps on the release page about the update site for addons. |
Thank you! I got it to work, but noticed the following:
|
yes you need to change the configuration\config.ini so that it uses the .rssowl2 in you local folder. another difference to 2.2.1 is that plugins are now installed in the .rssowl2-beta (or however you changed it) folder. i intentionally changed folders in case there are bugs. config221 is not used. old .rssowl2 folder is now .rssowl2-beta as mentioned. |
I guess what I'm saying is that I changed "configuration/config.ini" when I first started using your version and everything was working. But as soon as I installed an addon, all my settings and feeds were (seemingly) lost, because it created another profile somewhere else. I then had to go "config240/config.ini" and point it back to my profile. So it seems that if no addons are installed, "configuration/config.ini" is being used. As soon as addons are installed "config240/config.ini" is being used. |
yea i tried it now and the very first time you install an addon it writes the default paths to the .rssowl2-beta\config240\config.ini you need to correct those before you restart. afterwards it doesnt seem to do it anymore. even when uninstalling all addons an then installing a first addon again it stays on the changed path. |
I tried version 2.6, but still cannot get "Offline Mode" to work in a custom user directory. "Offline Mode" + custom configuration is working fine in the original version 2.21. |
there is a second config.ini inside the home folder: .rssowlnix-beta\config\config.ini more #2 ps: http://tutorial.rssowl.org/ht_offline.html is for rssowl 1.x i think. |
I tried that several times but it doesn't work. I did get it working in a version prior to 2.6. To recap, version < 2.6 can only do one of the following (but not both at the same time): |
i am using 2.7.0 with modified path with the notes addon myself so i know it works. so here are the steps (just now did it like this):
it needs this fix only once, somehow it remembers now but only until a new version triggers addon reinstall. after that need to fix the file in home folder again. (maybe reinstall also changes the one in the install folder, i dont remember). |
Thank you. I followed your steps and got it working again. I wish there was an easier way to save the profile folder within the application for portable applications. |
Thank you for picking up this project!
Are addons no longer supported?
I was using a 6KB offline addon, which adds the option File > Work Offline, to limit RSSOwl to the cached article feed. Using Wireshark, I noticed that RSSOwl makes an online request every time one would click on an article. This was true even for text only articles, presumably to check whether the article has been updated since downloading the feed.
This behavior is also documented here:
http://tutorial.rssowl.org/ht_offline.html
"When online, RSSOwl reloads news summaries and retains them in memory each time you select a newsfeed."
Is it possible to run addons? I tried putting it into "p2" and also into the "plugins" folder.
Or can an offline mode be implemented?
P.S.: Your sourceforge forum post regarding placing java inside the installation folder without having to install it is a great tip! Perhaps adding this to the main page would be helpful to many users.
The text was updated successfully, but these errors were encountered: