SlouchyFlower
Member
Posted 1 year ago #
The relative path to 'loading.gif' from slimbox2.css seems incorrect. Perhaps when the css was moved to its own folder, the path didn't get updated? I'm getting lots of 404s in my logs trying to access
/wp-content/plugins/wp-slimbox2/css/images/default/loading.gif
it's an easy fix, but I don't like modifying core plugins as a general rule. So if it could be worked into the next update that'd be awesome.
Thanks!
http://wordpress.org/extend/plugins/wp-slimbox2/
malcalevak
Member
Plugin Author
Posted 1 year ago #
Thanks for pointing this out. I actually saw this the other night, but I didn't actually process what it meant until you posted.
You're quite right about the cause of the problem, a fix should be coming soon.
leanderbraunschweig
Member
Posted 1 year ago #
I just wanted to inquire about the very same error here.
If I fix this one (code from relative to absolute), will the next update work fine e.g. overwrite my settings?
Thanks.
malcalevak
Member
Plugin Author
Posted 1 year ago #
It's not a matter of switching from relative to absolute, it's a matter of just pointing to the correct directory.
Just change url(images/default/loading.gif) to url(../images/default/loading.gif)
Then, when the next update is out (it's delayed since I'm trying to get more than this fix into it) it will continue to work fine.
SlouchyFlower
Member
Posted 1 year ago #
Awesome, thanks Malcalevak!
folgerj
Member
Posted 5 months ago #
I'm still seeing the same error, was this fixed or is it still in the develop phase?
malcalevak
Member
Plugin Author
Posted 4 months ago #
I've been a bit sick, so I haven't been able to wrap up the next release, however, the posted modification should still work.