Page 2 of 2

Re: 1.13.0.x gargoyle-ispy 2020-August-17 19

Posted: Fri Aug 28, 2020 8:30 am
by wbennett88
Lantis wrote:
Thu Aug 27, 2020 7:36 pm
For something like the wireless scheduler which has no dependencies, very straight forward.

Use WinSCP to move the plugin .ipk to /tmp
Use Putty and issue

Code: Select all

gpkg install /tmp/name_of_plugin_file.ipk
Should be done.
When installed in this method, you can't uninstall them from the GUI, you would have to do that over the command line as well.
Thanks Lantis, I now have the wireless scheduler installed.
Cheers!

Re: 1.13.0.x gargoyle-ispy 2020-August-17 19

Posted: Sun Aug 30, 2020 1:31 am
by ispyisail
Image

Re: 1.13.0.x gargoyle-ispy 2020-August-17 19

Posted: Sun Aug 30, 2020 1:32 am
by ispyisail
Can't "Add Plugin Source"

Re: 1.13.0.x gargoyle-ispy 2020-August-17 19

Posted: Sun Aug 30, 2020 1:58 am
by Lantis
You haven't entered anything in the boxes...?

Re: 1.13.0.x gargoyle-ispy 2020-August-17 19

Posted: Sun Aug 30, 2020 4:35 am
by ispyisail
Lantis wrote:
Sun Aug 30, 2020 1:58 am
You haven't entered anything in the boxes...?
opps

I was expecting the boxes to pop up

Thank you

Re: 1.13.0.x gargoyle-ispy 2020-August-17 19

Posted: Sun Aug 30, 2020 6:18 am
by manwithoutachance
Router Archer C7 V2
update OK (I preserve settings)

But:
1. the adblock plugin install doesn't work
2. http://lantisproject.com/gargoyle_plugins is down??
3. adblock manual installation does not work. the wget or cron
command not found
4. update firmware: no preserve settings? korrekt?
5. on the website: password forgotten . Error 404

Re: 1.13.0.x gargoyle-ispy 2020-August-17 19

Posted: Sun Aug 30, 2020 7:36 am
by Lantis
There seems to be a lot of confusion lately.

If you are using one of these beta builds, plugin install must be taken care of ON YOUR OWN. That is why the plugins are included in the download.
Plugins ARE NOT (generally...) compatible between builds. That is why they are included in the download for you. Using any existing Gargoyle repository, or a repository that isn't specific to your build is probably not going to work.
If you preserve settings between incompatible builds, you're on your own fixing it. That is why the recommendation is to not do so. If you do preserve settings, at least let us know what version you came from so we know if it was likely the cause of the issue or not.