Library functions and menu missing in /dev/php8?

brucek

I have two installations of prov. running: /git/dev running php v7.4, and /git/dev/php8 running php v8.3.

Everything else should be identicle....except the php8 does not display the Library menu, and browsing index.php/library/Dashboard/Index give an access denied error.

Both have the same /local/app.conf and /local/library_services.conf.
Both are using the same database, so user acess settings are the same.

Any thoughts?

brucek

Well I have tracked this down to /app/conf/local/app.conf NOT being referenced by (within DashboardController.php) but ONLY referencing /app/conf/app.conf

~ line 48: ...!$this->request->config->get('enable_library_services') || !$this->request->config->get('enable_object_checkout')) { ...

If I set:
enable_library_services = 1
enable_object_checkout = 1
within /app/conf/app.conf then all works...
but if I only set them in /app/conf/local/app.conf then it doesnt work

Somehow $this->request->config->get('enable_library_services') is ONLY checking /app/conf/app.conf and NOT /app/conf/local/app.conf

monica

Double check the permissions on the local directory and files inside. Do other settings in app.conf work?
Should also mention that CA hasn't been tested on PHP 8.3 yet.

brucek

my /local/app.conf is definitely being read correctly for all other functions, so I dont think its a permission issue.

Oh, I am running php8.3. Maybe I'll drop down to 8.1 and try it.

monica

I am running dev/php8 branch and library function appears if I turn it on. Maybe you have caching on for the menu? You can try clearing caches.

brucek

I have caching turned off for menus.
I am leaning towards a typo or some other mistake in my /local/app.conf file that I just havent spotted.

This would not be the first time I have spent lots of time only to discover a missing/extra comma, etc in a conf file.
It would be really nice if there were some tools for auditing config files for proper syntax, etc. This really becomes an issue with more complicated structures such a history tracking .

In general I find that while most errors are handled well, typo's in conf files often give no useful errors, but can cause very strange results.

monica

To test that, put the library config at the top of the file, if it works there, then there are errors further down. Edit the conf in a good text editor that will show misalignments like unmatched parentheses when creating.

I always put the history tracking rules at the bottom of the file.