CDN to local puts the files in a non existing assets directory when using t3s_package

[vmans]

V12, latest t3sbootstrap 5.3.3, and using t3s_package, version 1.0.1.

The path to bootstrap.bundle.min.js becomes

"/_assets/81d415137a1f642a138f8273fcd813ac/JS/bootstrap.bundle.min.js"

but there is no directory "81d415137a1f642a138f8273fcd813ac" in the /_assets/ directory.

The files are fetched from the CDN correctly and accessible in ../../vendor/t3sbs/t3sb-package/T3SB/Resources/Public/. That's according to the documentation. It's just in the _assets directory where it goes wrong.

This is in the _assets directory:
4f615b6e6e09f9eeb87b070d64aef896 -> ../../vendor/t3sbs/t3sb-package/Resources/Public/
8cd52890f6ceed8b546f8b3e4b64a8ca -> ../../vendor/t3sbs/t3sbootstrap/Resources/Public/

Can it be that the files are in the path that starts with T3SB that causes this issue? And then, how to solve this?

Using the fileadmin or CDN, everything works as expected.

[t3solution]

Is it a new installation?

[vmans]

Yes, it’s a new installation.

[t3solution]

I have set up a new composer and non-composer installation with the sitepackage. Both installations work as expected!
Maybe you should use v5.3.10 instead of v5.3.3 !

[vmans]

It was 5.3.9 that was installed. Now with 5.3.10 it's not working either.

Problems seems to be withing the "assets" set up. See analysis + proof here, but no solution.

First, as the image shows, all the fetched files are there.

Both the symlinked and the direct way do not work. The symlinked is the default.

In the public/_assets/ directory we see this:

The source however is looking for the files in a different directory that does not exist:

This only happens if I use the package set up. With fileadmin ot goes well, probably because the _assets setup is not used.

Now when I rename the symlink in the _assets directory from 4f615b6e6e09f9eeb87b070d64aef896 to 81d415137a1f642a138f8273fcd813ac, it works well.

So what's wrong with the generated assets path?

[t3solution]

I can't understand your problem.
For further help I need BE and FTP access.

[vmans]

Thanks for your assistance. I will provide you those details soon. I will do that in a new test environment that I have to set up. Since I have this situation the last two times I set up a system this way, I think it will happen a third time too.

For now:

• It's a composer setup. I don't use compress and concatenate, to get the issue clear (with complress and concatenate I have the same issue).
• If you disable the CDN setting, and run the scheduler, the files are stored in a path; what path is that on your side?
• I assume the files are stored in the public/_assets folder too?
• In the foot of the HTML, you see the path as well; does that match with the _assets path on the server? I bet in your case it does, but not in my case (that's what the last two images show, the difference between generated paths).

[t3solution]

I have now been able to reproduce the error!
If I set the following constant:
bootstrap.config.compress = 1
then the error disappears.
Is it the same in your case?