Skip to content
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

asset 404 error for ui-bg_flat_75_ffffff_40x100.png #5058

Closed
anonymous-matomo-user opened this issue Apr 30, 2014 · 3 comments
Closed

asset 404 error for ui-bg_flat_75_ffffff_40x100.png #5058

anonymous-matomo-user opened this issue Apr 30, 2014 · 3 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously.
Milestone

Comments

@anonymous-matomo-user
Copy link

I noticed that my error log was filling up with 404 errors for this asset file that seems to be a part of jQuery UI. I did some digging around and found out that the issue first presented itself when I upgraded from PHP 5.3.10 to PHP 5.3.11 on CentOS 6.5.

Specfically before the update I would see this:

./tmp/assets/asset_manager_global_css.css: background: #fff url(/libs/jquery/themes/base/images/ui-bg_flat_75_ffffff_40x100.png) 50% 50% repeat-x;

Before the update I would see:

./asset_manager_global_css.css: background: #fff url(libs/jquery/themes/base/images/ui-bg_flat_75_ffffff_40x100.png) 50% 50% repeat-x;

Note that the difference is the path changed to absolute which is a bug and incorrect. I'm not sure why a version change would do this but usually this suggests that the code that dynamically generates the path for the install was relying on some side effect or undocumented feature that PHP 5.3.11 deprecated.

@mattab
Copy link
Member

mattab commented Apr 30, 2014

Maybe this is related to: #5060 Incompatibility with PHP 5.5.11
But you are using 5.3.11 so probably not.

@anonymous-matomo-user
Copy link
Author

Ah my bad. I'm running 5.5.11. That was a typo/mistake on my part. I would then say it's most definitely the same issue as #5060. You should close this as a duplicate. I wasn't able to find that existing ticket since this site is incredibly hard to search for existing issues IMO.

@mattab
Copy link
Member

mattab commented May 1, 2014

Thanks! Yes searching here is quite hard, we are still thinking /looking for a better issue tracker system

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Development

No branches or pull requests

2 participants