Hi,

I am running Atahualpa V 3.6 and WP V 3.4.1.

I receive an error when running a Pingdom test for a page on my site that does not exist resulting in a 404.

http://weighlabel.com/images/expand-down-white.gif

I have tried finding where this reference may be located with no success. Also, have searched the forum here and have not come across this problem being reported prior.

Any help is most appreciated. Thanks.

Peter

That URL is pointing to an image in the images folder in the route of your site. Do you have an images folder in the root of your site? Do you have an image called expand-down-white.gif?

An update to my question and solution.

I edited the css.php file and added the full path (wp-content/themes/atahualpa/images) to where the images were stored and it seemed to solve my page not found problem.

Now the arrows were showing up in my page menu, which I had removed before. I originally edited the css.php file and commented out the appropriate section, but thought there must be a better way.

I further researched and came across a post (http://forum.bytesforall.com/showthread.php?t=17084) to remove the arrows..I added the code into the HTML/CSS Inserts section of the ATO and it is all fixed up.

Please feel free to comment or add any suggestions if I have missed something or have gone off in the wrong direction...I'm just hacking around, not a coder by any stretch of the imagination.

Hope this helps others.

Hi Larry,

No to both of your questions...which is still puzzling me as to why it caused a 404.

I was expecting the answers would be no to both questions. If the answer is no why are you using that url as a test?

Hi Larry,

I entered my site (main page) in Pingdom and it listed that particular url as one of the pages it is calling during the loading of my home page.

Per my earlier reply in this thread, as soon as I updated the path to where the file is located, error gone...but that was/is not a clean solution. The css insert you suggested in the post referred to above (removing the arrows on the page menu) did solve the problem and the file was no longer being loaded as part of the page test at Pingdom.

Hope that explains things a bit better. Appreciate the reply.

Peter