Can't navigate through objects under occurrences, entities, in Pawtucket

alcoma

Hello,

We would like to be able to navigate through objects under occurrences, entities, and collections in the same way one can normally navigate through objects when browsing and searching in Pawtucket.

Specifically, the "next" links/arrows do not currently exist when viewing objects under an occurrence or related entity. It is frustrating for users to always hit the "back" button rather than be able to go to the next object in the group. I imagine there is some code that can be added to the relevant detail pages but I have not found an example yet.

Any suggestions? Thank you.

monica

What version are you on? It works likes this on the php8 branch. Not sure if it's something that's been changed in the newer version or just not working for you.

So as an example, on a collection page there is a mini search results at the bottom that shows all objects with that collection as it's parent/related to. Click on one and there are next / previous buttons to browse through them, or back to results which goes back to the collections page.

alcoma

We're on Application version 1.8
Schema revision 180
Release type GIT
System GUID 3288ffba-4192-48c8-bc7b-634474867911
Last change log ID 4474705
PHP version 7.4.33

And actually, we are planning to update to Php 8.0 soon and also recommended to upgrade from Centos 07 to Alma Linux by our web host. That should be ok ? I'd like to see what changes by updating our install of C/A.

monica

alcoma Alma should be fine. Which theme are you using (or which have you used as your starting point) ?

alcoma

Do you mean our Pawtucket theme? It is customized but starting from the "default" theme.

monica

alcoma looking at this commit https://github.com/collectiveaccess/pawtucket2/commit/aaa08b6985b34f7834a328a7670fbcf9fba50d71. It seems to be an enhancement to version 2.0 (dev/php8 branch).

alcoma

Great. Looks like this might resolve itself on update. What is the best way to update to dev branch once we're on php 8.0 ? Should we update Providence as well ?
Thanks.

monica

You should update both providence and pawtucket to the dev/php8 branch at the same time. This version also supports php7.4, so you can upgrade the application first, then upgrade PHP8 (up to v 8.2)

To upgrade, first Backup your database.
Then run git checkout dev/php8 to bring in the updated code (assuming you used git to install develop branch 1.8).
You might want to make sure you haven't made any changes to core code that will be overwritten doing this. git status will tell you any files that have been modified. Assuming nothing shows here, then you are safe to use the checkout command, git will usually not let you checkout if there are conflicts like this.

Go to the site page and it'll tell you to click a button to perform migrations. This takes you from revision 180 to 195.

Your site will most likely work at this stage, but there might be complaints about some vendor libraries.
To update vendor libraries you'll need to delete the composer.lock file and run composer update

Some other tasks you might need to do are.

Clear caches
Reindex

alcoma

Thanks Monica! You've been so helpful.

I just ran 'git status' in both our Pawtucket and Prov. directories and received this msg:

"fatal: detected dubious ownership in repository at '/home/xxx/public_html/pawtucket'
To add an exception for this directory, call:
git config --global --add safe.directory"

I'm assuming since I didn't receive other info this is fine to add the "safe.directory" and proceed with git update. ?

monica

alcoma That message is because the user you ran git status as isn't the user that owns the git repository, so security doesn't let you see the details. As a root user, you can go ahead and add the safe.directory call to stop this message from happening and let anyone who has access to that directory see the details, or run your git commands as the owner of the repository.

alcoma

Got it. I updated my Providence directory to the dev/php8 branch without issues.
Then when trying to do the same in the Pawtucket directory, I received this error:

error: pathspec 'dev/php8' did not match any file(s) known to git

Did I miss something ?

alcoma

Well I figured one part out, and I think it was because I could only see a single branch from the first clone, so I ran

git remote show origin
then
git fetch dev/php8
git checkout dev/php8

and I have it running. Now, I'm just trying to get migration updated, and not sure how to proceed as I thought updating the dev branch would do this ?:

"Your database is out-of-date. Please install all schema migrations starting with migration #181."

monica

alcoma there should be a link on that page to trigger the database migration. If for some reason there isn't, run the caUtils command to update the database schema (do a caUtils help to get the command).
The migration should take you to schema 195. If it doesn't you might need to do a git fetch on providence to to update the dev/php8 branch, then git pull to ensure its completely up to date

alcoma

No no link but I ran the caUtils to update db schema and this was the output:

Database already at revision 180. No update is required.

I'll try the git fetch.

alcoma

Ok, I did the git fetch & pull then updated the schema which now shows:
Application version 2.0
Schema revision 197
Release type GIT

Going back to the navigation issue; I still don't see the ability to nav next when browsing objects under collections, occurrences, entities. I do see the nav next from one collection to another which is great, but is there any way to apply same principle to objects when browsed under those categories ?

Also, the Pawtucket update changed some design issues for us, like the audio player and our social media icons.

monica

alcoma have you cleared all caches?

alcoma

Yep. I cleared caches. I realized the player changes were because the new plyr css overrode some custom css for the older medialelement audio player. I just updated some settings in the new plyr.css and that is fine.

The other issue is that the icons for the social media widgets in the footer are no longer visible, just the background color. Wonder if the icons call in some custom css is somehow invalid after the update ?
No changes though in the navigation issue.

monica

alcoma only things left to suggest is to compare your code to that of the default theme. Are you overriding any controllers? Last thing is to share your theme so we can look at it.

alcoma

Thanks Monica, I'll compare it with the new default theme. How can I share our theme or the current code in our footer thats not working ?

And one more question re: the ability to browse next under occurrence and entities: as you mentioned previously

So as an example, on a collection page there is a mini search results at the bottom that shows all objects with that collection as it's parent/related to. Click on one and there are next / previous buttons to browse through them, or back to results which goes back to the collections page.

This is exactly what we're looking for to happen when browsing through the mini search results under an entity name, or an occurrence (which in our case are 'events'). Right now those navigation options only happen when browsing or searching objects or browsing collections. Is there a setting somewhere that will give entities and occurrences the same browse actions as those for objects and collections?

monica

alcoma
Do you have a live page we can look at?

To share the code, you would compress all the files in your theme directory and share that as a whole.

I don't believe there is anything you need to turn on, it all should just work.