Forum: Radiant CMS image 404s

B39240dc7475fb78645c56818ead0ac5?d=identicon&s=25 rosslaird (Guest)
on 2010-12-02 01:26
(Received via mailing list)
I have just started using Radiant (which is just great, by the way),
so apologies in advance for what may be a very simple question: the
server log shows various 404s to image files: button.png and new-
snippet.png are two examples. My setup is on locahost, for testing, so
the 404 refers to (for example) this url:
http://localhost/images/admin/button.png.
There are quite a few image files in /images/admin, but not
button.png. On the other hand, there is a new-snippet.png in the
images/admin directory, but I still get a 404 for that file as well.
These image files are not ones that I have created, so I'm not sure
what's going on. I do have some extensions installed (Chronicle, blog,
mailer, paperclipped, settings) and I don't know if these are a
factor. I have combed through all the css files I can find, and
nothing seems to point to these missing files.

Suggestions?

Thanks in advance.

Ross Laird
D24f9cba71237accf4281ed2a9fc3fd2?d=identicon&s=25 Craayzie As a fox (craayzie)
on 2010-12-02 01:54
(Received via mailing list)
connect to your DB and do a select * across all the tables w/ a content
field:

page_parts
pages
snippets
layouts

e.g. select * from page_parts where content like '%button.png%', etc.

That should identify where the reference to the asset is.

For the new-snippet.png 404 - that's a tough one. I'd use curl to debug
it -
confirm the 404 w/ curl and then go from there. My guess is the browser
is
requesting it with the wrong URI.

e.g. curl -svo /dev/null localhost/images/admin/new-snippet.png

HTH,
Fima
B39240dc7475fb78645c56818ead0ac5?d=identicon&s=25 rosslaird (Guest)
on 2010-12-02 03:02
(Received via mailing list)
Thanks for the help.
Unless I've done something incorrectly, this:

> select * from page_parts where content like '%button.png%', etc.

returns no results (I did this in PHPMyAdmin) for any of the tables
with a content field.

> For the new-snippet.png 404 - that's a tough one. I'd use curl to debug it -

Here's what I get from "curl -svo /dev/null localhost/images/admin/new-
snippet.png":

 GET /images/admin/new-snippet.png HTTP/1.1
 User-Agent: curl/7.21.0 (i686-pc-linux-gnu) libcurl/7.21.0 OpenSSL/
0.9.8o zlib/1.2.3.4 libidn/1.18
 Host: localhost
 Accept: */*

 HTTP/1.1 404 Not Found
 Date: Thu, 02 Dec 2010 01:51:01 GMT
 Server: Apache/2.2.16 (Ubuntu)
 Vary: Accept-Encoding

I'm not sure where to go next with that.

So, overall, I am learning things (the upside) but not closer to
resolving this (the downside).
Thanks again for the help.

Cheers.

Ross
D24f9cba71237accf4281ed2a9fc3fd2?d=identicon&s=25 Craayzie As a fox (craayzie)
on 2010-12-02 04:56
(Received via mailing list)
Can you hit other assets in the /admin dir w/ curl and do u get a 200?
B39240dc7475fb78645c56818ead0ac5?d=identicon&s=25 rosslaird (Guest)
on 2010-12-02 05:09
(Received via mailing list)
Nope. I get 404 for them all.

R.

On Dec 1, 7:55pm, Fima Leshinsky <flesh...@gmail.com> wrote:
> Can you hit other assets in the /admin dir w/ curl and do u get a 200?
D24f9cba71237accf4281ed2a9fc3fd2?d=identicon&s=25 Craayzie As a fox (craayzie)
on 2010-12-02 08:26
(Received via mailing list)
Yup so your request path/URI is wrong. Do a:

$ pwd; ls -lh

inside your image directory
0964828011133c856bae646e55911115?d=identicon&s=25 William Ross (spanner)
on 2010-12-02 09:13
(Received via mailing list)
On 2 Dec 2010, at 00:25, rosslaird wrote:

> I have just started using Radiant (which is just great, by the way),
> so apologies in advance for what may be a very simple question: the
> server log shows various 404s to image files: button.png and new-
> snippet.png are two examples. My setup is on locahost, for testing, so
> the 404 refers to (for example) this url:
http://localhost/images/admin/button.png.

Both of those are files used by older versions of the admin interface.
The most likely explanation is that one of your extensions is not up to
date: being contemporary with an older version of radiant it is assuming
the presence of files that don't exist any more.

Radiant's helper methods mean that the author probably didn't need to
spell out the image path, but something like this (in your radiant
instance directory) should show you where it's coming from:

  grep -r 'new-snippet' .

I don't get any matches from a normal radiant site except in old log
files.

best,

will
B39240dc7475fb78645c56818ead0ac5?d=identicon&s=25 rosslaird (Guest)
on 2010-12-02 15:09
(Received via mailing list)
I started to wonder if this was related to the chronicle extension
after I grep'ed for various of the 404-causing files and found
references to these files:

./vendor/extensions/chronicle/app/views/admin/snippets/index.html.haml
./vendor/extensions/chronicle/public/javascripts/admin/chronicle.js
./vendor/extensions/chronicle/public/javascripts/admin/HelpBalloon.js
./vendor/extensions/chronicle/app/helpers/admin/timeline_helper.rb

Then I saw Will's response. So, although I do like the chronicle
extension, is the solution to remove it (at least for now, until it is
updated)? And, if so, I can't find documentation anywhere on how to do
that. (I have removed extensions from redmine by just deleting their
directories, but this is not best practice I'm sure.)
B39240dc7475fb78645c56818ead0ac5?d=identicon&s=25 rosslaird (Guest)
on 2010-12-02 15:12
(Received via mailing list)
Oh wait, I found it:

https://github.com/radiant/radiant/wiki/Uninstalli...

A nice wiki page on how to uninstall extensions. Don't know how I
missed that.
This topic is locked and can not be replied to.