-
Notifications
You must be signed in to change notification settings - Fork 38
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
Test 2.1 updates and fixes #59
Comments
Not sure what you mean by "selected exhibit", but exhibit titles are appearing in the Search by Exhibit dropdown list. And I can search for items in a specific exhibit. |
The change here is about whether the search results page tells you you're searching for a particular exhibit. Previous Exhibit Builder versions don't. |
Got it. And yes, the name of the exhibit does appear as a search term on the results page. |
I am having trouble getting the master branch to work. I've tried re-installing multiple times, deleting the whole thing and cloning new. I can see and edit the main exhibit information, but any time I try to edit (in admin) or view (public side) an exhibit page, I get the following errors: #0 /home/mebrett/meganrbrett.net/make2exhibit/plugins/ExhibitBuilder/views/admin/exhibits/page-content-form.php(20): web_path_to('exhibit_layouts...') |
Is this a site you've previously had Exhibit Builder's "next" on? You generally can't go back and forth between the two on the same installation easily. If you were using "next" on here, you need to checkout "next", uninstall the plugin, checkout "master", then install. |
That was indeed the problem. It's working now, thank you. Contributor can delete exhibits created with that account. Can only edit exhibits it created. It can see the others in the exhibits panel in admin, but can only explore them through the public side. Both exhibit names are showing up in the drop-down for exhibits when doing advanced item search and when searching in the Add an Item dialog box in Exhibit Builder (I think that's what you were asking?) |
Everything here seems to be a-ok. |
@sheilabrennan, @mebrett
On branch "master."
Test that:
The text was updated successfully, but these errors were encountered: