Skip to content
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

SAGA tools no longer appear in 3.28.1 #51041

Open
2 tasks done
mapninja opened this issue Nov 28, 2022 · 7 comments
Open
2 tasks done

SAGA tools no longer appear in 3.28.1 #51041

mapninja opened this issue Nov 28, 2022 · 7 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! macOS Packaging

Comments

@mapninja
Copy link

What is the bug or the crash?

After upgrade to 3.28.1, SAGA tools no longer appear in the processing menu, and so cannot be accessed through the SAGANP plugin.

Steps to reproduce the issue

Install 3.28.1

Go to Main Menu>Processing>

Neither SAGA nor SAGANP (when installed) show up in the menus for the processing panels.

When you go to Processing>Settings they are both present in providers, but under neither has anything under the Menus item

Versions

Appears to only effect 3.28.1

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

  • I tried with a new QGIS profile

Additional context

Multiple installations, all MacOS, so far. Looks like a packaging oversight.

@mapninja mapninja added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Nov 28, 2022
@nyalldawson
Copy link
Collaborator

FYI: While this should work in 3.28, the inbuilt SAGA tools have been completely removed for 3.30. It's highly recommended that you start manually installing SAGA and using the 3rd party SAGA next gen plugin in order to prepare for this.

@mapninja
Copy link
Author

OK, seems to have been removed for 3.28.1, since none of my students are able to finish the lab exercise I wrote with 3.28.0.

Wish there was a way to know about these major removals before upgrading.

@nyalldawson
Copy link
Collaborator

nyalldawson commented Nov 28, 2022

It wasn't intentionally removed for 3.28.1 -- I suspect that's just a packaging issue with the macos installer. (ping @3nids)

Wish there was a way to know about these major removals before upgrading.

Trust me, It will be clearly communicated in the release notes for 3.30!

@agiudiceandrea
Copy link
Contributor

SAGA-GIS processing algorithms are available in QGIS 3.28.1 on Windows (OSGeo4W).

@DusanEastcode
Copy link

SAGA-GIS processing algorithms are available in QGIS 3.28.1 on Windows (OSGeo4W).

no MacOS anymore?
I run 800+ programmer community so maybe I can help :)

@benz0li
Copy link

benz0li commented Feb 13, 2023

Processing provider for SAGA 7.2. Requires manual installation of SAGA 7.2 binaries.

Processing Saga NextGen Provider — QGIS Python Plugins Repository > About


I am asking because bullseye (Debian 11), focal (Ubuntu 20.04 LTS) and jammy (Ubuntu 22.04 LTS) have v7.3.0 in their package repository.
ℹ️ bookworm (upcoming Debian 12), sid (upcoming Debian 13) and lunar (upcoming 24.04 LTS) have currently v8.5.0 in their package repository.

Furthermore, saga v7.2.0 does not build on 'Debian 11'/'Ubuntu 20.04 LTS' and newer – only saga versions ≥ 7.3.0.

@nyalldawson Is it safe to use this plugin with saga versions 7.3.0 and 8.5.0? Any plans this plugin will officially support saga versions > 7.2.0?


Cross references:

@amyfox777
Copy link

I just want to add here that directing students to install and open an older version of QGIS (in this case: 3.8.2), is a wonderful way of introducing them to regressive software. Some of the old versions of QGIS work so much nicer for individual projects.

Never lose the opportunity to teach students to "stretch" back to the older versions of QGIS. We can never have enough QGIS, can we???

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! macOS Packaging
Projects
None yet
Development

No branches or pull requests

6 participants