Support Forum
I'm seeing 404 error on images in /wp-content/sp-resources/forum-themes/css-only/images/ running the latest SP 5.5.1. I can access the images directly through a URL, for example, http://mysite.com/wp-content/s.....owDown.png, but they don't load when displaying the forum page.
Other than the missing images, the forum topic displays as expected. The Chrome console just shows a bunch of 404 (Not Found) errors.
Any suggestions as to how I can best resolve this?
Hey Brad,
So taking a look, as far as I can see the images don't appear to exist, as in I too am seeing the 404's on the ones that are supposed to display, namely the icons for the buttons in the header..Ironically one of the only ones that I can see on it's own is the one you referenced in the first post 'arrow down'...
I would suggest that firstly if you could, take a look in the actual image folder and see if they do exist. If they do, then we are probably looking at some kind of permissions issue which we can then look into resolving.
If they don't, then firstly it would be nice to know why they don't, but a fix would probably be to re-download the css-only theme and replace the folder.
Might actually be worth - as a first port of call - trying a different SP Theme. Default or Unified maybe.
Let us know how you get on
Thanks for your suggestions and comments.
Looking from cPanel, I'm seeing fully populated images folders in the forum themes. The problem persists after switching to the stacked theme and then back to css-only theme.
When I view the Chrome console, I can click on one of the image links in the list of 404 errors. This brings me to a Page not Found 404 error within my site http://mysitename.com/wp-conte.....Button.png
However, when I shorten the above to the containing directory rather than the file, http://mysitename.com/wp-conte.....es/images/, I am presented a list of files in the directory. Oddly, though, these are NOT the filenames that I expect to see here, and that I do see in cPanel. Here are the files (and directories) shown at http://mysitename.com/wp-conte.....es/images/:
Parent Directory
mobile/
sp_SubscriptionsForumStatus.png
sp_SubscriptionsPostEditor.png
sp_SubscriptionsReviewButton.png
sp_SubscriptionsSubscribeButton.png
sp_SubscriptionsSubscribeForum.png
sp_SubscriptionsSubscribeForumButton.png
sp_SubscriptionsUnread.png
sp_SubscriptionsUnsubscribe.png
sp_SubscriptionsUnsubscribeButton.png
sp_SubscriptionsUnsubscribeForum.png
sp_SubscriptionsUnsubscribeForumButton.png
I'll keep exploring and let you know if I find anything else of interest.
Brad
I cleared my local browser cache and turned off my cache plugin on the server. I still have the 404 errors showing in the Chrome console. Now, however, I can go to the containing directory and see ALL of the expected files here: http://mysitename.com/wp-conte.....ly/images/
I can then successfully click on any of the linked images from that index page and load the image successfully, no 404 error.
This is in contrast to when I click on an image link from the Chrome console. That gives me a 404 page.
I wonder if the referrer has some new significance when loading an image. For example, I can successfully load destination B from referrer A but receive a 404 when I try to load destination B from referrer C. Is there any difference in the way the theme images are loaded in comparison to the way other images on the page are loaded (successfully)?
There is nothing different about the way any images are loaded up.
However, there were some changes in SP 5.5.1 in the construction of the images paths. Actually made them simpler and more versatile in terms of customisation. But if I am understanding this thread correctly that is not really the problem.
What DOES seem to be the problem if you look closely at the HTML being generated (and you can see this in the browser console as well) is that the file names are being altered in many - but by no means all - of the images.
To take an example of a 'missing' icon - the html refers to it as 'sp-ForumIcon.png' when it is, in fact, named 'sp_ForumIcon.png'. So the big question is - what is changing the correct underscore to an incorrect hyphen?
YELLOW
SWORDFISH
|
1 Guest(s)