Providence functionality broken

alexgoldmanccmm

Hi all!

Providence (dev/php8, on php8.3, freshly pulled today) quite suddenly stopped working correctly on all but one computer. Doesn't matter which log on is used, but only one laptop can access it correctly. On all of the others, the navbar mis-aligns, any button (such as for editing) isn't there, the object editor shows nothing in any field (but the objects themselves still have their data, it shows in summary), clicking things like "log in" or "save" produce no action, among others. This seemingly occurred out of nowhere, and I cannot for the life of me figure out why it only works on ONE computer (on chrome, running windows 11 -- but doesn't work on any other computer running chrome or firefox on windows 10, windows 11, or ubuntu). I cleared the providence cache, cleared the browser caches... nothing. The logs are full of warnings for undefined variables and arrays etc but not related specifically to the problems we're facing with accessing providence.

It is possible that this all started after trying to do a batch edit (which failed) to switch all object representations (media) to be accessible to public, but the fact that one computer still has zero problems with access makes me think it isn't to do with that. But thought I'd mention it anyway!

I would definitely appreciate any ideas or thoughts!

Thanks, all!

Alex

monica

alexgoldmanccmm Do you have a link you can share? I'm not sure what the state of the dev/php8 branch is, I think it's just a little behind the current release, so should work.

Have you tried the master branch, or upgrading to one of the version 2 tags? Up to version 2.0.3 with 2.0.4 coming out soon.

monica

alexgoldmanccmm Another thought is the assets directory, or the content of it is no longer readable during one of your recent pulls.

alexgoldmanccmm

Hi @monica !

I switched to the master branch, no dice, unless there's something else I need to do after pulling that branch.

I tried switching something in the app.conf just to see if the site can see the assets directory, and it did cause a change, so it isn't that (phew).

I created an account for you. Our site is located at https://access.ccmmla.org
Your username is monica
Your password collectiveaccess (you'll have to hit enter after the password, clicking login doesn't work)
It's a very limited account, so I'm not worried about the log in living on the forum at least for the time being! I had to create it from an ssh session. Because the functionality is so reduced, I recommend doing a quick search for * just to pull up results. If you try to browse, clicking on any of the browse options does nothing. And you won't be able to open an object record directly because there's no way to select any from the search results. But I can send you a link to one.

I feel like it has to be something in the css that is messing up. I haven't modified any of it, but it would explain the site still being functional on the computer that can access it because we haven't cleared the cache on there or forced it to reload the site, so it's still using an old style sheet.

monica

alexgoldmanccmm Much of the jquery is not accessible and giving a 404 not found returned. This means files in your /assets and /css directories don't have the right permissions.

If you run ls -l over the content of assets/jquery you might see that they (or some of them) don't have read permissions.

alexgoldmanccmm

Ohhhh the way I am blushing right now. Is there a list of recommended permissions for various parts of the site? I just set everything in app and assets to 775 which may be overkill. I don't have root access because it's a shared server, so I run into problems with the 'fix-permissions', but I can manually set things and I don't mind doing it!

Thank you, @monica , truly lifesaving.

seth

The files need to be readable by the web server. That's pretty much it.