-
Notifications
You must be signed in to change notification settings - Fork 2k
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
"New view" button does not work #4260
Labels
Comments
Sacrond
referenced
this issue
May 21, 2018
To make easier to track changes and simplify the deplyment and upgrade, the Solr schema file included in the CKAN source is now unified under `schema.xml`. As part of the release process, the file will be checked for changes, and if present the version numbers on the schema file and the supported versions list will be updated. Release, install and upgrade docs have been updated to reflect this changes. Travis now also always points to schema.xml
@klikstermkd can you have a look and see if it's an easy fix? |
@amercader Yes I will. |
amercader
added a commit
that referenced
this issue
Apr 30, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CKAN Version if known (or site URL)
2.8
Please describe the expected behaviour
If the portal is in Bootstrap 2 mode, the "New view" button located in the "Views" tab for a resource, when clicked it should give a list of possible views to create.
Please describe the actual behaviour
If the portal is in Bootstrap 2 mode, the "New view" button located in the "Views" tab for a resource, when clicked it does not give a list of possible views to create. Instead in the browser console it shows the following error when clicked:
What steps can be taken to reproduce the issue?
In a CKAN 2.8 portal, make it to use Bootstrap 2 by setting
ckan.base_templates_folder
totemplates-bs2
andckan.base_public_folder
topublic-bs2
in the config file. Then create a resource. Go to the "Manage" page for the created resource and then "Views" tab. Try to click the "New view" button.The text was updated successfully, but these errors were encountered: