Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

  • 0
Pierrox15

B-O Timestamped images return 404

Question

Hello,

In the Backoffice -> product edit -> Images Tab: Thumbnails got a timestamp like "?time=1568749403911"
The image return a 404 and a default no-image.jpg is displayed.  If I remove the timestamp from the url the image is display correctly.
the problem occur only on this tab. (i

I don't know why, my local web server do that for TB.
I try with modules and overrides disable, Hard cache reset on firefox and reload TB  cache but  it's the same issue.

In many other CMS timestamped resources have no problem and  In my CSS files on front I use timestamp for Fontello icon and it works as normal.

I don't know where I can search for fix that?

 

Edit: in the fancybox,  when i click on this image (exactly the same ressource is called) image display correctly. It's no sense for me 😞

Edited by Pierrox15

Share this post


Link to post
Share on other sites

5 answers to this question

Recommended Posts

  • 0

More tests:

localhost/img/p/2/5/7/3/8/25738.jpg?time=156874940  // (thickbox) hit
localhost/img/p/2/5/7/3/8/25738.jpg // (thickbox) hit

localhost/img/p/2/5/7/3/8/25738-small.jpg //  hit
localhost/img/p/2/5/7/3/8/25738-small.jpg?time=156874940 // 404

 

Capture d’écran de 2019-09-17 22-30-43.png

Share this post


Link to post
Share on other sites
  • 0

So what i understand: they are a rewrite rule who try to do this:

localhost/img/p/2/5/7/3/8/25738-small.jpg -> localhost/img/p/2/5/7/3/8/25738-small_default.jpg

who work but  break on querystring timestamp.

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

Excellent analysis! This timestamp was introduced here:

https://github.com/PrestaShop/PrestaShop/pull/4267/commits/1e1932559758ce989a8d42d931fd650043234d21

to fix this bug:

http://forge.prestashop.com/browse/PSCSX-7050

Such a timestamp doesn't make sense to me. Each image has an individual number, there should be no caching issue (unless one changes the image on the command line or by FTP).

I've reverted this commit, which results in loading the right picture. On Bleeding Edge -> 1.1.x in ~10 minutes.

Share this post


Link to post
Share on other sites
  • 0

Timestamp is very usefull, and it will be available on all resources to refresh all cache when it needed. It's the easiest way to control a web cache server 🙂

I don't know prestashop very well... but I think, it will be the job of PageNotFoundController.php to consider querystring at the end of ressource and a .htaccess rules.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...